From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 00:57:59 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06ED11065672 for ; Sun, 11 Sep 2011 00:57:59 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id BC9F98FC1A for ; Sun, 11 Sep 2011 00:57:57 +0000 (UTC) Received: by yib19 with SMTP id 19so2097425yib.13 for ; Sat, 10 Sep 2011 17:57:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ljkzU/tp5avWjTJ4bK8qh5cnCodkFbiL/G/ClrwoKAE=; b=KLy+d3f1RrEgMJxD0ej9/zb8bnVdcudE2MP1lbTzOSy/CO9f3joUVSYX8XeFXaC2Km B0K/713uY6AaT2SSf0sOD/hDrf+11iRo4dOE/7SqmFcKoFsIFOm3WmIaTAaRgeqZVoSI F3OIO4aOWAghbKTOusZ4nTiVDewsN23I45tjk= MIME-Version: 1.0 Received: by 10.236.144.193 with SMTP id n41mr19376369yhj.78.1315702677273; Sat, 10 Sep 2011 17:57:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.103.6 with HTTP; Sat, 10 Sep 2011 17:57:57 -0700 (PDT) In-Reply-To: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> Date: Sun, 11 Sep 2011 08:57:57 +0800 X-Google-Sender-Auth: xw4YhDTdpvfDoYg_0dMqYhEsxxk Message-ID: From: Adrian Chadd To: Riccardo Cattaneo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 00:57:59 -0000 You can use the callout API to schedule timed events in the kernel. Adrian From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 01:02:08 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B59011065674 for ; Sun, 11 Sep 2011 01:02:08 +0000 (UTC) (envelope-from cattaneo.riccardo@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 4310A8FC0A for ; Sun, 11 Sep 2011 01:02:07 +0000 (UTC) Received: by fxe4 with SMTP id 4so4817128fxe.13 for ; Sat, 10 Sep 2011 18:02:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=kD027X+PFDeP9OaD6o/8oDk4Gw6Hbl6nYlSijoJaIL8=; b=VmVbCTcJhw5bLfl7jFFqo+e6fbywy6pQwbJZqsNAMtQ5lS8x5cMk1zfWuSyNiuSv2s HT7d9jEyoCwe5+p8QO/O4/xVNQkzZEPHkGvSnUtCldP6rZ3WpnODTycdeZBdcoOJU4OA QZFkz960gfsOeMi9UqIK/hw+jZ1OPzrn/InBc= Received: by 10.223.55.209 with SMTP id v17mr872252fag.77.1315702926883; Sat, 10 Sep 2011 18:02:06 -0700 (PDT) Received: from host-001.homenet.telecomitalia.it (host246-143-dynamic.44-79-r.retail.telecomitalia.it [79.44.143.246]) by mx.google.com with ESMTPS id g5sm4564589fad.19.2011.09.10.18.02.02 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 10 Sep 2011 18:02:02 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Riccardo Cattaneo In-Reply-To: Date: Sun, 11 Sep 2011 03:02:00 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <2778D90F-F718-446E-8ABB-627790F00A93@gmail.com> References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> To: Adrian Chadd X-Mailer: Apple Mail (2.1084) Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 01:02:08 -0000 Of course, the module from which I'm calling them must be already loaded = and initialized, isn't it? Riccardo On Sep 11, 2011, at 2:57 AM, Adrian Chadd wrote: > You can use the callout API to schedule timed events in the kernel. >=20 >=20 >=20 > Adrian From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 01:17:43 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 358511065670 for ; Sun, 11 Sep 2011 01:17:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id E91528FC16 for ; Sun, 11 Sep 2011 01:17:42 +0000 (UTC) Received: by yxk36 with SMTP id 36so2998348yxk.13 for ; Sat, 10 Sep 2011 18:17:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=h8VZ72jXtORKkhiw8mKU8dB4xVOXFJeAI0hQrWt9Bks=; b=Tmw46QIuXJJInE6yZkoiPkZPBtrvlfkDN8NmV7H1nD0Rb7vXDv59Gpzd+hAJste6C5 Lo4xHlF381Ny4uDhbhN91xKe+ajMZBcK/khYpGl05AHoRcokAJ3NOu2Tm60ch4QZuNAK 7y9yJhyrDkZck3IyXrAM2goaP/LRI9O63smE8= MIME-Version: 1.0 Received: by 10.236.173.131 with SMTP id v3mr19568314yhl.112.1315703862008; Sat, 10 Sep 2011 18:17:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.236.103.6 with HTTP; Sat, 10 Sep 2011 18:17:41 -0700 (PDT) In-Reply-To: <2778D90F-F718-446E-8ABB-627790F00A93@gmail.com> References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> <2778D90F-F718-446E-8ABB-627790F00A93@gmail.com> Date: Sun, 11 Sep 2011 09:17:41 +0800 X-Google-Sender-Auth: J78OXOpszyRrtSiz0LpG9akUzFk Message-ID: From: Adrian Chadd To: Riccardo Cattaneo Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 01:17:43 -0000 On 11 September 2011 09:02, Riccardo Cattaneo wrote: > Of course, the module from which I'm calling them must be already loaded and initialized, isn't it? > Riccardo Well, yes - but then, you can just add something to the module load code to start off the callout. There are race conditions to keep in mind though - the callout may just about to be in-play when you go to remove it. The callout manpage points out these situations under "Avoiding Race Conditions." Adrian From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 11:48:28 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27139106566B; Sun, 11 Sep 2011 11:48:28 +0000 (UTC) (envelope-from ambrosehua@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7A5658FC13; Sun, 11 Sep 2011 11:48:27 +0000 (UTC) Received: by fxg9 with SMTP id 9so256779fxg.13 for ; Sun, 11 Sep 2011 04:48:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=w0GOTNljptE0UXWqizzXFtrNLcr+stteOhNUjkJLBa0=; b=CraQ9Qudgk6JuFfv/99yVKLo+3VN9ZJ+1coS1YVfqtPbyvRxXjm1GyRjUe3Ir63rmw bAfQaH1GK2w9S0aaoyYPpvnLZNfSKEUs5eWzknNzFspWilXAG4mHEMPz35i7OXE/uMgA vfddQ1pDKeUdE3HkFkTLZZq5tBet/FlvbcHJ8= MIME-Version: 1.0 Received: by 10.223.37.68 with SMTP id w4mr1687472fad.49.1315741705570; Sun, 11 Sep 2011 04:48:25 -0700 (PDT) Received: by 10.223.62.5 with HTTP; Sun, 11 Sep 2011 04:48:25 -0700 (PDT) In-Reply-To: <20110909185909.GA66131@freebsd.org> References: <20110909162537.183770@gmx.com> <20110909184653.GA64971@freebsd.org> <20110909185909.GA66131@freebsd.org> Date: Sun, 11 Sep 2011 19:48:25 +0800 Message-ID: From: Paul Ambrose To: Alexander Best Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, Dieter BSD Subject: Re: excessive use of gettimeofday(2) and other syscalls X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 11:48:28 -0000 Sorry, my previous test is not accurate. I use both firefox and chromium to open 13 same web pages( two of them are from www.sina.com.cn, other from groups.google.com, wiki.sun.com and freebsd.org, both web browsers use libcrossflash to drive linux flash plugin, not linuxulator on my amd64 8.2-stable , sorry I can not have access to youtube.com or facebook.com, I'm in china), and this is the result: ................................................... [root@lateaxfreebsd sys]# dtrace -n 'syscall::gettimeofday:entry / execname == "chrome" || execname == "firefox-bin"|| execname == "plugin-container" / { @[execname] = count() } profile:::tick-1 { exit(0); } ' dtrace: description 'syscall::gettimeofday:entry ' matched 2 probes CPU ID FUNCTION:NAME 1 97 :tick-1 plugin-container 7802 chrome 8403 firefox-bin 215777 if I close the two sina.com.cn tab( the big page), then ................................................. [root@lateaxfreebsd sys]# dtrace -n 'syscall::gettimeofday:entry / execname == "chrome" || execname == "firefox-bin"|| execname == "plugin-container" / { @[execname] = count() } profile:::tick-1 { exit(0); } ' dtrace: description 'syscall::gettimeofday:entry ' matched 2 probes CPU ID FUNCTION:NAME 1 97 :tick-1 chrome 65 plugin-container 2145 firefox-bin 268932 I think I can drive conclusion that chromium is much better than firefox when rendering same page set, especially on static pages only 65 per second. If we add opera to the list( opera not using flash plugin), it seems opera does NOT use gettimeofday ..................................................... [root@lateaxfreebsd sys]# dtrace -n 'syscall::gettimeofday:entry / execname == "chrome" || execname == "firefox-bin"|| execname == "plugin-container" || execname == "opera" / { @[execname, probefunc] = count() } profile:::tick-1 { exit(0); } ' dtrace: description 'syscall::gettimeofday:entry ' matched 2 probes CPU ID FUNCTION:NAME 0 97 :tick-1 chrome gettimeofday 7632 plugin-container gettimeofday 8107 firefox-bin gettimeofday 232142 but it use more clock_gettime ..................................................... [root@lateaxfreebsd sys]# dtrace -n 'syscall::clock_gettime:entry / execname == "chrome" || execname == "firefox-bin"|| execname == "plugin-container" || execname == "opera" / { @[execname, probefunc] = count() } profile:::tick-1 { exit(0); } ' dtrace: description 'syscall::clock_gettime:entry ' matched 2 probes CPU ID FUNCTION:NAME 1 97 :tick-1 firefox-bin clock_gettime 634 chrome clock_gettime 839 plugin-container clock_gettime 1040 opera clock_gettime 14978 2011/9/10 Alexander Best > On Fri Sep 9 11, Alexander Best wrote: > > On Fri Sep 9 11, Dieter BSD wrote: > > > >> Firefox 5 and 6 has more gettimeofday call than 20000 per second on > my > > > >> amd64-8.2-stable box. > > > > > > > i don't see why chromium needs > > > > to call gettimeofday(2) or any library function that triggers it more > > > > than 3000 times a second. > > > > > > What the are web browsers doing that they "need" the clock > > > so often? > > > > > > I suspect the answer is the same as why firefox uses significant > amounts > > > of CPU when it should be idle, why it uses memory without bound > > > (I actually had to add ulimit to my shell's rc file :-( ), and > > > so on. > > > > > > Using "links -g", > > > "ktrace -di -tc -p6951; sleep 1; ktrace -C; kdump|wc -l" > > > gives a typical count of 300-400, highest count seen: 1454. > > > > well that measurement is probably unfair. my measurements included all > opened > > tabs (~ 15), running plugins and extensions. if i disable all of those > extra > > stuff and use only a single tab, chromium produces less syscalls than > links: > > > > 270 > > ...however sites such as facebook produce a much higher syscall peek under > chromium. with only one tab opened with youtube.com in it, chromium has a > typical syscall count of 700-2000. i guess this is due to stuff like js, > html5 > and friends. > > if i enable the flash plugins with only 1 single tab (youtube.com), the > syscall > count climbs to ~ 8000 with a peak at 19000 when youtube.com wasn't > completely > loaded. so the high syscall count is not only chromiums fault, but a > combination of chromium, flash and the linuxulator. > > i believe further linuxulator improvements might reduce syscalls in this > scenario. > > also with chromium 15, the syscall count is supposed to drop quite > noticably > (as mentioned in a previous message). > > cheers. > alex > > > > > cheers. > > alex > > > > > > > > What we need, is a sanely written web browser that has the > > > features we need. Unfortunately the last time I checked, > > > links and dillo both lacked features needed for online > > > shopping/banking. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 12:29:07 2011 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B672B1065672 for ; Sun, 11 Sep 2011 12:29:07 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id 947738FC0A for ; Sun, 11 Sep 2011 12:29:07 +0000 (UTC) Received: by pzk33 with SMTP id 33so18718300pzk.18 for ; Sun, 11 Sep 2011 05:29:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=5QcjaeYwGnc0coQj47oVEaMWsoKesmfHAKEfbPDmJiE=; b=LDbVEqUKj5eX4mQz1rJm3nIbMFmrXDSMaM0PFi28SQUop6AvkM7lD4AFODJBCT86F2 RYph7PfkgWbax+feP8Xrg+OC1uqrEAkxnc0B3sx1tzRoTIj//72G2jwpatxAbN58MwfK /WokoE529pLsNWp8N0EiHr9kM2hT8vu053NR8= MIME-Version: 1.0 Received: by 10.68.199.133 with SMTP id jk5mr4740506pbc.486.1315742362304; Sun, 11 Sep 2011 04:59:22 -0700 (PDT) Received: by 10.142.166.13 with HTTP; Sun, 11 Sep 2011 04:59:22 -0700 (PDT) Date: Sun, 11 Sep 2011 07:59:22 -0400 Message-ID: From: "b. f." To: Raphael Kubo da Costa , "Julian H. Stacey" , freebsd-hackers@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: man bzip2 - suggest we add to See Also X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 12:29:07 -0000 > > I suggest we should add a See Also section to man bzip2, > > FreeBSD-8.2-RELEASE & current man bzip2 > .../-current/src/contrib/bzip2/bzip2.1 > > adding URLs > http://www.7-zip.org/download.html -> > http://www.freshports.org/archivers/p7zip/ > > as currently no reference is made to 7zip or 7-zip I'm a bit confused -- are you recommending this because you think that users should be aware of the the other compression methods/archive formats that 7zip uses, so that they can investigate alternatives, or just because it is a Windows program that can decompress bzipped files? In either case, I don't see any reason to single out 7zip -- we have xz(1) in the base system now, and there are other, arguably better compression methods in Ports. And there is a lot of Windows-based software that can decompress bzip2, including Windows ports of bzip2 itself. I don't think that the bzip2 manpage is the appropriate place to add this kind of information. (Perhaps the FreeBSD Handbook, in a section about working with files typically found on FreeBSD or other Unixen in Windows, or in libarchive(5), if it were changed to support the 7zip archive format.) And I don't think that -hackers is the appropriate list for this proposal -- -doc seems to be the right place. b. From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 12:54:15 2011 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C3D0106566B for ; Sun, 11 Sep 2011 12:54:15 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 06A7D8FC08 for ; Sun, 11 Sep 2011 12:54:14 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBE209.dip.t-dialin.net [93.203.226.9]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p8BCJrpl078045; Sun, 11 Sep 2011 12:19:54 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id p8BCJjL6049925; Sun, 11 Sep 2011 14:19:46 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p8BCJXwY059714; Sun, 11 Sep 2011 12:19:39 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109111219.p8BCJXwY059714@fire.js.berklix.net> To: bf1783@gmail.com From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 11 Sep 2011 07:59:22 EDT." Date: Sun, 11 Sep 2011 14:19:33 +0200 Sender: jhs@berklix.com Cc: freebsd-hackers@FreeBSD.org, Raphael Kubo da Costa Subject: Re: man bzip2 - suggest we add to See Also X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 12:54:15 -0000 "b. f." wrote: > > > > I suggest we should add a See Also section to man bzip2, > > > > FreeBSD-8.2-RELEASE & current man bzip2 > > .../-current/src/contrib/bzip2/bzip2.1 > > > > adding URLs > > http://www.7-zip.org/download.html -> > > http://www.freshports.org/archivers/p7zip/ > > > > as currently no reference is made to 7zip or 7-zip > > I'm a bit confused -- are you recommending this because you think that > users should be aware of the the other compression methods/archive > formats that 7zip uses, so that they can investigate alternatives, or > just because it is a Windows program that can decompress bzipped > files? Yes. If FreeBSD users happen to export .bz2 files to Microsoft users, uts nice to be able to tell MS users at least 1 MS program that can access the format. > In either case, I don't see any reason to single out 7zip -- > we have xz(1) in the base system now, and there are other, arguably > better compression methods in Ports. And there is a lot of > Windows-based software that can decompress bzip2, including Windows > ports of bzip2 itself. OK didnt know that. by all means add a URL. > I don't think that the bzip2 manpage is the > appropriate place to add this kind of information. (Perhaps the > FreeBSD Handbook, in a section about working with files typically > found on FreeBSD or other Unixen in Windows, or in libarchive(5), if > it were changed to support the 7zip archive format.) And I don't think > that -hackers is the appropriate list for this proposal -- -doc seems > to be the right place. Well I'm an old Unix hand, I have much more faith in the man command, that works on machines even if no net connected. (& easy to edit, & format without the tool chain from hell that doc uses) hence I suggested adding a URL in see also of man. Cos' if eg I get a phone call from an MS [l]user saying "what do I do with your .bz2?" I would first by reflex type man bzip2 /See Also. & not first connect to net & mouse around to docs. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 13:08:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D4EB1065673; Sun, 11 Sep 2011 13:08:37 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id BD63B8FC12; Sun, 11 Sep 2011 13:08:36 +0000 (UTC) Received: by yxk36 with SMTP id 36so3176398yxk.13 for ; Sun, 11 Sep 2011 06:08:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=AyCGYtXfHltQjcYJRTL3bAEkSLOkOkOWqQf/byG7OKc=; b=UP/vd+g9PqvR02ASIfflwANu0jhC5vtfne44K8Hlznzwsg2nadqztTnCN6nrbhgmQ3 lVYWVYQ46Acof6hQw6V1ohGphvXlSA2TwMci+MhggGbi7YN5x20Opv9KXpgJv/rRq4UA /HxWBiislUGg1ZUGR4qWj9mPSLs5X+UOct/bA= Received: by 10.43.132.130 with SMTP id hu2mr415529icc.352.1315746515288; Sun, 11 Sep 2011 06:08:35 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.231.61.148 with HTTP; Sun, 11 Sep 2011 06:08:05 -0700 (PDT) In-Reply-To: <201109111219.p8BCJXwY059714@fire.js.berklix.net> References: <201109111219.p8BCJXwY059714@fire.js.berklix.net> From: Chris Rees Date: Sun, 11 Sep 2011 14:08:05 +0100 X-Google-Sender-Auth: kQoX3bdDJ0l49ZHeuWj4sFKb2So Message-ID: To: "Julian H. Stacey" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: bf1783@gmail.com, freebsd-hackers@freebsd.org, Raphael Kubo da Costa Subject: Re: man bzip2 - suggest we add to See Also X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 13:08:37 -0000 On 11 September 2011 13:19, Julian H. Stacey wrote: > "b. f." wrote: >> > >> > I suggest we should add a See Also section to man bzip2, >> > >> > =A0 =A0 =A0 =A0 FreeBSD-8.2-RELEASE & current man bzip2 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 .../-current/src/contrib/bzip2/bzip2.1 >> > >> > adding URLs >> > =A0 =A0 =A0 =A0 http://www.7-zip.org/download.html =A0 =A0 =A0-> >> > =A0 =A0 =A0 =A0 http://www.freshports.org/archivers/p7zip/ >> > >> > as currently no reference is made to 7zip or 7-zip >> >> I'm a bit confused -- are you recommending this because you think that >> users should be aware of the the other compression methods/archive >> formats that 7zip uses, so that they can investigate alternatives, or >> just because it is a Windows program that can decompress bzipped >> files? > > Yes. > If FreeBSD users happen to export .bz2 files to Microsoft users, > uts nice to be able to tell MS users at least 1 MS program that can > access the format. > >> In either case, I don't see any reason to single out 7zip -- >> we have xz(1) in the base system now, and there are other, arguably >> better compression methods in Ports. And there is a lot of >> Windows-based software that can decompress bzip2, including Windows >> ports of bzip2 itself. > > OK didnt know that. by all means add a URL. > >> I don't think that the bzip2 manpage is the >> appropriate place to add this kind of information. =A0(Perhaps the >> FreeBSD Handbook, in a section about working with files typically >> found on FreeBSD or other Unixen in Windows, or in libarchive(5), if >> it were changed to support the 7zip archive format.) And I don't think >> that -hackers is the appropriate list for this proposal -- -doc seems >> to be the right place. > > Well I'm an old Unix hand, I have much more faith in the man command, > that works on machines even if no net connected. (& easy to edit, > & format without the tool chain from hell that doc uses) hence I > suggested adding a URL in see also of man. > > Cos' if eg I get a phone call from an MS [l]user saying "what do I > do with your .bz2?" I would first by reflex type man bzip2 /See > Also. =A0& not first connect to net & mouse around to docs. > Do we usually add a Windows analogue of our commands to the man page? I would have thought that Google is definitely the most appropriate medium for finding that out. Chris From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 13:30:50 2011 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 227B51065670; Sun, 11 Sep 2011 13:30:50 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 7E06B8FC0C; Sun, 11 Sep 2011 13:30:49 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBE209.dip.t-dialin.net [93.203.226.9]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p8BDUlDe078450; Sun, 11 Sep 2011 13:30:47 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id p8BDUbef051599; Sun, 11 Sep 2011 15:30:38 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p8BDUJMO060192; Sun, 11 Sep 2011 13:30:25 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109111330.p8BDUJMO060192@fire.js.berklix.net> to: freebsd-hackers@FreeBSD.org From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 11 Sep 2011 14:19:33 +0200." Date: Sun, 11 Sep 2011 15:30:19 +0200 Sender: jhs@berklix.com Cc: bf1783@gmail.com, Raphael Kubo da Costa , Julian Seward Subject: Re: man bzip2 - suggest we add to See Also X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 13:30:50 -0000 Hi, Repost of mine, with restored cc: Julian Seward as I just noticed (while later answering Chris Rees), that Julian Seward ( author of imported code in src/ ) mistakenly dropped by bf1783@gmail.com (so Chris inherited depleted CC line from b f) Reference: > From: "Julian H. Stacey" > Date: Sun, 11 Sep 2011 14:19:33 +0200 > "Julian H. Stacey" wrote: > "b. f." wrote: > > > > > > I suggest we should add a See Also section to man bzip2, > > > > > > FreeBSD-8.2-RELEASE & current man bzip2 > > > .../-current/src/contrib/bzip2/bzip2.1 > > > > > > adding URLs > > > http://www.7-zip.org/download.html -> > > > http://www.freshports.org/archivers/p7zip/ > > > > > > as currently no reference is made to 7zip or 7-zip > > > > I'm a bit confused -- are you recommending this because you think that > > users should be aware of the the other compression methods/archive > > formats that 7zip uses, so that they can investigate alternatives, or > > just because it is a Windows program that can decompress bzipped > > files? > > Yes. > If FreeBSD users happen to export .bz2 files to Microsoft users, > uts nice to be able to tell MS users at least 1 MS program that can > access the format. > > > In either case, I don't see any reason to single out 7zip -- > > we have xz(1) in the base system now, and there are other, arguably > > better compression methods in Ports. And there is a lot of > > Windows-based software that can decompress bzip2, including Windows > > ports of bzip2 itself. > > OK didnt know that. by all means add a URL. > > > I don't think that the bzip2 manpage is the > > appropriate place to add this kind of information. (Perhaps the > > FreeBSD Handbook, in a section about working with files typically > > found on FreeBSD or other Unixen in Windows, or in libarchive(5), if > > it were changed to support the 7zip archive format.) And I don't think > > that -hackers is the appropriate list for this proposal -- -doc seems > > to be the right place. > > Well I'm an old Unix hand, I have much more faith in the man command, > that works on machines even if no net connected. (& easy to edit, > & format without the tool chain from hell that doc uses) hence I > suggested adding a URL in see also of man. > > Cos' if eg I get a phone call from an MS [l]user saying "what do I > do with your .bz2?" I would first by reflex type man bzip2 /See > Also. & not first connect to net & mouse around to docs. > > Cheers, > Julian > -- > Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com > Reply below, not above; Indent with "> "; Cumulative like a play script. > Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. > http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 11 13:49:54 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 73FB2106564A; Sun, 11 Sep 2011 13:49:54 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id D67318FC12; Sun, 11 Sep 2011 13:49:53 +0000 (UTC) Received: from mart.js.berklix.net (p5DCBE209.dip.t-dialin.net [93.203.226.9]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id p8BDnpAP078600; Sun, 11 Sep 2011 13:49:52 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id p8BDnjm8052774; Sun, 11 Sep 2011 15:49:45 +0200 (CEST) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.4/8.14.4) with ESMTP id p8BDnRGJ060535; Sun, 11 Sep 2011 13:49:33 GMT (envelope-from jhs@fire.js.berklix.net) Message-Id: <201109111349.p8BDnRGJ060535@fire.js.berklix.net> to: freebsd-hackers@freebsd.org From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Sun, 11 Sep 2011 14:08:05 BST." Date: Sun, 11 Sep 2011 15:49:27 +0200 Sender: jhs@berklix.com Cc: bf1783@gmail.com, Chris Rees , Raphael Kubo da Costa , Julian Seward Subject: Re: man bzip2 - suggest we add to See Also X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 13:49:54 -0000 Chris Rees wrote: > On 11 September 2011 13:19, Julian H. Stacey wrote: > > "b. f." wrote: > >> > > >> > I suggest we should add a See Also section to man bzip2, > >> > > >> >         FreeBSD-8.2-RELEASE & current man bzip2 > >> >                 .../-current/src/contrib/bzip2/bzip2.1 > >> > > >> > adding URLs > >> >         http://www.7-zip.org/download.html      -> > >> >         http://www.freshports.org/archivers/p7zip/ > >> > > >> > as currently no reference is made to 7zip or 7-zip > >> > >> I'm a bit confused -- are you recommending this because you think that > >> users should be aware of the the other compression methods/archive > >> formats that 7zip uses, so that they can investigate alternatives, or > >> just because it is a Windows program that can decompress bzipped > >> files? > > > > Yes. > > If FreeBSD users happen to export .bz2 files to Microsoft users, > > uts nice to be able to tell MS users at least 1 MS program that can > > access the format. > > > >> In either case, I don't see any reason to single out 7zip -- > >> we have xz(1) in the base system now, and there are other, arguably > >> better compression methods in Ports. And there is a lot of > >> Windows-based software that can decompress bzip2, including Windows > >> ports of bzip2 itself. > > > > OK didnt know that. by all means add a URL. > > > >> I don't think that the bzip2 manpage is the > >> appropriate place to add this kind of information.  (Perhaps the > >> FreeBSD Handbook, in a section about working with files typically > >> found on FreeBSD or other Unixen in Windows, or in libarchive(5), if > >> it were changed to support the 7zip archive format.) And I don't think > >> that -hackers is the appropriate list for this proposal -- -doc seems > >> to be the right place. > > > > Well I'm an old Unix hand, I have much more faith in the man command, > > that works on machines even if no net connected. (& easy to edit, > > & format without the tool chain from hell that doc uses) hence I > > suggested adding a URL in see also of man. > > > > Cos' if eg I get a phone call from an MS [l]user saying "what do I > > do with your .bz2?" I would first by reflex type man bzip2 /See > > Also.  & not first connect to net & mouse around to docs. > > > > Do we usually add a Windows analogue of our commands to the man page? > I would have thought that Google is definitely the most appropriate > medium for finding that out. > > Chris Good point. Consisteny; that would probably tilt to Not adding any URLs; but many Unix commands don't have direct comparable commands, so there's not so many commands to be consistent with I suppose, tar might be a related tool to be consistent with, but bsdtar is quite new, & hasn't had much time to accumulate URLs to compatible tools on other OS's, though it does have a section Standards. Google & other search engines help discovery, (that's how I found bzip2 compression method listed on minux3.org in last URL). I guess author of imported code will decide: Julian Seward Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below, not above; Indent with "> "; Cumulative like a play script. Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. http://www.softwarefreedomday.org 17th Sept, http://berklix.org/sfd/ Oct. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 09:11:58 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B093106564A for ; Mon, 12 Sep 2011 09:11:58 +0000 (UTC) (envelope-from filippo.sironi@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CCB998FC08 for ; Mon, 12 Sep 2011 09:11:57 +0000 (UTC) Received: by wyh15 with SMTP id 15so4218853wyh.13 for ; Mon, 12 Sep 2011 02:11:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=v3/gVopqB+Fua3W+r7SGt/gcfq6uY3xvfc07UmZUmDc=; b=hHfID4Oki0NSufYpgPw10Q3uLhfbNRUQFU5r/OdWfmnJfbOKebfach8xIATTPKlJ0Z ivLuXUTdk8fjpn/EKCXpsgt4mSPB8RHnsxvad/Xtvf9fpJvmVB3PRJuSbaW2BOiRL/x4 PzuBOARoQiO5Ewd1BfRiPmK0+geUA7RHdmnY0= Received: by 10.227.209.21 with SMTP id ge21mr3009362wbb.42.1315816965264; Mon, 12 Sep 2011 01:42:45 -0700 (PDT) Received: from filippo.sironi.dynamic.micro.elet.polimi.it (micro.elet.polimi.it [131.175.127.118]) by mx.google.com with ESMTPS id fa7sm15442107wbb.26.2011.09.12.01.42.43 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Sep 2011 01:42:44 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Filippo Sironi In-Reply-To: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> Date: Mon, 12 Sep 2011 10:42:40 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> To: Riccardo Cattaneo X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 09:11:58 -0000 This is what I wrote for FreeBSD 7.2 and it does not work: = --------------------------------------------------------------------------= ------ #include #include #include #include static struct callout timer_callout; static void timer_function(void *arg) { if (callout_reset(&timer_callout, hz, timer_function, NULL)) uprintf("callout_reset() !=3D 0\n"); uprintf("Hello, World!\n"); } static int timer_event_handler(struct module *mod, int cmd, void *arg) { switch (cmd) { case MOD_LOAD: callout_init(&timer_callout, CALLOUT_MPSAFE); if (callout_reset(&timer_callout, hz, timer_function, = NULL)) uprintf("callout_reset() !=3D 0\n"); break; case MOD_UNLOAD: callout_drain(&timer_callout); break; case MOD_SHUTDOWN: break; default: return EOPNOTSUPP; } return 0; } static struct moduledata timer_moduledata =3D { "timer", timer_event_handler, NULL }; DECLARE_MODULE(timer, timer_moduledata, SI_SUB_DRIVERS, = SI_ORDER_MIDDLE); = --------------------------------------------------------------------------= ------ but I do not know why... I basically run through many different examples I found within the = kernel and they are not different from this module. Does anyone see any clear issue? Filippo On 10/set/2011, at 19:39, Riccardo Cattaneo wrote: > Hi all, > Me in the same situation: university project, freebsd os, required to = call a certain function X times/second (say, uprintf). > Got no luck till now :( > Thanks > Riccardo_______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 09:24:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37C5D1065676 for ; Mon, 12 Sep 2011 09:24:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f50.google.com (mail-vw0-f50.google.com [209.85.212.50]) by mx1.freebsd.org (Postfix) with ESMTP id E1CB68FC0C for ; Mon, 12 Sep 2011 09:24:23 +0000 (UTC) Received: by vws14 with SMTP id 14so4213897vws.37 for ; Mon, 12 Sep 2011 02:24:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wyUIZwHxXIgEXoRizv39JqUSY1r3PvLrMsBoJSab1Ws=; b=YRBzksdvxewp9aM33I7YmIXtjMe6zuHownvrhpqvXggzGTfhhnb4MXouxB2xhP5RHh F4gERfw2IvtAmgDq06RMajeWcLFGNfm8y+3q6vzqXNKGjkB+VMI/NslZz0XwAztysOJZ C7Woi1tsSmmnnhZMFmdY+47kWHbAzqYS9wC2U= MIME-Version: 1.0 Received: by 10.52.72.16 with SMTP id z16mr1932293vdu.395.1315819463126; Mon, 12 Sep 2011 02:24:23 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.52.161.138 with HTTP; Mon, 12 Sep 2011 02:24:23 -0700 (PDT) In-Reply-To: References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> Date: Mon, 12 Sep 2011 17:24:23 +0800 X-Google-Sender-Auth: Njvvf6oiOwcKOsEVZwvf-mXEAY0 Message-ID: From: Adrian Chadd To: Filippo Sironi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org, Riccardo Cattaneo Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 09:24:24 -0000 How about adding some printfs() to the functions to ensure they're being called? Adrian From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 09:34:55 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AC93106566C for ; Mon, 12 Sep 2011 09:34:55 +0000 (UTC) (envelope-from filippo.sironi@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 14DE98FC16 for ; Mon, 12 Sep 2011 09:34:54 +0000 (UTC) Received: by wwe3 with SMTP id 3so1829552wwe.31 for ; Mon, 12 Sep 2011 02:34:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=RZ1SgopnE5+CBMiWY/I68QYYiFTFwuNG4hAndQSOpys=; b=JDpfA3RMrT+C36VTJofDStdyKZ+1tDC4hdJNAaA56w46CF6e+fq6F8DXOQ9UqMihhy mpS31JJBbVRS01Ja12RWGiaV8WIF6x8vQVZAV9wh/U9CleASG0+OVEz8/00Q1nAdnPi4 RZwVkQ11VMekz7TaPbAOmRGn3eIsD8eFaKkSI= Received: by 10.216.132.210 with SMTP id o60mr2204531wei.82.1315820093668; Mon, 12 Sep 2011 02:34:53 -0700 (PDT) Received: from filippo.sironi.dynamic.micro.elet.polimi.it (micro.elet.polimi.it [131.175.127.118]) by mx.google.com with ESMTPS id fa7sm15605078wbb.26.2011.09.12.02.34.52 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Sep 2011 02:34:52 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: Filippo Sironi In-Reply-To: Date: Mon, 12 Sep 2011 11:34:50 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <4C14E323-F283-4EB1-82D9-E782A3340995@gmail.com> References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> To: Adrian Chadd X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-hackers@freebsd.org, Riccardo Cattaneo Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 09:34:55 -0000 I already did that to ensure timer_event_handler would be called = correctly. The result follows: freebsd# kldload ./timer.ko=20 timer_event_handler() with MOD_LOAD freebsd# kldunload ./timer.ko=20 timer_event_handler() with MOD_UNLOAD and I maintained the module load for about 1 minute so the timer = printing "Hello, World!" should have been run. Filippo On 12/set/2011, at 11:24, Adrian Chadd wrote: > How about adding some printfs() to the functions to ensure they're = being called? >=20 > Adrian From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 09:58:41 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E1861065675 for ; Mon, 12 Sep 2011 09:58:41 +0000 (UTC) (envelope-from filippo.sironi@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 4D3508FC08 for ; Mon, 12 Sep 2011 09:58:40 +0000 (UTC) Received: by qyk10 with SMTP id 10so1444074qyk.13 for ; Mon, 12 Sep 2011 02:58:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=UFV+bV97mfXesT7ygoc89zcHWijcIgHFniSsDg4cXKA=; b=MH9WgDlza13OjbAEZH2sJrwujE+Vly4Fahy1fOpjGdfvgyFYdxdMkeEPhGnySLu67u gkQvENpWaoD1GM3uNaYzqpNJG4gzrlLPj+F5/pxX9uL/phKGe/vsEKQNZfFMVZblmsBX z85uzG8JZTSnFya6IWmtjDPLUQ3kyurquIe80= Received: by 10.224.9.14 with SMTP id j14mr1129200qaj.376.1315821520559; Mon, 12 Sep 2011 02:58:40 -0700 (PDT) Received: from filippo.sironi.dynamic.micro.elet.polimi.it (micro.elet.polimi.it. [131.175.127.118]) by mx.google.com with ESMTPS id el2sm12177250qab.2.2011.09.12.02.58.39 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Sep 2011 02:58:39 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: Filippo Sironi X-Priority: 3 In-Reply-To: <20110912094842.251380@gmx.net> Date: Mon, 12 Sep 2011 11:58:37 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <9B13644B-F61E-4761-8C4F-E9E33F6E82B8@gmail.com> References: <20110912094842.251380@gmx.net> To: =?iso-8859-1?Q?=22Marc_L=F6rner=22?= X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 09:58:41 -0000 This is how I modified the module: = --------------------------------------------------------------------------= ------ #include #include #include #include static struct callout timer_callout; static void timer_function(void *arg) { uprintf("timer_function() begin\n"); if (callout_reset(&timer_callout, hz, timer_function, NULL)) uprintf("callout_reset() !=3D 0\n"); uprintf("Hello, World!\n"); uprintf("timer_function() end\n"); } static int timer_event_handler(struct module *mod, int cmd, void *arg) { uprintf("timer_event_handler() begin\n"); switch (cmd) { case MOD_LOAD: uprintf("MOD_LOAD\n"); callout_init(&timer_callout, CALLOUT_MPSAFE); if (callout_reset(&timer_callout, hz, timer_function, = NULL)) uprintf("callout_reset() !=3D 0\n"); break; case MOD_UNLOAD: uprintf("MOD_UNLOAD\n"); callout_drain(&timer_callout); break; case MOD_SHUTDOWN: uprintf("MOD_SHUTDOWN\n"); break; default: return EOPNOTSUPP; } uprintf("timer_event_handler() end\n"); return 0; } static struct moduledata timer_moduledata =3D { "timer", timer_event_handler, NULL }; DECLARE_MODULE(timer, timer_moduledata, SI_SUB_DRIVERS, = SI_ORDER_MIDDLE); = --------------------------------------------------------------------------= ------ and this is the output of load and unload operations: freebsd# kldload ./timer.ko timer_event_handler() begin MOD_LOAD timer_event_handler() end freebsd# kldunload timer.ko timer_event_handler() begin timer_event_handler() begin MOD_UNLOAD timer_event_handler() end I don't know why "timer_event_handler() begin" is printed twice on = unload but the timer doesn't start... and of course it is set on 1 = second but I left the module load for 1 minute or so just to be sure. ;) Thanks again for your help, Filippo On 12/set/2011, at 11:48, Marc L=F6rner wrote: > Hello, > what about changing order of callout_reset and uprintf? > And your timeout isn't 1minute, it's one second! >=20 > Regards, > Marc > --=20 > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 10:15:23 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD5001065675 for ; Mon, 12 Sep 2011 10:15:23 +0000 (UTC) (envelope-from loerner@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by mx1.freebsd.org (Postfix) with SMTP id 299E98FC0C for ; Mon, 12 Sep 2011 10:15:22 +0000 (UTC) Received: (qmail 27355 invoked by uid 0); 12 Sep 2011 09:48:42 -0000 Received: from 212.185.199.2 by www041.gmx.net with HTTP; Mon, 12 Sep 2011 11:48:41 +0200 (CEST) Content-Type: text/plain; charset="utf-8" Date: Mon, 12 Sep 2011 11:48:42 +0200 From: =?iso-8859-1?Q?=22Marc_L=F6rner=22?= Message-ID: <20110912094842.251380@gmx.net> MIME-Version: 1.0 To: filippo.sironi@gmail.com X-Authenticated: #60932973 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX1+Fl0cGbPKFfxYKB14A4lVM/CKXbLd4iOzSmmkxYz zQIUx1GwxFuKvvRoTs12ZAp7cZSqKj190z/g== Content-Transfer-Encoding: 8bit X-GMX-UID: HrwID1wWfW47S1eZ1mZokHRudmllcoVv X-Mailman-Approved-At: Mon, 12 Sep 2011 11:17:14 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 10:15:23 -0000 Hello, what about changing order of callout_reset and uprintf? And your timeout isn't 1minute, it's one second! Regards, Marc >I already did that to ensure timer_event_handler would be called correctly. > >The result follows: > >freebsd# kldload ./timer.ko >timer_event_handler() with MOD_LOAD > >freebsd# kldunload ./timer.ko >timer_event_handler() with MOD_UNLOAD > >and I maintained the module load for about 1 minute so the timer printing >"Hello, World!" should have been run. > >Filippo > >On 12/set/2011, at 11:24, Adrian Chadd wrote: > >> How about adding some printfs() to the functions to ensure they're being called? >> >> Adrian > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 11:27:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CCD2106564A for ; Mon, 12 Sep 2011 11:27:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id ED3188FC0C for ; Mon, 12 Sep 2011 11:27:08 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p8CBR3Dt022038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Sep 2011 14:27:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p8CBR3RF047328; Mon, 12 Sep 2011 14:27:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p8CBR38H047327; Mon, 12 Sep 2011 14:27:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 12 Sep 2011 14:27:03 +0300 From: Kostik Belousov To: Marc L?rner Message-ID: <20110912112703.GO17489@deviant.kiev.zoral.com.ua> References: <20110912094842.251380@gmx.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8fdAbLF0bbg2TsS/" Content-Disposition: inline In-Reply-To: <20110912094842.251380@gmx.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: filippo.sironi@gmail.com, freebsd-hackers@freebsd.org Subject: Re: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 11:27:09 -0000 --8fdAbLF0bbg2TsS/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 12, 2011 at 11:48:42AM +0200, "Marc L?rner" wrote: > Hello, > what about changing order of callout_reset and uprintf? > And your timeout isn't 1minute, it's one second! >=20 > Regards, > Marc >=20 > >I already did that to ensure timer_event_handler would be called correct= ly. > > > >The result follows: > > > >freebsd# kldload ./timer.ko=20 > >timer_event_handler() with MOD_LOAD > > > >freebsd# kldunload ./timer.ko=20 > >timer_event_handler() with MOD_UNLOAD > > > >and I maintained the module load for about 1 minute so the timer printin= g >"Hello, World!" should have been run. > > > >Filippo > > > >On 12/set/2011, at 11:24, Adrian Chadd wrote: > > > >> How about adding some printfs() to the functions to ensure they're bei= ng called? > >>=20 The callouts are executed in the context that does not have the controlling terminal. uprintf(9) tries to use the ctty for output. Use printf(9) to get something on console. --8fdAbLF0bbg2TsS/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5t7IcACgkQC3+MBN1Mb4iyzQCfbwFFVQnPHcMCwNWVsk+QKL7X dtUAoIL3v6D9FbH1yO0c0epPUovv3W0D =aUjh -----END PGP SIGNATURE----- --8fdAbLF0bbg2TsS/-- From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 11:36:22 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95C45106566C for ; Mon, 12 Sep 2011 11:36:22 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2E7148FC0A for ; Mon, 12 Sep 2011 11:36:21 +0000 (UTC) Received: by wyh15 with SMTP id 15so4386665wyh.13 for ; Mon, 12 Sep 2011 04:36:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xRX3YxSjVXfLfTUtkQUEzOvdMExZ+viFPMloQ8kmgLQ=; b=v74AnbC66BiZUEl5V0FHjDrr6Fj8QTdjQiT5m0YWdCbthigK2m09gElCSaLqunvsh0 S7fsZOSb1DQMJoSDmmyBkq0pw7jCboAwplX5NaC90cLJYt4g6XzYfSpLOI34UV4/5/Lu dWhX/ajDGte6Igq2y4fxkSuZCJ4yJdKPvAx4Q= MIME-Version: 1.0 Received: by 10.227.200.147 with SMTP id ew19mr78832wbb.38.1315827380981; Mon, 12 Sep 2011 04:36:20 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.227.19.193 with HTTP; Mon, 12 Sep 2011 04:36:20 -0700 (PDT) In-Reply-To: <20110912112703.GO17489@deviant.kiev.zoral.com.ua> References: <20110912094842.251380@gmx.net> <20110912112703.GO17489@deviant.kiev.zoral.com.ua> Date: Mon, 12 Sep 2011 13:36:20 +0200 X-Google-Sender-Auth: TH6HyemrD8REC55N-4VSxe6b44M Message-ID: From: Attilio Rao To: Kostik Belousov Content-Type: text/plain; charset=UTF-8 Cc: filippo.sironi@gmail.com, freebsd-hackers@freebsd.org, Marc L?rner Subject: Re: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 11:36:22 -0000 Besides I'd also suggest to have the callout rearming as the very last step of you callback in order to avoid buffering interleaving issues. Attilio 2011/9/12 Kostik Belousov : > On Mon, Sep 12, 2011 at 11:48:42AM +0200, "Marc L?rner" wrote: >> Hello, >> what about changing order of callout_reset and uprintf? >> And your timeout isn't 1minute, it's one second! >> >> Regards, >> Marc >> >> >I already did that to ensure timer_event_handler would be called correctly. >> > >> >The result follows: >> > >> >freebsd# kldload ./timer.ko >> >timer_event_handler() with MOD_LOAD >> > >> >freebsd# kldunload ./timer.ko >> >timer_event_handler() with MOD_UNLOAD >> > >> >and I maintained the module load for about 1 minute so the timer printing >"Hello, World!" should have been run. >> > >> >Filippo >> > >> >On 12/set/2011, at 11:24, Adrian Chadd wrote: >> > >> >> How about adding some printfs() to the functions to ensure they're being called? >> >> > > The callouts are executed in the context that does not have the controlling > terminal. uprintf(9) tries to use the ctty for output. > > Use printf(9) to get something on console. > -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 11:17:45 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 359091065674 for ; Mon, 12 Sep 2011 11:17:45 +0000 (UTC) (envelope-from loerner@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 9DC378FC17 for ; Mon, 12 Sep 2011 11:17:44 +0000 (UTC) Received: (qmail 22319 invoked by uid 0); 12 Sep 2011 11:17:43 -0000 Received: from 212.185.199.2 by www062.gmx.net with HTTP; Mon, 12 Sep 2011 13:17:41 +0200 (CEST) Content-Type: text/plain; charset="utf-8" Date: Mon, 12 Sep 2011 13:17:41 +0200 From: =?iso-8859-1?Q?=22Marc_L=F6rner=22?= In-Reply-To: <9B13644B-F61E-4761-8C4F-E9E33F6E82B8@gmail.com> Message-ID: <20110912111741.298340@gmx.net> MIME-Version: 1.0 References: <20110912094842.251380@gmx.net> <9B13644B-F61E-4761-8C4F-E9E33F6E82B8@gmail.com> To: Filippo Sironi X-Authenticated: #60932973 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) X-Priority: 3 X-Provags-ID: V01U2FsdGVkX19SygZP+EFSvmTMxromH/v+b5U/JwQGSYmCtSh5Rl mdYdA6wnxi6V1oxqeLNSzJ+OIrYb2Zz3ub0w== Content-Transfer-Encoding: 8bit X-GMX-UID: bdhUe7E5eWUoTQWi0nZz9B0xU3U4N8/a X-Mailman-Approved-At: Mon, 12 Sep 2011 11:42:47 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 11:17:45 -0000 Hello again, it seems that uprintf needs a tty to put output to. I tried your code with printf instead of uprintf and got output to root-console ttyu0 every second. HTH, Marc -------- Original-Nachricht -------- > Datum: Mon, 12 Sep 2011 11:58:37 +0200 > Von: Filippo Sironi > An: "Marc Lörner" > CC: freebsd-hackers@freebsd.org > Betreff: Re: Kernel timers infrastructure > This is how I modified the module: > -------------------------------------------------------------------------------- > #include > #include > #include > #include > > static struct callout timer_callout; > > static void > timer_function(void *arg) > { > uprintf("timer_function() begin\n"); > if (callout_reset(&timer_callout, hz, timer_function, NULL)) > uprintf("callout_reset() != 0\n"); > uprintf("Hello, World!\n"); > uprintf("timer_function() end\n"); > } > > static int > timer_event_handler(struct module *mod, int cmd, void *arg) > { > uprintf("timer_event_handler() begin\n"); > switch (cmd) { > case MOD_LOAD: > uprintf("MOD_LOAD\n"); > callout_init(&timer_callout, CALLOUT_MPSAFE); > if (callout_reset(&timer_callout, hz, timer_function, NULL)) > uprintf("callout_reset() != 0\n"); > break; > case MOD_UNLOAD: > uprintf("MOD_UNLOAD\n"); > callout_drain(&timer_callout); > break; > case MOD_SHUTDOWN: > uprintf("MOD_SHUTDOWN\n"); > break; > default: > return EOPNOTSUPP; > } > uprintf("timer_event_handler() end\n"); > return 0; > } > > static struct moduledata timer_moduledata = { > "timer", > timer_event_handler, > NULL > }; > > DECLARE_MODULE(timer, timer_moduledata, SI_SUB_DRIVERS, SI_ORDER_MIDDLE); > -------------------------------------------------------------------------------- > and this is the output of load and unload operations: > freebsd# kldload ./timer.ko > timer_event_handler() begin > MOD_LOAD > timer_event_handler() end > freebsd# kldunload timer.ko > timer_event_handler() begin > timer_event_handler() begin > MOD_UNLOAD > timer_event_handler() end > > I don't know why "timer_event_handler() begin" is printed twice on unload > but the timer doesn't start... and of course it is set on 1 second but I > left the module load for 1 minute or so just to be sure. ;) > > Thanks again for your help, > Filippo > > On 12/set/2011, at 11:48, Marc Lörner wrote: > > > Hello, > > what about changing order of callout_reset and uprintf? > > And your timeout isn't 1minute, it's one second! > > > > Regards, > > Marc > > -- > > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 12:12:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17185106567A for ; Mon, 12 Sep 2011 12:12:24 +0000 (UTC) (envelope-from filippo.sironi@gmail.com) Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9BA9E8FC16 for ; Mon, 12 Sep 2011 12:12:23 +0000 (UTC) Received: by ewy19 with SMTP id 19so1915693ewy.17 for ; Mon, 12 Sep 2011 05:12:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:x-priority:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=KCJRd4xGKlVywqbZdGeukSxfKm41NxmRzLAlzCEAyOU=; b=Zlj0SxIhkSPs7l1NzZ9v/Ud4rDZFUPR5e9VsDafDo7+lM6rGpM3Ch1LNJqqF+/F5/Z 1g1q796KPzW4p46ODKFuQvzoKxPJ7WZlYwKbcGUS0XZ7XG4RUKj3lFaLlOouUCl3KLwf XoypYFhlLuDcg8LX9uww8OkhyFyUZEbZULmss= Received: by 10.14.10.212 with SMTP id 60mr1421069eev.188.1315829542428; Mon, 12 Sep 2011 05:12:22 -0700 (PDT) Received: from filippo.sironi.dynamic.micro.elet.polimi.it (micro.elet.polimi.it [131.175.127.118]) by mx.google.com with ESMTPS id w19sm18440287eeh.6.2011.09.12.05.12.20 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Sep 2011 05:12:21 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=us-ascii From: Filippo Sironi X-Priority: 3 In-Reply-To: <20110912111741.298340@gmx.net> Date: Mon, 12 Sep 2011 14:12:19 +0200 Content-Transfer-Encoding: 7bit Message-Id: References: <20110912094842.251380@gmx.net> <9B13644B-F61E-4761-8C4F-E9E33F6E82B8@gmail.com> <20110912111741.298340@gmx.net> To: freebsd-hackers@freebsd.org X-Mailer: Apple Mail (2.1244.3) Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 12:12:24 -0000 Thanks a lot guys, it didn't even think about the tty problem... shame on me, I should have read the man pages. :( Filippo From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 12:14:06 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37F531065672 for ; Mon, 12 Sep 2011 12:14:06 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id A94B38FC1B for ; Mon, 12 Sep 2011 12:14:05 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1R35Oj-0007Kh-H5 for freebsd-hackers@freebsd.org; Mon, 12 Sep 2011 14:14:01 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Sep 2011 14:14:01 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 Sep 2011 14:14:01 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Mon, 12 Sep 2011 14:13:44 +0200 Lines: 21 Message-ID: References: <4E5CEF79.7070508@freebsd.org> <4E5D82FC.2020909@freebsd.org> <4E5E2D01.3000400@freebsd.org> <4E5E3895.4090400@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110907 Thunderbird/6.0.1 In-Reply-To: <4E5E3895.4090400@freebsd.org> X-Enigmail-Version: 1.1.2 Subject: Re: 9-beta1 installer - partition editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 12:14:06 -0000 Unfortunately, I continue to have problems with the partitioner part of the installer in the BETA2 image. See the (unchanged) problem screenshots here: http://ivoras.imgur.com/freebsd_installer_2 See also the screenshots of the entire process here (on BETA1): http://ivoras.imgur.com/installer__partitioner I am no longer trying to create a swap partition but still: 1) I cannot proceed without specifying a root partition 2) I cannot specify the root partition (the dialog ignores it). If this doesn't get solved, it makes FreeBSD uninstallable in this case. There may be some kind of interference between the existing MBR scheme and the operations that the installer attempts to do. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 12:19:06 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 908271065672 for ; Mon, 12 Sep 2011 12:19:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 616F88FC18 for ; Mon, 12 Sep 2011 12:19:06 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id EB26346B09; Mon, 12 Sep 2011 08:19:05 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7AA068A02E; Mon, 12 Sep 2011 08:19:05 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Mon, 12 Sep 2011 08:19:04 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <023BD0FF-053C-4DCB-81EA-5D69B2411819@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109120819.05109.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 12 Sep 2011 08:19:05 -0400 (EDT) Cc: Filippo Sironi , Riccardo Cattaneo Subject: Re: Kernel timers infrastructure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 12:19:06 -0000 On Monday, September 12, 2011 4:42:40 am Filippo Sironi wrote: > This is what I wrote for FreeBSD 7.2 and it does not work: callout_reset() is always going to return false here as you are never rescheduling an existing callout (it is either idle or has already fired each time you invoke callout_reset()). However, you are calling uprintf() from the kernel softclock thread and that thread is not attached to your tty, so the uprintf() is going to nowhere. Just use a regular printf and you will get your "Hello, World!" output once a second. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 12:47:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0848A106566C; Mon, 12 Sep 2011 12:47:37 +0000 (UTC) (envelope-from aduane@juniper.net) Received: from exprod7og105.obsmtp.com (exprod7og105.obsmtp.com [64.18.2.163]) by mx1.freebsd.org (Postfix) with ESMTP id 6C3BE8FC28; Mon, 12 Sep 2011 12:47:35 +0000 (UTC) Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKTm3/Zuunad2q5uT1HgN3LaAcd6vN+5BJ@postini.com; Mon, 12 Sep 2011 05:47:36 PDT Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.83.0; Mon, 12 Sep 2011 05:46:17 -0700 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Mon, 12 Sep 2011 08:46:16 -0400 From: Andrew Duane To: John Baldwin , "freebsd-arch@freebsd.org" Date: Mon, 12 Sep 2011 08:46:15 -0400 Thread-Topic: Soliciting opinions on an extension of the bootinfo structure Thread-Index: Acxu7If3eeG5YhC2RxiKwSeS4k5V0ACXT73Q Message-ID: References: <4E6940D3.4070801@freebsd.org> <201109090832.20770.jhb@freebsd.org> In-Reply-To: <201109090832.20770.jhb@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-hackers@freebsd.org" , Peter Grehan , Peter Wemm Subject: RE: Soliciting opinions on an extension of the bootinfo structure X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 12:47:37 -0000 Since this has turned out to be a more contentious idea than I thought, and= the upcoming FDT work will probably remove the need for it at all, I'm wit= hdrawing the idea. Although our current code uses such a platform extension= structure, we can make do with either metadata or environment variables fo= r the time being. =A0................................... Andrew Duane Juniper Networks o=A0=A0=A0+1 978 589 0551 m=A0 +1 603-770-7088 aduane@juniper.net =A0 -----Original Message----- From: John Baldwin [mailto:jhb@freebsd.org]=20 Sent: Friday, September 09, 2011 8:32 AM To: freebsd-arch@freebsd.org Cc: Peter Wemm; Peter Grehan; freebsd-hackers@freebsd.org; Andrew Duane Subject: Re: Soliciting opinions on an extension of the bootinfo structure On Thursday, September 08, 2011 6:48:19 pm Peter Wemm wrote: > On Thu, Sep 8, 2011 at 3:25 PM, Peter Grehan wrote: > >> I'm proposing an extension framework for the bootinfo structure used > >> to pass information from the bootstrap/loader to the kernel. Although > >> I'm only proposing this for the MIPS bootinfo, it's completely > >> applicable to any of them. > >> > >> What I propose is adding an optional platform extension structure: > >> bootinfo_pext, surrounded by #ifdef BOOTINFO_PEXT > > > > Any reason not to put the vendor bits into another piece of loader=20 metadata > > ? That seems the extensible way to add additional info from the loader, > > rather than extending bootinfo (as was the case pre-loader days). > > > > later, >=20 > It sounds like they're not using loader, which is probably a > reasonable thing for their environment. That doesn't stop you from adding metadata to the kernel. It is just an ar= ray=20 of variable length blobs appended after 'end'. Any boot loader can support adding metadata. --=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 13:40:52 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 621DD106564A for ; Mon, 12 Sep 2011 13:40:52 +0000 (UTC) (envelope-from bsdlisten@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id AA5858FC12 for ; Mon, 12 Sep 2011 13:40:51 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so1675630bkb.13 for ; Mon, 12 Sep 2011 06:40:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:user-agent:x-mailer:mime-version :content-type; bh=pPo4xp2j5sOk9xjF8Dye2vm8Lj03Zmh8uuXqbR1qTf0=; b=wzzlXbCBmTSKt8UaZoeXgdrXeQh2cLKU5HKNZSGyhmW83R3zTNJ77J7uYn+Y0noHVt SLazL2CmbIvEXylbO0+0HtzTDfxHhQ7T4Q8mpDhyGouZVZvR0WAJcMcPRdLWx3JwC4Ra a1wcuUT3zHr3FAy7mWs4Q/a173GGEvzjJJFEk= Received: by 10.204.132.212 with SMTP id c20mr28616bkt.352.1315833222380; Mon, 12 Sep 2011 06:13:42 -0700 (PDT) Received: from debiand1.localdom.ain ([89.47.83.116]) by mx.google.com with ESMTPS id zw12sm6110922bkb.10.2011.09.12.06.13.39 (version=SSLv3 cipher=OTHER); Mon, 12 Sep 2011 06:13:40 -0700 (PDT) Date: Mon, 12 Sep 2011 16:13:53 +0300 From: Rares Aioanei To: freebsd-hackers@freebsd.org Message-ID: <20110912161353.257402c2@debiand1.localdom.ain> User-Agent: my user agent X-Mailer: my x-mailer Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/XRTa5uPiIpCGnfupnMh2Rnx" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Typo in the 9.0 beta 2 installer X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 13:40:52 -0000 --MP_/XRTa5uPiIpCGnfupnMh2Rnx Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline As seen in the screenshot, it says "resovler" instead of "resolver". Hope this is the appropriate mailing list. Regards, -- Rares Aioanei --MP_/XRTa5uPiIpCGnfupnMh2Rnx-- From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 15:23:00 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 080271065670 for ; Mon, 12 Sep 2011 15:23:00 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id B9A938FC08 for ; Mon, 12 Sep 2011 15:22:59 +0000 (UTC) Received: by gxk28 with SMTP id 28so3240740gxk.13 for ; Mon, 12 Sep 2011 08:22:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=/5MCuNE9wiWVuDRPf+rLhnEbA+XKp+yhE/+2WnGQwF0=; b=Km8xqL5sMPNqNKoRp76WSz52I3YD1NNMZhlorITu19bFLidh7C7mNNqBGNqfQrHLRR VnwzYe0kP7/+XcOB2UU2sZMi942LonlEbWD2khEh/CLH+o3YPDjXODLFZS2COCmznmby bPsju7sHKR+Ip0C0KyeIpmeT+0pEh1vD1WHEI= Received: by 10.231.60.76 with SMTP id o12mr7386125ibh.83.1315840978861; Mon, 12 Sep 2011 08:22:58 -0700 (PDT) Received: from [192.168.20.56] (c-24-6-49-154.hsd1.ca.comcast.net [24.6.49.154]) by mx.google.com with ESMTPS id el2sm22293784ibb.10.2011.09.12.08.22.57 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 12 Sep 2011 08:22:57 -0700 (PDT) References: <20110912161353.257402c2@debiand1.localdom.ain> In-Reply-To: <20110912161353.257402c2@debiand1.localdom.ain> Mime-Version: 1.0 (iPhone Mail 8L1) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Message-Id: <0CB85C65-7163-4BFE-B31E-A48BD6521CD7@gmail.com> X-Mailer: iPhone Mail (8L1) From: Garrett Cooper Date: Mon, 12 Sep 2011 08:22:52 -0700 To: Rares Aioanei Cc: "freebsd-hackers@freebsd.org" Subject: Re: Typo in the 9.0 beta 2 installer X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 15:23:00 -0000 On Sep 12, 2011, at 6:13 AM, Rares Aioanei wrote: > As seen in the screenshot, it says "resovler" instead of "resolver". Hope t= his is the appropriate mailing list. Already fixed on head. Thanks, -Garrett= From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 16:28:37 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 406881065673; Mon, 12 Sep 2011 16:28:37 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from adsum.doit.wisc.edu (adsum.doit.wisc.edu [144.92.197.210]) by mx1.freebsd.org (Postfix) with ESMTP id 10E428FC0A; Mon, 12 Sep 2011 16:28:36 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth1.wiscmail.wisc.edu by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0LRF00L064FONZ00@smtpauth1.wiscmail.wisc.edu>; Mon, 12 Sep 2011 11:28:36 -0500 (CDT) Received: from wanderer.tachypleus.net (AAnnecy-157-1-99-204.w90-4.abo.wanadoo.fr [90.4.178.204]) by smtpauth1.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0LRF007KP4FIV940@smtpauth1.wiscmail.wisc.edu>; Mon, 12 Sep 2011 11:28:32 -0500 (CDT) Date: Mon, 12 Sep 2011 18:28:29 +0200 From: Nathan Whitehorn In-reply-to: To: Ivan Voras Message-id: <4E6E332D.8030404@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=90.4.178.204 X-Spam-PmxInfo: Server=avs-9, Version=5.6.1.2065439, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.9.12.161814, SenderIP=90.4.178.204 References: <4E5CEF79.7070508@freebsd.org> <4E5D82FC.2020909@freebsd.org> <4E5E2D01.3000400@freebsd.org> <4E5E3895.4090400@freebsd.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110905 Thunderbird/6.0.1 Cc: freebsd-hackers@freebsd.org Subject: Re: 9-beta1 installer - partition editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 16:28:37 -0000 On 09/12/11 14:13, Ivan Voras wrote: > Unfortunately, I continue to have problems with the partitioner part of > the installer in the BETA2 image. See the (unchanged) problem > screenshots here: > > http://ivoras.imgur.com/freebsd_installer_2 > > See also the screenshots of the entire process here (on BETA1): > > http://ivoras.imgur.com/installer__partitioner > > I am no longer trying to create a swap partition but still: > > 1) I cannot proceed without specifying a root partition > 2) I cannot specify the root partition (the dialog ignores it). > > If this doesn't get solved, it makes FreeBSD uninstallable in this case. > There may be some kind of interference between the existing MBR scheme > and the operations that the installer attempts to do. > This was resolved earlier -- you cannot install onto just MBR without a bsdlabel. This has never been supported, and worked only by accident before. *As it tells you* you need to create sub-partitions. -Nathan From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 16:44:57 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 265201065673 for ; Mon, 12 Sep 2011 16:44:57 +0000 (UTC) (envelope-from mohacsi@niif.hu) Received: from mail.ki.iif.hu (mail.ki.iif.hu [IPv6:2001:738:0:411::241]) by mx1.freebsd.org (Postfix) with ESMTP id A68D88FC0C for ; Mon, 12 Sep 2011 16:44:56 +0000 (UTC) Received: from cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [193.225.14.182]) by mail.ki.iif.hu (Postfix) with ESMTP id A58A887744 for ; Mon, 12 Sep 2011 18:44:55 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at cirkusz.lvs.iif.hu Received: from mail.ki.iif.hu ([IPv6:::ffff:193.6.222.241]) by cirkusz.lvs.iif.hu (cirkusz.lvs.iif.hu [::ffff:193.225.14.72]) (amavisd-new, port 10024) with ESMTP id LCU2yRnYlx+s for ; Mon, 12 Sep 2011 18:44:53 +0200 (CEST) Received: by mail.ki.iif.hu (Postfix, from userid 9002) id 4D23587733; Mon, 12 Sep 2011 18:44:53 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.ki.iif.hu (Postfix) with ESMTP id 4B96B87721 for ; Mon, 12 Sep 2011 18:44:53 +0200 (CEST) Date: Mon, 12 Sep 2011 18:44:53 +0200 (CEST) From: Mohacsi Janos X-X-Sender: mohacsi@mignon.ki.iif.hu To: freebsd-hackers@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Subject: 9.0-beta1 updates X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 16:44:57 -0000 Dear All, Are there any plan to generate update packages for FreeBSD 9.0-BETA(1,2) to be used for freebsd-update(8)? Thanks. Janos Mohacsi From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 18:00:00 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFCDD1065674; Mon, 12 Sep 2011 18:00:00 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 63F658FC08; Mon, 12 Sep 2011 18:00:00 +0000 (UTC) Received: by ywp17 with SMTP id 17so1263044ywp.13 for ; Mon, 12 Sep 2011 10:59:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=8jOrINVM/EtLtm2sCN0IuOqW5h4VWfmpIuajzh8Yipc=; b=r/hGfCmE2l8f2Tbmc/IHQyDoPSRMJvjhSMER5Qn6+OJPa1skXbW/rfwfujNH6OtZz1 OUuWlyg4sUgRhaJm/Rdlf0/xiPGjs6njxhDUe1Efycbt6iY4xS3Xw9Bq44ZEXXu6mOuq +QAQoBQxT0/oo2JgIveHjj3spQuY4FzlY4jqc= Received: by 10.101.176.12 with SMTP id d12mr4272235anp.100.1315850399170; Mon, 12 Sep 2011 10:59:59 -0700 (PDT) MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.100.190.6 with HTTP; Mon, 12 Sep 2011 10:59:19 -0700 (PDT) In-Reply-To: <4E6E332D.8030404@freebsd.org> References: <4E5CEF79.7070508@freebsd.org> <4E5D82FC.2020909@freebsd.org> <4E5E2D01.3000400@freebsd.org> <4E5E3895.4090400@freebsd.org> <4E6E332D.8030404@freebsd.org> From: Ivan Voras Date: Mon, 12 Sep 2011 19:59:19 +0200 X-Google-Sender-Auth: a0h2EYWtTu2BKcjg2RlXEx7KxDI Message-ID: To: Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 Cc: freebsd-hackers@freebsd.org Subject: Re: 9-beta1 installer - partition editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 18:00:00 -0000 On 12 September 2011 18:28, Nathan Whitehorn wrote: > This was resolved earlier -- you cannot install onto just MBR without a > bsdlabel. This has never been supported, and worked only by accident before. > *As it tells you* you need to create sub-partitions. Hi, I'll again note that it should be supported because a) there's no technical reason not to and b) this is how every other OS works. But I'll leave it at that, maybe the users won't mind. But other than that, it might be that I just don't get the workflow it's supposed to implement. Can you point out to me on these screenshots: http://ivoras.imgur.com/freebsd_installer_2 (or on the other set), what option on what screen (i.e. which screenshot) should I choose to create bsdlabels? From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 18:48:39 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A34261065673 for ; Mon, 12 Sep 2011 18:48:39 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 661CD8FC15 for ; Mon, 12 Sep 2011 18:48:39 +0000 (UTC) Received: by qyk10 with SMTP id 10so1913870qyk.13 for ; Mon, 12 Sep 2011 11:48:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=j+BiVPCQ1rOUDwF/Q72sEQbOqIC2uxkLIsMRv8bTcSc=; b=cn6ojKBY2CUEwqBtZOjy0ewu6DTr/tAnbkC+HHVODb5qGFOK14vbjv1prHHqOEGPDn e4tW2UM4Bc9LzVcJ/5Vv8H3oBMziudn+F0pgCgqN1ebFaQ//PQrRjwOleCOa6Is5p+7x e19TeFF9fo1QVE3gt9y7VOiQe6zf4te+uzatE= MIME-Version: 1.0 Received: by 10.224.195.10 with SMTP id ea10mr725519qab.342.1315853318526; Mon, 12 Sep 2011 11:48:38 -0700 (PDT) Received: by 10.224.37.83 with HTTP; Mon, 12 Sep 2011 11:48:38 -0700 (PDT) In-Reply-To: References: Date: Mon, 12 Sep 2011 11:48:38 -0700 Message-ID: From: Garrett Cooper To: Mohacsi Janos Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: 9.0-beta1 updates X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 18:48:39 -0000 On Mon, Sep 12, 2011 at 9:44 AM, Mohacsi Janos wrote: > Dear All, > =A0 =A0 =A0 =A0Are there any plan to generate update packages for FreeBSD > 9.0-BETA(1,2) to be used for freebsd-update(8)? > =A0 =A0 =A0 =A0Thanks. According to the re@ message: no. This is to improve test coverage with the new installer. Thanks, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 19:30:20 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59E58106564A for ; Mon, 12 Sep 2011 19:30:20 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 101458FC08 for ; Mon, 12 Sep 2011 19:30:19 +0000 (UTC) Received: by vxi39 with SMTP id 39so4287636vxi.13 for ; Mon, 12 Sep 2011 12:30:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iQiwYyc135/zWgvMDlO4sgiC90gpF4PHNIffaDlFfsg=; b=OW5L2Yrvgt/HWLXusCTvWMsszWDEHZjLxW8eeuuwiZSnLMtOlhYH5W4vtoUK+hX4WO 7Qm7h0/LFilJ1lvNEiUvvXe85RHuwuqJg0bh8awn9xn+SJ8/IvaXuvoXg6qXfwMTcvcW GpPciqKmEKoeujPPJrPIElrSeQgw8mGjYajEQ= MIME-Version: 1.0 Received: by 10.52.114.197 with SMTP id ji5mr2082270vdb.217.1315854105166; Mon, 12 Sep 2011 12:01:45 -0700 (PDT) Received: by 10.220.199.194 with HTTP; Mon, 12 Sep 2011 12:01:45 -0700 (PDT) In-Reply-To: References: <4E5CEF79.7070508@freebsd.org> <4E5D82FC.2020909@freebsd.org> <4E5E2D01.3000400@freebsd.org> <4E5E3895.4090400@freebsd.org> <4E6E332D.8030404@freebsd.org> Date: Mon, 12 Sep 2011 12:01:45 -0700 Message-ID: From: Freddie Cash To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 9-beta1 installer - partition editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 19:30:20 -0000 On Mon, Sep 12, 2011 at 10:59 AM, Ivan Voras wrote: > On 12 September 2011 18:28, Nathan Whitehorn > wrote: > > > This was resolved earlier -- you cannot install onto just MBR without a > > bsdlabel. This has never been supported, and worked only by accident > before. > > *As it tells you* you need to create sub-partitions. > > I'll again note that it should be supported because a) there's no > technical reason not to and b) this is how every other OS works. But > I'll leave it at that, maybe the users won't mind. > Well, if you look at the history of BSD Unix and the port to the PC, you'll notice that every other PC-based OS does partitioning wrong. :) Unix partitioning has always been this way: - create partition on disk for OS - create sub-partitions for filesystems And it was that way for many years (decades?) before the PC came along. IBM/MS decided to ignore the huge history of computers and partitioning that came before, instead coming up with the lame-brained "primary partition" MBR scheme with a limit of 4 partitions. Later extending that with the even more lame-brained concept of an "extended partition" and "logical partitions". Don't blame FreeBSD (a member of the BSD family) for following the BSD Unix tradition for partitioning. Thankfully, the GPT partitioning standard removes the distinction between "primary", "extended", and "logical" partitions. Now, a partition is a partition is a partition. It's just too bad that they removed the concept of sub-partitions (bsdlabels) as a multi-boot system now has a giant, messy, table full of top-level partitions, with each OS jumbled together (but, it's much easier to label them all to make it easier to manage). :( -- Freddie Cash fjwcash@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 19:21:54 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BE73106566C for ; Mon, 12 Sep 2011 19:21:54 +0000 (UTC) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 153E58FC17 for ; Mon, 12 Sep 2011 19:21:53 +0000 (UTC) Received: from WildRover.lariat.net (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2] (may be forged)) by lariat.net (8.9.3/8.9.3) with ESMTP id MAA18859 for ; Mon, 12 Sep 2011 12:59:30 -0600 (MDT) Message-Id: <201109121859.MAA18859@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 12 Sep 2011 12:59:31 -0600 To: hackers@freebsd.org From: Brett Glass Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailman-Approved-At: Mon, 12 Sep 2011 19:34:49 +0000 Cc: Subject: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 19:21:54 -0000 Here's a puzzler. I just put FreeBSD 8.1 up on an old (but good) 500 MHz Celeron with half a gig of RAM. Interfaces are classic xl (3Com) and dc (DEC tulip). Works quite nicely except for one quirk: ping times that ought to be positive (no more than 200 ms worst case) are coming out negative! Can't figure out what might be causing this. dmesg output is as follows: Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.1-RELEASE-p2 #5: Fri Apr 15 16:10:53 MST 2011 brett@washington.lariat.net:/usr/obj/usr/src/sys/WASHINGTON i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Family = 6 Model = 6 Stepping = 5 Features=0x183f9ff real memory = 536870912 (512 MB) avail memory = 515813376 (491 MB) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at devic e 0.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 vgapci0: port 0xbc00-0xbc7f mem 0xee800000-0xeeffffff,0xef6f0000-0xef6fffff irq 11 at device 0.0 on pci1 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xdc00-0xdc7f mem 0xefffaf80-0xefffafff irq 11 at devic e 8.0 on pci0 miibus0: on xl0 xlphy0: <3c905C 10/100 internal PHY> PHY 24 on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:01:03:be:8b:c1 xl0: [ITHREAD] dc0: port 0xd800-0xd8ff mem 0xefffa800-0xefffabff irq 12 at device 9.0 o n pci0 miibus1: on dc0 ukphy0: PHY 1 on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:14:bf:5b:f5:ed dc0: [ITHREAD] xl1: <3Com 3c905B-TX Fast Etherlink XL> port 0xd400-0xd47f mem 0xefffaf00-0xefffaf7f irq 9 at device 10.0 on pci0 miibus2: on xl1 xlphy1: <3Com internal media interface> PHY 24 on miibus2 xlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl1: Ethernet address: 00:40:ca:97:13:7a xl1: [ITHREAD] acpi_button0: on acpi0 acpi_button0: enable wake failed atrtc0: port 0x70-0x71 irq 8 on acpi0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff,0xc8800-0xd7fff pnpid ORM0000 on is a0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] Timecounter "TSC" frequency 501141912 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 initialized, divert loadable, nat enabled, rule-based forwarding enabled, default to accept, l ogging disabled load_dn_sched dn_sched PRIO loaded load_dn_sched dn_sched QFQ loaded load_dn_sched dn_sched RR loaded load_dn_sched dn_sched WF2Q+ loaded load_dn_sched dn_sched FIFO loaded ad0: 9787MB at ata0-master UDMA66 Trying to mount root from ufs:/dev/ad0s1a Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) Bump sched buckets to 64 (was 0) xl0: promiscuous mode enabled xl0: promiscuous mode disabled dc0: TX underrun -- increasing TX threshold dc0: TX underrun -- increasing TX threshold Any hints here as to what's wrong? --Brett Glass From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 12 21:53:41 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5E4D106566B for ; Mon, 12 Sep 2011 21:53:41 +0000 (UTC) (envelope-from brett@lariat.net) Received: from lariat.net (lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 60F4D8FC13 for ; Mon, 12 Sep 2011 21:53:41 +0000 (UTC) Received: from WildRover.lariat.net (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2] (may be forged)) by lariat.net (8.9.3/8.9.3) with ESMTP id PAA20860 for ; Mon, 12 Sep 2011 15:53:38 -0600 (MDT) Message-Id: <201109122153.PAA20860@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Mon, 12 Sep 2011 15:53:39 -0600 To: hackers@freebsd.org From: Brett Glass In-Reply-To: <14112_1315854090_4E6E570A_14112_184_1_D9B37353831173459FDA A836D3B43499C803FA06@WADPMBXV0.waddell.com> References: <201109111852.MAA08146@lariat.net> <14112_1315854090_4E6E570A_14112_184_1_D9B37353831173459FDAA836D3B43499C803FA06@WADPMBXV0.waddell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Mailman-Approved-At: Mon, 12 Sep 2011 23:24:17 +0000 Cc: Subject: RE: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Sep 2011 21:53:41 -0000 More information regarding the odd behavior I'm seeing. Turns out that packets do not even need to leave the machine for it to report large negative ping times, on the order of more than half a second. (See below.) Clearly something is odd about timekeeping in this system (SiS motherboard chipset, PII-generation Celeron but still effectively a "686") which was not a problem when it was running FreeBSD 4.11-RELEASE (as it was before). Any ideas? --Brett Glass # ping localhost PING localhost (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=-0.148 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=-0.151 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=-686.111 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=-0.180 ms 64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.110 ms 64 bytes from 127.0.0.1: icmp_seq=5 ttl=64 time=686.351 ms 64 bytes from 127.0.0.1: icmp_seq=6 ttl=64 time=-686.376 ms 64 bytes from 127.0.0.1: icmp_seq=7 ttl=64 time=0.121 ms 64 bytes from 127.0.0.1: icmp_seq=8 ttl=64 time=-686.402 ms 64 bytes from 127.0.0.1: icmp_seq=9 ttl=64 time=-686.105 ms 64 bytes from 127.0.0.1: icmp_seq=10 ttl=64 time=686.623 ms 64 bytes from 127.0.0.1: icmp_seq=11 ttl=64 time=0.107 ms 64 bytes from 127.0.0.1: icmp_seq=12 ttl=64 time=0.119 ms 64 bytes from 127.0.0.1: icmp_seq=13 ttl=64 time=0.418 ms 64 bytes from 127.0.0.1: icmp_seq=14 ttl=64 time=0.401 ms 64 bytes from 127.0.0.1: icmp_seq=15 ttl=64 time=-0.169 ms 64 bytes from 127.0.0.1: icmp_seq=16 ttl=64 time=0.113 ms 64 bytes from 127.0.0.1: icmp_seq=17 ttl=64 time=0.401 ms 64 bytes from 127.0.0.1: icmp_seq=18 ttl=64 time=-686.117 ms 64 bytes from 127.0.0.1: icmp_seq=19 ttl=64 time=0.115 ms 64 bytes from 127.0.0.1: icmp_seq=20 ttl=64 time=0.111 ms From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 13 03:01:09 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCB5C1065670 for ; Tue, 13 Sep 2011 03:01:09 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 10B3B8FC12 for ; Tue, 13 Sep 2011 03:01:08 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p8D3161j075017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 12 Sep 2011 20:01:07 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p8D316vV075013; Mon, 12 Sep 2011 20:01:06 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA25888; Mon, 12 Sep 11 19:48:18 PDT Date: Tue, 13 Sep 2011 02:48:01 -0700 From: perryh@pluto.rain.com To: fjwcash@gmail.com Message-Id: <4e6f26d1.GZdzm/ZHXJjqFow1%perryh@pluto.rain.com> References: <4E5CEF79.7070508@freebsd.org> <4E5D82FC.2020909@freebsd.org> <4E5E2D01.3000400@freebsd.org> <4E5E3895.4090400@freebsd.org> <4E6E332D.8030404@freebsd.org> In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: 9-beta1 installer - partition editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2011 03:01:09 -0000 Freddie Cash wrote: > Unix partitioning has always been this way: > - create partition on disk for OS > - create sub-partitions for filesystems No, not "always". The very first Unix I ever encountered, AT&T 6th Edition on a PDP-11/34 with RK05 disks, used what FreeBSD has (until recently) called "dangerously dedicated" disks. Ditto the first BSD- derived Unix I used, SunOS 3.5 on a Sun-3/160 with the Xylogics SMD disk controller. Of course there was nothing dangerous about it then, because no one had ever heard of installing more than one OS on any given disk pack or cartridge. (Even the large multi-platter disk packs were small enough that one ordinarily needed multiple packs per OS; there was no way anyone would have wanted to squeeze multiple OS onto a pack.) Prior to the IBM PC-AT -- the first PC to have a hard drive -- how many systems _did_ support multiple installs? From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 13 07:01:41 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C72CD106566C for ; Tue, 13 Sep 2011 07:01:41 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 87CD88FC17 for ; Tue, 13 Sep 2011 07:01:41 +0000 (UTC) Received: from critter.freebsd.dk (critter.freebsd.dk [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id D01305DA6; Tue, 13 Sep 2011 06:44:33 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.5/8.14.5) with ESMTP id p8D6iWdu002637; Tue, 13 Sep 2011 06:44:33 GMT (envelope-from phk@phk.freebsd.dk) To: perryh@pluto.rain.com From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 13 Sep 2011 02:48:01 MST." <4e6f26d1.GZdzm/ZHXJjqFow1%perryh@pluto.rain.com> Content-Type: text/plain; charset=ISO-8859-1 Date: Tue, 13 Sep 2011 06:44:32 +0000 Message-ID: <2636.1315896272@critter.freebsd.dk> X-Mailman-Approved-At: Tue, 13 Sep 2011 11:22:40 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: 9-beta1 installer - partition editor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2011 07:01:41 -0000 In message <4e6f26d1.GZdzm/ZHXJjqFow1%perryh@pluto.rain.com>, perryh@pluto.rain .com writes: >Freddie Cash wrote: > >> Unix partitioning has always been this way: >> - create partition on disk for OS >> - create sub-partitions for filesystems No, it has not. In fact, it is only on PC like hardware that you can reliably share a disk between different mutually competitive operating systems. Most "unix-machines" don't have a concept of what you call partitions, and neither did BSD unix until 386BSD introduced it. Until then: One OS, one disk(-pack|-drive). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 13 12:19:11 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82ABA106564A for ; Tue, 13 Sep 2011 12:19:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 59D1F8FC0A for ; Tue, 13 Sep 2011 12:19:11 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 12A3346B2E; Tue, 13 Sep 2011 08:19:11 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 945EF8A02E; Tue, 13 Sep 2011 08:19:10 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 13 Sep 2011 08:17:42 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110617; KDE/4.5.5; amd64; ; ) References: <201109111852.MAA08146@lariat.net> <14112_1315854090_4E6E570A_14112_184_1_D9B37353831173459FDAA836D3B43499C803FA06@WADPMBXV0.waddell.com> <201109122153.PAA20860@lariat.net> In-Reply-To: <201109122153.PAA20860@lariat.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109130817.42232.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Tue, 13 Sep 2011 08:19:10 -0400 (EDT) Cc: Brett Glass Subject: Re: Negative ping times with FreeBSD 8.1-RELEASE on older Celeron system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2011 12:19:11 -0000 On Monday, September 12, 2011 5:53:39 pm Brett Glass wrote: > More information regarding the odd behavior I'm seeing. Turns out > that packets do not even need to leave the machine for it to > report large negative ping times, on the order of more than half > a second. (See below.) Clearly something is odd about timekeeping > in this system (SiS motherboard chipset, PII-generation Celeron > but still effectively a "686") which was not a problem when it was > running FreeBSD 4.11-RELEASE (as it was before). Any ideas? 4.x didn't support the ACPI timer. I would look at the kern.timecounter sysctls. Maybe try forcing it to use the TSC. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 13 12:19:32 2011 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ADBA1065673; Tue, 13 Sep 2011 12:19:32 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id AC66B8FC25; Tue, 13 Sep 2011 12:19:31 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:2d7d:e6bb:877a:7b03]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id C20DB4AC2D; Tue, 13 Sep 2011 16:19:29 +0400 (MSD) Date: Tue, 13 Sep 2011 16:19:21 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1483956987.20110913161921@serebryakov.spb.ru> To: Andriy Gapon In-Reply-To: <4E6F432E.2000600@FreeBSD.org> References: <1093822073.20110912175151@serebryakov.spb.ru> <4E6E49C0.1030609@FreeBSD.org> <1638258448.20110913135932@serebryakov.spb.ru> <4E6F432E.2000600@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: hackers@FreeBSD.org Subject: Re: Which way for developing multi-commit feature for FreeBSD is proper at these days -- ask for perosnal space on SVN or use git-svn? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Sep 2011 12:19:32 -0000 Hello, Andriy. You wrote 13 =F1=E5=ED=F2=FF=E1=F0=FF 2011 =E3., 15:49:02: >> But I can not figure out how to have git-svn repo which could be >> cloned (and used as point-of-rendezvous) as git repository -- it >> doesn't work "out of box," as I demonstrated in other message :( > There is a certain contradiction in what you tried to do. > git development model is more suitable for pulling than pushing and what = you > wanted to do is more naturally done with pulling than with pushing. After= all, > there must be a person who decides what should be committed to svn, that = person > decides what changes to pull from other developers and how to commit them= to svn. I don't want to commit to svn often (tens of commits), and could do this with svn itself later, without git-svn at all. It is why I don't want to work with FreeBSD svn repo directly -- I will need many commits which are "bad", partial, without meaningful message, etc. :) > You tried to implement the workflow in the opposite direction - each of t= he > developers may decide what he wants to push in the svn-facing repository.= This > doesn't look like a correct workflow to me. I'm the only developer (yet), but with two workstations and each workstation could not see other one (and they both could not be seen from server with "central" repo -- NAT and corporate firewalls with application-level proxies) -- so they could "push" and "pull" to central repository, but not from each other and central repository could not initiate "pull" from them. > If you really want to have some central repository for pushing, then you = can > create another repository. That repository should be bare and should be = used only > for pushing of local changes from the developers. Then, the git-svn meis= ter would > pull changes from that repository. But I haven't thought through this ki= nd of > workflow, especially rebasing the central repository on top of svn change= s. It seems, I need more deep understanding of git model and limitations. It is much more unobvious compared to Mercurial (hg), which seems very natural for me :) > P.S. Is this really a topic for developers@? This is a normal technical > discussion with no secrets from public, so I think that hackers@ would be= quite > appropriate for it. Ok, I've redirected it. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 14 08:42:56 2011 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 377071065674 for ; Wed, 14 Sep 2011 08:42:56 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 00E5D8FC19 for ; Wed, 14 Sep 2011 08:42:56 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:f803:edca:622b:8392]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 9B1BD4AC1C for ; Wed, 14 Sep 2011 12:42:54 +0400 (MSD) Date: Wed, 14 Sep 2011 12:42:45 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <14710700060.20110914124245@serebryakov.spb.ru> To: hackers@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: mdoc(8) files (man files) editor? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2011 08:42:56 -0000 Hello, Hackers. What editor do you use for mdoc(8) / man files? Generic vi[m]/[x]emacs? Is here something special, maybe, kind of WYSIWYG? Constructs which starts at new line, like .Xr and .Nm make editing these files in generic-purpose text editor very uncomfortable, IMHO. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 14 09:33:43 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E60A106566B for ; Wed, 14 Sep 2011 09:33:43 +0000 (UTC) (envelope-from roam@ringlet.net) Received: from erengrad.hoster.bg (erengrad.hoster.bg [77.77.142.9]) by mx1.freebsd.org (Postfix) with ESMTP id D7F9A8FC14 for ; Wed, 14 Sep 2011 09:33:42 +0000 (UTC) Received: from middenheim.hoster.bg (middenheim.hoster.bg [77.77.142.11]) by erengrad.hoster.bg (Postfix) with ESMTP id 3A2B7DD247 for ; Wed, 14 Sep 2011 12:06:56 +0300 (EEST) Received: from straylight.m.ringlet.net (unknown [95.111.66.80]) (Authenticated sender: roam@hoster.bg) by mail.hoster.bg (Postfix) with ESMTP id 56D7A5C0DB for ; Wed, 14 Sep 2011 12:06:31 +0300 (EEST) Received: from roam (uid 1000) (envelope-from roam@ringlet.net) id dae01d by straylight.m.ringlet.net (DragonFly Mail Agent) Wed, 14 Sep 2011 12:06:31 +0300 Date: Wed, 14 Sep 2011 12:06:31 +0300 From: Peter Pentchev To: Lev Serebryakov Message-ID: <20110914090630.GA2922@straylight.m.ringlet.net> Mail-Followup-To: Lev Serebryakov , hackers@FreeBSD.org References: <14710700060.20110914124245@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: <14710700060.20110914124245@serebryakov.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-MailScanner-ID: 56D7A5C0DB.2E22C X-hoster-MailScanner: Found to be clean X-hoster-MailScanner-SpamCheck: not spam, SpamAssassin (cached, score=0.001, required 10, autolearn=disabled, UNPARSEABLE_RELAY 0.00) X-hoster-MailScanner-From: roam@ringlet.net X-hoster-MailScanner-To: hackers@freebsd.org X-Spam-Status: No Cc: hackers@FreeBSD.org Subject: Re: mdoc(8) files (man files) editor? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2011 09:33:43 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 14, 2011 at 12:42:45PM +0400, Lev Serebryakov wrote: > Hello, Hackers. >=20 > What editor do you use for mdoc(8) / man files? Generic vi[m]/[x]emacs? Vim works just fine for me. > Is here something special, maybe, kind of WYSIWYG? >=20 > Constructs which starts at new line, like .Xr and .Nm make editing > these files in generic-purpose text editor very uncomfortable, IMHO. Vim seems to automagically switch into 'nroff mode' and editing is actually quite nice and easy, IMHO. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@FreeBSD.org peter@packetscale.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 I had to translate this sentence into English because I could not read the = original Sanskrit. --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJOcG6SAAoJEGUe77AlJ98TciMP/jEvniG50j1zEvRC3U9bTtAE 121UM8/UEmwyF4E+KMYm8Ym4282tntVk4SAGJZUdmypvfpbriBHDo80S0RAipsvB tWn2IimB/uL9NEJEapHCImA7BmKtpddrOJt8/VZj7RuPI2GCTs3yuoiR7eWiIOBo muFllfgDuTxgWYmJUKGTHQKbd9yVoJb2DCA7VqATLiwT/wjHVpa+Tw4gmcs6WBzU tGSpu5IDo1O217Nn593xcbQDqxPb2izo70zs5hPiT0rE8hX4cdv4tuzMRVJGr9fe MY8noSVTSq1sj+fT+vW4PjzXpcs/Lcq18RLS7RlqKOa4BxEj8kcCWDxR1SaFFikj kmHwSUkGxpcF2t65e3PyihcBnJ5mExhPTLEvPa2/4ggL2/LLoUHLS93q8kWLbCAl 97DH3gGgQGjQ+IuS7rv1iKhiIH5i2uv/KdZ9YSl3aVudQanTMzLfrX2Nq3W4wPx4 xfRQ4ryQzmbj8gOhKpp8N/fuCZH83lRNhGUdKsvwDf0ExfP0hDzho7J2ShGK2dRr B7w5JW81/pHs/yz38cKdRWXL8UY3gQXujFwzCQoHQodhYMd4c2VlYFdQ4UHvuWPP RBZp6gaakCHVMDvUJYaFCfuzxzMR66N8hvHjs/qPjkHmciuMFOpvR9M+DZqBDeJs kDooTO6TEH+O9kvvoAUW =OWQ+ -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 14 14:39:26 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13B11106566C; Wed, 14 Sep 2011 14:39:26 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 010C08FC12; Wed, 14 Sep 2011 14:39:26 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p8EEdPD8031082; Wed, 14 Sep 2011 14:39:25 GMT (envelope-from danger@freefall.freebsd.org) Received: (from danger@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p8EEdPnI031081; Wed, 14 Sep 2011 14:39:25 GMT (envelope-from danger) Date: Wed, 14 Sep 2011 14:39:25 +0000 From: Daniel Gerzo To: hackers@freebsd.org Message-ID: <20110914143925.GA31052@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: stable@freebsd.org, current@freebsd.org Subject: FreeBSD Status Report April - June, 2011 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2011 14:39:26 -0000 FreeBSD Quarterly Status Report - April-June, 2011 Introduction This report covers FreeBSD-related projects between April and June 2011. It is the second of the four reports planned for 2011. Since this quarter, the work is being focused on the next major version of FreeBSD, 9.0, which is to be released in September. Thanks to all the reporters for the excellent work! This report contains 36 entries and we hope you enjoy reading it. Please note that the deadline for submissions covering the period between July and September 2011 is October 15th, 2011. __________________________________________________________________ Projects * Clang replacing GCC in the base system * Fix clang warnings * libarchive, bsdtar, bsdcpio * ZFS pool version 28 FreeBSD Team Reports * ArabBSD * The FreeBSD Foundation Network Infrastructure * DIstributed Firewall and Flow-shaper Using Statistical Evidence (DIFFUSE) * FreeBSD IPv6-only Support * IPv6 RA Handling Improvements * netmap * New ipfw features * TCP User Timeout Option (UTO) Kernel * Intel GPU Driver * OpenAFS port * Overhaul of the mii(4)-subsystem * Status Report for NFS Documentation * FreeBSD June 6th, 2011 Doc Sprint * The FreeBSD Dutch Documentation Project * The FreeBSD Japanese Documentation Project Architectures * FreeBSD on the Sony Playstation 3 * FreeBSD/arm on Marvell Armada XP * FreeBSD/powerpc on AppliedMicro APM86290 * FreeBSD/powerpc64 on IBM pSeries machines * FreeBSD/sparc64 Ports * Chromium * FreeBSD Haskell Ports * KDE-FreeBSD * libvirt networking port * Portbuilder * Ports Collection Miscellaneous * bsd_day(2011) Google Summer of Code * Capsicum adaptation and core libraries * Disk device error counters * Google Summer of Code * nvi-iconv * Replacing the Regular Expression Code __________________________________________________________________ ArabBSD URL: https://sites.google.com/site/arabbsd/ Contact: Mohammed Farrag FreeBSD Awareness, Handbook Translation and FreeBSD Kernel Development Summer Course. Open tasks: 1. FreeBSD Kernel Development Summer Course. __________________________________________________________________ bsd_day(2011) URL: http://bsdday.eu/2011 Contact: Martin Matuska Contact: Gábor Páli The purpose of this one-day event is to gather Central European developers of today's open-source BSD systems to popularize their work and their organizations, and to meet each other in the real life. We would also like to motivate potential future developers and users, especially undergraduate university students to work with BSD systems. This year's BSD-Day will be held in Bratislava, Slovakia at Slovak University of Technology, Faculty of Electrical Engineering and Information Technology on November 5, 2011. Everybody is welcome! Open tasks: 1. Apply. We are looking for you! __________________________________________________________________ Capsicum adaptation and core libraries URL: http://www.cl.cam.ac.uk/research/security/capsicum URL: http://wiki.FreeBSD.org/SOC2011IlyaBakulin Contact: Ilya Bakulin Some applications from the base system received sandboxing support, current task is to adapt lightweight resolver daemon for using it in sandboxes -- this fixes problems with applications that need to convert IP addresses into domain names while in sandbox. Open tasks: 1. Add sandboxing to even more applications in the base system. 2. Help Jonathan Anderson and Robert Watson to merge FreeBSD-Capsicum into FreeBSD-HEAD. __________________________________________________________________ Chromium URL: http://www.chromium.org/Home URL: http://trillian.chruetertee.org/chromium Contact: Chromium on FreeBSD Team During the last quarter we have been keeping the Chromium browser up to date, with new major releases being imported into the Ports Collection the same day as the upstream release. As time passes by, more patches are incorporated or otherwise became obsolete by virtue of upstream code cleanups. Version 13 is already available from the Chruëtertee repository, with 70 patches less than version 12. __________________________________________________________________ Clang replacing GCC in the base system URL: http://wiki.FreeBSD.org/BuildingFreeBSDWithClang URL: http://wiki.FreeBSD.org/PortsAndClang Contact: Dimitry Andric Contact: Roman Divacky Contact: Brooks Davis Contact: Pawel Worach We imported newer snapshot of clang/llvm. This features quite a lot of goodies. Most notably there's a new register allocator that brings much better runtime performance. If you did a performance evaluation of clang/llvm in the past now it's the time to rerun it with the new register allocator! There was some progress on Mips and PowerPC in addition to the usual influx of improvements on ARM, i386 and amd64. We've managed to get clang compiled arm kernel booting. ARM world is blocked by FreeBSD using old ARM ABI. We got a buildbot that periodically builds clang/llvm on FreeBSD and FreeBSD (amd64 and i386) using clang/llvm, including booting the resulting image. We ran a few ports exp runs and got many ports bugs fixed so right now we're able to build more than 15000 ports with clang. We expect this number to grow rapidly as the problems are mostly trivial. Open tasks: 1. Fix your ports. 2. Performance evaluate the new clang/llvm. 3. Fix clang warnings in src. 4. Implement proper support for cross compiling. __________________________________________________________________ Disk device error counters URL: http://wiki.FreeBSD.org/Disk%20device%20error%20counters Contact: Oleksandr Dudinskyi Currently, I work on schedule, I printed the information of disk error in utility iostat option -E. While only displays five types of errors. Further analysis will give me the opportunity to identify other types of disk errors. Open tasks: 1. Search other type of error and the place of their registration. 2. Maybe find a better place registration of errors than xpt_done(). __________________________________________________________________ DIstributed Firewall and Flow-shaper Using Statistical Evidence (DIFFUSE) URL: http://caia.swin.edu.au/urp/diffuse/ URL: http://caia.swin.edu.au/urp/diffuse/downloads.html Contact: Sebastian Zander Contact: Grenville Armitage DIFFUSE is a system enabling FreeBSD's IPFW firewall subsystem to classify IP traffic based on statistical traffic properties. With DIFFUSE, IPFW computes statistics (such as packet lengths or inter-packet time intervals) for observed flows, and uses ML (machine learning) to classify flows into classes. In addition to traditional packet inspection rules, IPFW rules may now also be expressed in terms of traffic statistics or classes identified by ML classification. This can be helpful when direct packet inspection is problematic (perhaps for administrative reasons, or because port numbers do not reliably identify applications). DIFFUSE also enables one instance of IPFW to send flow information and classes to other IPFW instances, which then can act on such traffic (e.g. prioritise, accept, deny, etc.) according to its class. This allows for distributed architectures, where classification at one location in your network is used to control fire-walling or rate-shaping actions at other locations. The DIFFUSE prototype is a set of patches for FreeBSD-CURRENT that can be downloaded from the project's web site. The web site also contains a more comprehensive introduction, as well as links to related work and documentation. In July 2011, we released DIFFUSE v0.4. This release contains a number of bug fixes and new features. Most notably we improved the functionality of the tools used for training classification models, and performing offline analysis. DIFFUSE v0.4 is the last release, as the DIFFUSE project has concluded. However, we may release bug fixes in the future if necessary. __________________________________________________________________ Fix clang warnings Contact: Ben Laurie In order to assist with the process of moving away from gcc, while I learn the ropes of being a contributor, I am systematically fixing clang warnings, so we can turn on -Werror again. Down from > 42,000 warnings at the end of May to < 9,000 warnings now. Open tasks: 1. Always happy if someone else finds and fixes a warning! __________________________________________________________________ FreeBSD Haskell Ports URL: http://wiki.FreeBSD.org/Haskell URL: https://github.com/freebsd-haskell/freebsd-haskell/ URL: http://haskell.org/mailman/listinfo/freebsd-haskell/ Contact: Gábor János PÁLI Contact: Ashish SHUKLA Contact: Giuseppe Pilichi We are proud to announce that the FreeBSD Haskell Team has committed Haskell Platform 2011.2.0.1 to the FreeBSD Ports Collection, as well as updated existing ports to their latest stable versions. Apart from the ports officially available there, many ports (Snap web framework, Leksah, and their dependencies) are still waiting to be added. Any users who like to get early access to them, please refer to the instructions at our development repository. Open tasks: 1. Update Haskell Platform (along with GHC) to 2011.4.0.0 as soon as it gets out. 2. Add more ports to the Ports Collection. 3. Create a port for Happstack. 4. Create a port for gitit. __________________________________________________________________ FreeBSD IPv6-only Support URL: http://www.FreeBSDFoundation.org/project%20announcements.shtml#Bjoern URL: http://www.ixsystems.com/ix/media/freebsd-foundation-and-ixsystems-anno unce-ipv6-only-testing-versions-of-freebsd-and-pc-bsd URL: http://www.FreeBSD.org/ipv6/ipv6only.html URL: http://www.pcbsd.org/IPv6 Contact: Bjoern A. Zeeb As a follow-up work to the no-IP kernel, a FreeBSD IPv6-only prototype kernel was build beginning of 2010. This work was now carried on and merged to mainstream FreeBSD and will be part of the upcoming 9.0-RELEASE allowing for custom no-IPv4 kernels to be built. In addition IPv6 installation and configuration support for FreeBSD and PC-BSD were improved. An IPv6-only kernel and continued efforts to build world without IPv4, like FreeBSD had supported compiling out IPv6 for a long time, will allow easier IPv6 validation work to happen. This will not only help FreeBSD or FreeBSD-derived commercial product builders but we are also hoping to motivate other Open Source projects to test their software for IPv6-readiness on FreeBSD or PC-BSD. We have provided and will continue to provide IPv6-only snapshots for FreeBSD. In IPv6-only PC-BSD snapshots have been released to provide a great Open Source desktop environment to test GUI applications for IPv6-readiness as well. I would like to thank the FreeBSD Foundation and iXsystems for their support of the project, as well as George Neville-Neil for providing review and Kris Moore for helping on the PC-BSD integration and building and providing the PC-BSD snapshots. __________________________________________________________________ FreeBSD June 6th, 2011 Doc Sprint URL: http://wiki.FreeBSD.org/DocSprints URL: http://people.FreeBSD.org/~bcr/doc/sprints/20110606-final.html URL: http://people.FreeBSD.org/~linimon/annotated_prs.docsprint.html URL: http://openhelpconference.com/ Contact: Benedict Reuschling Contact: Dru Lavigne On June 6, the FreeBSD documentation project held a doc sprint where a number of documentation issues were discussed. The sprint took place primarily in IRC channel #bsddocs on EFNet. Notes were taken in an Etherpad document where all participants could concurrently edit them in an easy to use interface. Parallel to the discussion, a number of doc problem reports have been closed. There are still some doc PRs that have been identified that could also be closed, because their original issue was already committed but the PR is still open. This needs to be investigated on a case by case basis. Dru Lavigne brought in her experiences from the Open Help conference that she was attending during the sprint. It would be good to have some FreeBSD documentation people at a future Open Help conference to exchange ideas with other open source documentation projects and how they go about doing their work. The primary discussion focused on the issues that have been talked about at the documentation working group at BSDCan's DevSummit in May. Subjects like converting the documentation repository from CVS to SVN, the move from DocBook SGML to XML-based documentation as well as other formats like RST (re-restructured text), and publication efforts of the handbook in electronic and dead-tree form were thoroughly debated. Overall participation was good, but we would like to have more documentation folks to participate in future sprints. The next sprint is planned before EuroBSDCon 2011 and will be announced in time so that interested people can set aside some time for it. We also plan to include different time zones so that we can have more input from various areas. We hope to establish these kind of sprints on a regular basis to deal with documentation issues that affect the whole community. Thanks to everyone who participated and helped bring some of the issues we talked about forward. Open tasks: 1. Schedule the next documentation sprint before the next EuroBSDCon and include different timezones. 2. Work on the todo items identified during the sprint. 3. Resolve open documentation problem reports identified to be fixed, but still open for some reason. __________________________________________________________________ FreeBSD on the Sony Playstation 3 URL: http://people.freebsd.org/~nwhitehorn/ps3/ Contact: Nathan Whitehorn The FreeBSD Playstation 3 port is now fairly mature and will be included in the 9.0 release, starting with BETA2. Most internal devices, including the USB ports, bluetooth, ethernet, and SATA devices are now supported, and the operating system can be installed to and boot from the internal hard disk. There are several remaining pieces to the port (Wireless, Sound, X11, and the SPUs), which may be interesting projects for those interested in non-PC architectures. Open tasks: 1. Built-in wireless. The 802.11 wireless interface on the Playstation 3 is multiplexed through the wired ethernet MAC and is currently unsupported. 2. The sound hardware is not currently supported. 3. The framebuffer driver does not currently support X11. This would involve writing a simple X11 framebuffer driver to connect to syscons. 4. The synergistic processing units (SPUs) on the Cell processor are not supported yet. They present an interesting model of heterogeneous computing, more suited for full treatment by a UNIX-type kernel than GPGPU computing: each SPU has a concept of user and supervisor mode, as well as interrupts, and can share MMU context with the main CPU cores. As such, they in principle can support a full UNIX process model. __________________________________________________________________ FreeBSD/arm on Marvell Armada XP Contact: Grzegorz Bernacki Contact: Rafal Jaworowski Marvell Armada XP is a complete system-on-chip solution based on Sheeva embedded CPU. These devices integrate up to four ARMv6/v7 compliant Sheeva CPU cores with shared L2 cache. This work is extending FreeBSD/arm infrastructure towards support for recent ARM architecture variations along with a basic set of device drivers for integrated peripherials. Current FreeBSD suppport for Armada XP includes: * Booting via U-Boot bootloader * ARMv6/v7 support * + Reworked CPU indentification scheme + New cache identification scheme + Support for PIPT caches + Reworked PMAP for ARMv6/v7 features * Serial console support (UART) * Interrupt controller * Integrated timers * USB driver attachment * Ethernet controller driver Next steps: * L2 cache support * SMP support * PCI-Express and SATA drivers __________________________________________________________________ FreeBSD/powerpc on AppliedMicro APM86290 Contact: Grzegorz Bernacki Contact: Rafal Jaworowski The APM86290 system-on-chip device is a member of AppliedMicro's PACKETpro family of embedded processors. The chip includes two Power Architecture PPC465 processor cores, which are compliant with Book-E specification of the architecture, and a number of integrated peripherals. This work is extending current Book-E support in FreeBSD towards PPC4xx processors variation along with device drivers for integrated peripherials. Current FreeBSD APM86290 support includes: * Booting via U-Boot bootloader * Support for PPC465 core * L1 cache * Serial console (UART) Next steps: * Interrupt controller * EHCI USB driver attachment * Ethernet controller * Queue Manager/Traffic Manager * L2 cache support __________________________________________________________________ FreeBSD/powerpc64 on IBM pSeries machines URL: svn://svn.FreeBSD.org/base/projects/pseries/ Contact: Nathan Whitehorn Contact: Andreas Tobler The goal of this project is to make FreeBSD running on PAPR compliant machines like the IBM pSeries family. Currently we can boot a POWER7 emulation under a recent qemu snapshot. The boot process stops when trying to find a PIC. The same applies for an IntelliStation-285. (POWER5+). Open tasks: 1. Implement interrupt controller. 2. PCI bus scanning. 3. Drivers, drivers, drivers. 4. Improve memory management. __________________________________________________________________ FreeBSD/sparc64 Contact: Marius Strobl * The iommu(4) driver has been changed to take advantage of the streaming buffers of the host-PCI and host-SBus bridges if present, which in at least some configurations results in a modest performance improvement due to the caching of DMA transactions. As a prerequisite, the bus_dma(9) usage of all drivers compiled as part of the sparc64 GENERIC kernel has been reviewed and fixed and in case of sound(4) and sym(4) at least worked around as necessary in order to be able to use the streaming buffers. Support for this will be merged back to 8-STABLE prior to 8.3-RELEASE. * Following the update of the in-tree binutils to 2.17.50, which now for the first time include support for GNUTLS on sparc64 in the base, support for TLS relocations on sparc64 was added to rtld(1) and enabled in the base GCC and malloc(3). * Support and a workaround necessary for Sun Fire V890 equipped with UltraSPARC-IV was added. Support for these will be merged back to 8-STABLE prior to 8.3-RELEASE. * The schizo(4) driver has been updated to also support the XMITS Fireplane/Safari to PCI-X bridges and a workaround for Casinni/Skyhawk combinations has been added. Chances are that the latter solves the crashes seen when using the the on-board Casinni NICs of Sun Fire V480 equipped with centerplanes other than 501-6780 or 501-6790. These changes have been merged back to 8-STABLE and will be part of 8.3-RELEASE. * As part of the largeSMP project which had the goal of supporting more than 32 CPU cores in FreeBSD several parts of the sparc64 specific code had to be adapted mainly in the assembler bits but as a result now also supports more than 32 CPU cores. * On machines where we do not need to lock the kernel TSB into the dTLB and thus may basically use the entire 64-bit kernel address space, i.e. on machines equipped with UltraSPARC-III+ and greater CPUs, the kernel virtual memory was increased to not be limited by VM_KMEM_SIZE_MAX and VM_KMEM_SIZE_SCALE decreased to 1 allowing kernel to use more memory as for example useful for ZFS. These changes will be merged back to 8-STABLE prior to 8.3-RELEASE. * The shortcut taken in the code responsible for flushing user mappings from the TLBs of UltraSPARC-III and greater CPUs turned out to not scale well on MP-systems with more than 8 CPU cores and thus was re-written. As a result it now scales up to at least 16-way machines. These changes will be merged back to 8-STABLE prior to 8.3-RELEASE. __________________________________________________________________ Google Summer of Code URL: http://wiki.FreeBSD.org/SummerOfCode2011 Contact: Brooks Davis Contact: Robert Watson We are happy to be participating in our 7th Google Summer of Code. After the mid-term evaluation we have 15 projects working towards the final evaluation. You can see the latest status on student's individual wiki pages or by subscribing to the soc-status mailing list. __________________________________________________________________ Intel GPU Driver URL: http://wiki.FreeBSD.org/Intel_GPU Contact: Konstantin Belousov The FreeBSD Foundation sponsored project to port the Linux kernel-mode driver for Intel GPU progressed to the point where some machines can use Xorg with ddx driver from the git head and latest Mesa. On my test machine I was able to run uhexen2 and ioquake3. Nonetheless, the driver is still in the early stages of debugging. Read the wiki page for more details, guidelines on installation and initial bug analysis. Main efforts right now are directed on getting the required VM changes into the base system, ideally before 9.0 is released. __________________________________________________________________ IPv6 RA Handling Improvements Contact: Hiroki Sato ICMPv6 Router Advertisement (RA) message is a part of IPv6 Neighbor Discovery Protocol in RFC 4861 and takes an important role in IPv6 basic functionality. FreeBSD supports it in the kernel, and the rtadvd(8) and rtsold(8) programs derived from KAME project handle it in userland. This small project aims to improve the current RA handling by removing limitations and adding new functionality found in the latest RFCs. Changes committed are as follows: * FreeBSD now supports RA receiving even if net.inet6.ip6.forwarding=1 and enabling/disabling the receiving in a per-interface basis. The traditional "host" and "router" node model in IPv6 RFCs is translated into a concept of "RA-receiving interfaces" and "RA-sending interfaces" in FreeBSD 9.0 or later, not depending only on system-wide IP forwarding capability. This is useful for a system with multiple IPv6-capable interfaces (such as a customer-edge router) which require SLAAC (Stateless Address Autoconfiguration) feature described in RFC 4862. * The rtadvd(8) and rtsold(8) programs now support IPv6 Router Advertisement Options for DNS Configuration in RFC 6106. This enables updating /etc/resolv.conf by using RAs. * The rtadvd(8) daemon now supports dynamically-added/removed interfaces. Although it was needed that all of RA-sending interfaces exist before the daemon was invoked, the new version no longer requires it. When a new interface arrived, it will be configured on the fly. * The rtadvctl(8) utility has been added. This displays RA-sending status on each interface and provides a way to control the daemon. This utility makes system administration much easier. All of the changes described above have already been committed to 9-CURRENT and a part of them will be merged to 8-STABLE. __________________________________________________________________ KDE-FreeBSD URL: FreeBSD.kde.org URL: http://dot.kde.org/2011/06/29/platform-frameworks-kde-hackers-meet-swit zerland URL: http://blogs.FreeBSDish.org/avilla/2011/06/14/call-for-tests-kde-pim-4- 6-0 URL: http://FreeBSD.kde.org/area51.php Contact: KDE FreeBSD Alberto Villa and Raphael Kubo da Costa went to Randa, Switzerland, to attend, respectively, the KDE Multimedia/Kdenlive sprint and the Platform 11 sprint. The sprints afforded them the opportunity to form closer bonds with the upstream KDE community, to learn about the future of Qt and KDE and make sure FreeBSD's needs are taken into account. For more information see the article "From Platform to Frameworks -- KDE hackers meet in Switzerland" at dot.kde.org. The KDE on FreeBSD team have continued to improve the experience of KDE and Qt under FreeBSD. The latest round of improvements include: * Qt supports Clang as a compiler The team has also made many releases and upstreamed many fixes and patches. The latest round of releases include: * Qt: 4.7.3 * KDE: 4.6.3; 4.6.4; 4.6.5 * Amarok: 2.4.1 * Digikam (and KIPI-plugins): 1.9.0 Further testing is requested for KDE PIM 4.6.0 and Calligra 2.3.72 before the ports are committed. To test the ports please visit Alberto Villa's call for test and area51. The team is always looking for more testers and porters so please visit us at kde-freebsd@kde.org and our homepage. Open tasks: 1. Testing KDE PIM 4.6.0. __________________________________________________________________ libarchive, bsdtar, bsdcpio URL: http://code.google.com/p/libarchive Contact: Tim Kientzle Contact: Michihiro Nakajima Libarchive, bsdtar and bsdcpio in 9-CURRENT have been updated to version 2.8.4 (thanks to mm@FreeBSD.org) and bsdtar now supports extracting XAR and RPM archive formats. There is ongoing development in trunk with many improvements including support for new formats both on the read (e.g. cab, lha, rar) and write parts (e.g. iso9660, xar). __________________________________________________________________ libvirt networking port URL: http://www.libvirt.org/ Contact: Jason Helfman Contact: Daniel P. Berrange Libvirt, a Toolkit to interact with virtualization capabilities, has been ported to FreeBSD, however the networking capabilities have been disabled as they are incompatible with FreeBSD. Libvirt currently supports connecting to many types of hypervisors, however it can be a far more useful tool if the networking capabilities were ported to FreeBSD. In contacting Daniel P. Berrange, he was kind enough to advise on what is required to port networking of libvirt to FreeBSD. His response is paraphrased below: There are two aspects to networking in libvirt: * The virtual network driver (in src/network/bridge_driver.c) uses the Linux kernel's native 'bridge' functionality to provide an isolated, or routed, or NATed network connection to guests. There is a bridge device on the host created, and guest TAP devices are added to it. There is no physical ethernet device added to the bridge, and iptables is used to control whether the host OS routes traffic to/from the bridge & physical LAN. Porting bridge and bridge control functionality to FreeBSD would need to be done, and how to nat/routed/isolated guest configs and write a compatible version of bridge_driver.c for FreeBSD. * The host interface driver (in src/inteface/netcf_driver.c) uses the netcf library to manage configuration of host network interfaces to do things like bonding, vlans, bridging and controlling the interfaces availability. The core job is to port netcf to work with FreeBSD. A netcf backend that understands FreeBSD's networking configuration files and calls appropriate tools to bring interfaces online/offline would need to be created. Both these jobs are pretty much independent, so can easily be done in parallel. Open tasks: 1. Port bridge network driver for libvirt. 2. Port netcf driver for libvirt. __________________________________________________________________ netmap URL: http://info.iet.unipi.it/~luigi/netmap/ Contact: Luigi Rizzo netmap is a novel framework to achieve wire-speed packet processing in FreeBSD, while retaining the safety and richness of features provided by the user space environment, and using only standard system calls. With netmap, it takes as little as 70 clock cycles to move one packet between the user program and the wire. As an example, a single core running at 900MHz can generate the 14.8Mpps that saturate a 10GigE interface. This is a 5-10x improvement over the use of a standard device driver. netmap is implemented with a relatively small kernel device driver (less than 2000 lines of code), plus individual network card patches (300-500 lines each; currently supported are Intel 1 and 10 Gbit cards, and RealTek 1 Gbit cards). No special user libraries are needed, although we have a small libpcap-over-netmap which enables the use of existing applications on top of the new API with no source or binary modifications. The netmap home page contains a more detailed description of the project, source code, papers and slides. __________________________________________________________________ New ipfw features URL: http://svnweb.FreeBSD.org/base?view=revision&revision=223666 Contact: Vadim Goncharov The ipfw(4) packet filter now supports call and return rule actions. When a packet matches a rule with the call action, the rule number is saved in the internal stack and rules processing continues from the first rule with specified number (similar to skipto action, but backward jumps are allowed). If later a rule with return action is encountered, the processing returns to the first rule with number greater than the number saved in the internal stack. This makes it possible to organize "subroutines" with rules, e.g. to call one subroutine several times from different places in the ruleset. For more details, see ipfw(8). __________________________________________________________________ nvi-iconv URL: http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1 URL: https://github.com/lichray/nvi2 Contact: Zhihao Yuan This project creates a multibyte aware nvi fork. While most of the userland tools in the FreeBSD base system support multibyte encodings, there is no pure-licensed nvi fork comes with sufficient multibyte encoding (both Unicode and non-Unicode) support prior to this. Currently, functionally, the new nvi is ready for testing. The description is at https://github.com/lichray/nvi2/wiki (the patch is deprecated). I will commit a new one latter. The features dropped from nvi-1.79 are: * Perl and Tcl interpreter supports; * The whole Perl/Tcl/Tk scripting framework; * A third-party gtags support. and the features adopted from nvi-1.81.6 includes: * Multibyte encoding supports (wchar_t + libiconv + libncursesw); * fileencoding and inputencoding options; * Undocumented :vsplit command, which vertically splits the screen. Many known bugs, incomplete code from nvi-devel are fixed. However, I find a serious memory leaking (via valgrind) in the nvi-devel iconv framework. This requires a careful review. Open tasks: 1. Reviews the iconv part and fixes the memory leak. 2. Ex scripts for testing. But it seems that I have no experience on that... 3. File encoding detection. My plan it to detect UTF-16 BOM first, then UTF-8. If all fails, uses locale. UTF-8 BOM is not supported by iconv, and we need to discuss whether we should support it in the editor. __________________________________________________________________ OpenAFS port URL: http://openafs.org URL: http://wiki.FreeBSD.org/afs Contact: Benjamin Kaduk Contact: Derrick Brashear AFS is a distributed network filesystem that originated from the Andrew Project at Carnegie-Mellon University. Since our last report, upstream OpenAFS has updated to a 1.6.0pre6 release candidate, which is available in the FreeBSD Ports Collection. We still expect the upcoming 1.6.0 release to be usable for regular client workloads (though not heavy load). We have also made progress on integration with the bsd.kmod.mk kernel-module-building infrastructure, with a working prototype implementation. Further cleanup and testing is needed before it is ready to be committed. There are several known outstanding issues that are being worked on, but detailed bug reports are welcome at port-freebsd@openafs.org. Open tasks: 1. Update VFS locking to allow the use of disk-based client caches as well as memory-based caches. 2. Track down races and deadlocks that may appear under load. 3. Integrate with the bsd.kmod.mk kernel-module build infrastructure. 4. Eliminate a moderate memory leak from the kernel module. 5. PAG (Process Authentication Group) support is not functional. __________________________________________________________________ Overhaul of the mii(4)-subsystem Contact: Marius Strobl The mii(4)-subsystem has been overhauled and fixes and enhancements from NetBSD/OpenBSD since mii(4) originally has been ported over have been merged. As a result a lot of code duplication and hacks have been removed from the PHY drivers and we are now able again to share the miidevs file with NetBSD. Due to KPI breakages the majority of this work will not be merged back into 8-STABLE and earlier. Additionally shorthand aliases for common media+option combinations as announced by mii(4) have been added to the ifmedia code so that now one can actually supply the media strings found in the dmesg output to ifconfig(8). Support for this will be merged back to 8-STABLE prior to 8.3-RELEASE. __________________________________________________________________ Portbuilder URL: https://github.com/DragonSA/portbuilder URL: https://github.com/DragonSA/portbuilder/blob/0.1.3/README URL: https://github.com/DragonSA/portbuilder/blob/0.1.3/TODO Contact: David Naylor I would like to introduce a project that has been in the works for the last 3 years. From the projects README: A concurrent ports building tool. Although FreeBSD ports supports building a single port using multiple jobs (via MAKE_JOBS), it cannot build multiple ports concurrently. This tool accomplishes just that. Some of its key features: * Concurrent port building * Load control * Top like UI * Persistent builds (by default) Portbuilder originally used threads to control each port at each stage of the build however the required locks resulting in deadlocks, and some ports would not build correctly. To resolve those issues a rewrite was done to use only a single thread, making all locking code redundant. Thanks to the use of kqueue(2) the overhead of managing concurrent port builds is minimal. Further work to reduce that overhead is underway. Portbuilder is installable from ports under ports-mgmt/portbuilder, see the README for usage details. Please note that this is considered BETA quality, that the feature set and API are expected to change, and that portbuilder may crash or fail to behave properly. Open tasks: 1. Wiki page. 2. Testing. 3. See TODO. __________________________________________________________________ Ports Collection URL: http://www.FreeBSD.org/ports/ URL: http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing-ports/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.FreeBSD.org/portmgr/index.html URL: http://blogs.FreeBSDish.org/portmgr/ URL: http://www.twitter.com/freebsd_portmgr/ URL: http://www.facebook.com/group.php?gid=135441496471197 URL: http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-baptis te-daroussin.html URL: http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-julien -laffaye.html URL: http://FreeBSDFoundation.blogspot.com/2011/06/bsdcan-trip-report-thomas -abthorpe.html URL: http://blogs.FreeBSDish.org/portmgr/2011/05/26/thankyoufoundation/ Contact: Thomas Abthorpe Contact: Port Management Team The ports tree slowly moves up closer to 23,000. The PR count still remains at about 1100. In Q2 we added 3 new committers, took in 2 commit bits for safe keeping, and added a new member to portmgr. The Ports Management team have been running -exp runs on an ongoing basis, verifying how base system updates may affect the ports tree, as well as providing QA runs for major ports updates. Of note, -exp runs were done for: * ports/154044, -exp run to update x11-toolkits/open-motif * ports/155269, -exp run to fix problem with base/ports ncurses * ports/155215, -exp run to update gmake, completed by linimon * ports/156575, -exp run to generate a subset of ports in INDEX * ports/155983, -exp run to reroot md5 in /sbin * ports/139116, -exp run to call target "install-rc-script" before "post-install" * ports/155510, -exp run to remove support for pre 7.X * ports/156533, -exp run to patch bsd.apache.mk * ports/152498, -exp run to improve USERS/GROUPS handling * flz has been performing clang -exp runs * erwin performed -exp run for perl 5.12.4 update * pav performed multiple -exp runs for gtk3 Open tasks: 1. Looking for help getting ports to build with clang. 2. Looking for help fixing ports broken on CURRENT. (List needs updating, too) 3. Looking for help with Tier-2 architectures. (List needs updating, too) 4. Most ports PRs are assigned, we now need to focus on testing, committing, and closing. __________________________________________________________________ Replacing the Regular Expression Code URL: http://wiki.FreeBSD.org/G%C3%A1borSoC2011 Contact: Gábor Kövesdán The current regular expression code in libc is quite outdated and does not support wide characters. There are various open source regular expression libraries but replacing the code is not a simple task because there are quite many considerations and requirements. The best candidate is TRE, which is a BSD-licensed, supports wide and multibyte characters, conforms to POSIX and it performs well compared to another available alternatives, so the work has been started with TRE. Apart from the replacement, the plan is to implement heuristical matching, which will speed up the pattern matching significantly. Besides, grep and diff in the base system have been using the GNU regex code, which has a more permissive syntax. It is desired to have a single regex engine in the base system, so the GNU syntax has to be implemented (as an optional feature), as well. So far, a fast string matching algorithm has been added, which is a variant of the Turbo Boyer-Moore algorithm. It has been slightly tuned to support not only literal patterns but patterns containing $^. symbols. This algorithm is used automatically when the pattern makes it possible. Besides, heuristic matching has also been implemented. If the fast matcher cannot be applied directly, it parses the pattern and separates the fixed-length prefix and suffix of the pattern. Then it can be used to locate the possibly matching regions of the text, using a more efficient algorithm than the full regex NFA and the latter only has to be applied to the narrow context that has been located. Open tasks: 1. Implement GNU regex syntax. 2. Add test suite GNU-specific behavior and also add some tests for locale-specific behavior. 3. Test and review the code. Contact the author and check if these improvements can be added to the upstream code so that more people can benefit from this. __________________________________________________________________ Status Report for NFS Contact: Rick Macklem The new NFS client and server are no longer considered experimental and will most likely be the default for FreeBSD 9.0. Included is support for NFSv4.0 as well as NFSv3 and NFSv2. The NFSv4.0 support was tested at a recent NFSv4 Interoperability Bakeathon held at CITI of the University of Michigan. Also tested at the Bakeathon was a basic client implementation of NFSv4.1 which will soon be available as a test patch against the FreeBSD 9.0 kernel sources. If you are interested in testing NFSv4.1, stay tuned to the freebsd-fs@FreeBSD.org mailing list. zkirsch@FreeBSD.org and friends will be taking on a majority of the NFSv4 server work while I concentrate on the client, with hopes that the NFSv4.1 support will mature over the next year or so. I will also be making a patch for an experimental aggressive client side on-disk caching mechanism for NFSv4 I call Packrats available. An announcement about this will be made on freebsd-fs@FreeBSD.org as well. __________________________________________________________________ TCP User Timeout Option (UTO) URL: http://wiki.FreeBSD.org/CatalinNicutar/TCPUTO URL: http://p4web.FreeBSD.org/@md=d&cd=//depot/projects/soc2011/&dw=u&c=kml@ //depot/projects/soc2011/cnicutar_tcputo_8/?ac=83 Contact: Catalin Nicutar Contact: Bjoern Zeeb The goal of the User Timeout option is to allow an application to tweak the time TCP waits for acknowledgements. Using UTO, an application can choose the exact time it is willing to wait for data to be acknowledged. Also, an application can suggest to its peer the time it should wait before dropping the connection (the peer may or may not allow this). As an example, a SSH client can request a large timeout (4 hours) for a connection. After some time the client is disconnected, reconnecting 2 hours later (with the same IP). Due to UTO, the connection should still be alive and any lost data should be retransmitted. Current testing is done on TCP over IPv4. Timeouts can be limited by global sysctls and an application can choose how to send or accept timeout values via socket options. In addition to regression tests, support has been added to telnet, ssh and netcat. Open tasks: 1. Regression tests for TCP over IPv6. 2. Add support to more userland applications. 3. Implement strategies and regression tests to handle and simulate DoS scenarios. __________________________________________________________________ The FreeBSD Dutch Documentation Project URL: http://wiki.FreeBSD.org/DutchDocumentationProject URL: http://p4db.FreeBSD.org/depotTreeBrowser.cgi?FSPC=//depot/projects/docp roj_nl Contact: Remko Lodder Contact: René Ladan During the last period most work went into keeping the Handbook up to date; it is currently up-to-date except for a section on network servers. Other areas being worked on are the FAQ and the web site. The latter two are still a work-in-progress. Open tasks: 1. Volunteers! The best part is that you do not need to be an expert on FreeBSD nor the Dutch language to join, just some enthusiasm and spare time. __________________________________________________________________ The FreeBSD Foundation URL: www.FreeBSDFoundation.org Contact: Deb Goodkin We were a proud sponsor of BSDCan. We also sponsored 6 developers to attend the conference. And, we brought in over $1,000 in donations! The Foundation was also represented at FlourishConf in Chicago, IL and SouthEast LinuxFest in Spartanburg, SC. We acquired a non-exclusive copyright license to the libcxxrt C++ runtime software from PathScale. Sponsored a project to create an IPv6-only version of FreeBSD and PC-BSD. We're pleased announce the addition of Ed Maste to our Board of Directors. Ed has been involved with FreeBSD since 2003. And, has been a committer since 2005. Ed leads the OS team at Sandvine and is responsible for a number of developers who bring enhancements from FreeBSD into Sandvine's OS and contribute their own changes back to FreeBSD. We continued our work on infrastructure projects to beef up hardware for package-building, network-testing, etc. This includes purchasing equipment as well as managing equipment donations. In fact we just placed an order for a 80-core server for SMP performance work. Stop by and visit with us at Ohio LinuxFest, Columbus, OH, on September 10. The work above, as well as many other tasks we do for the project, couldn't be done without donations. Please help us by making a donation or asking your company to make a donation. We would be happy to send marketing literature to you or your company. Find out how to make a donation at http://www.FreeBSDFoundation.org/donate/. Find out more up-to-date Foundation news by reading our blog and Facebook page. __________________________________________________________________ The FreeBSD Japanese Documentation Project URL: http://www.FreeBSD.org/ja/ URL: http://www.jp.FreeBSD.org/doc-jp/ Contact: Hiroki Sato Contact: Ryusuke Suzuki The www/ja and doc/ja_JP.eucJP/books/handbook subtrees have constantly been updated. During this period, many part of out-dated contents in the www/ja subtree were updated to the latest versions in the English counterpart. Thus most of the files in the subtree are already synchronized with www/en at this moment, and this updating work will be finished within this year. For FreeBSD Handbook, translation work for the kernelconfig section was just started. In addition, we are planning to translate the upcoming release announcement because it is also important for Japanese people. Open tasks: 1. Further translation work for outdated and/or non-translated documents in both doc/ja_JP.eucJP and www/ja. __________________________________________________________________ ZFS pool version 28 Contact: Pawel Jakub Dawidek Contact: Martin Matuska ZFS pool version 28 has been merged into 8-STABLE as of June 6, 2011. In addition, several bugfixes and improvements from the Illumos project have been imported. Open tasks: 1. Investigation of ZFS problem reports. __________________________________________________________________ The FreeBSD Project. All rights reserved. From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 14 14:49:08 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EECD51065767 for ; Wed, 14 Sep 2011 14:49:08 +0000 (UTC) (envelope-from schumjs@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id CAFDF8FC16 for ; Wed, 14 Sep 2011 14:49:08 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R3qTX-0000FF-5j for freebsd-hackers@freebsd.org; Wed, 14 Sep 2011 07:30:07 -0700 Date: Wed, 14 Sep 2011 07:30:07 -0700 (PDT) From: John Schumacher To: freebsd-hackers@freebsd.org Message-ID: <1316010607171-4803024.post@n5.nabble.com> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Problem with running simple pthreads program under gdb-7.2 (Invalid selected thread) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Sep 2011 14:49:09 -0000 These replies seemed to dance around the actual issue, I assume this wasn't resolved? I have been seeing this lately in gdb7.2 built from ports, and was curious as to what the real issue was. excerpt: [Thread 803855580 (LWP 100241 IPC UDP Socket) ex ited] error: Invalid selected thread. thread.c:583: internal-error: set_running: Asser tion `tp->state_ != THREAD_EXITED' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] thread.c:583: internal-error: set_running: Asser tion `tp->state_ != THREAD_EXITED' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal] I encountered this in: get_current_frame(~) I don't think the current_inferior changes after a thread exits. Which could be okay, but I've noticed that the thread_info for this particular current_inferior doesn't always exist... Meaning that any time that a current_inferior ptid leads to a NULL thread_info [via find_thread_ptid(~)], we will get hosed on an assert. Any thoughts? -- View this message in context: http://freebsd.1045724.n5.nabble.com/Problem-with-running-simple-pthreads-program-under-gdb-7-2-Invalid-selected-thread-tp4426179p4803024.html Sent from the freebsd-hackers mailing list archive at Nabble.com. From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 03:21:47 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7983E106564A for ; Thu, 15 Sep 2011 03:21:47 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 56F378FC0C for ; Thu, 15 Sep 2011 03:21:47 +0000 (UTC) Received: by pzk36 with SMTP id 36so412627pzk.31 for ; Wed, 14 Sep 2011 20:21:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=moaGSZQYgXM734xpFcswt2BHX92yeB8jLZd9dgLDkrQ=; b=xljVGdvtJU9CyQxFEaKrkzf3WYP0sqs26iERV8hs6lJD41FSuD9K4I9kk3ygpx1g7Z X5Pu3sx4Y0ZctYYC5JGRq2HFECFge4uM3Nj8hO8qVeqGn9hPjZjLq4OraexyQpFODD/z Eu0Y3wG/XaDmMJcCs/Eh+4vJaYx+LX8MMU2vc= MIME-Version: 1.0 Received: by 10.68.27.101 with SMTP id s5mr786809pbg.197.1316055205974; Wed, 14 Sep 2011 19:53:25 -0700 (PDT) Received: by 10.142.12.18 with HTTP; Wed, 14 Sep 2011 19:53:25 -0700 (PDT) Date: Wed, 14 Sep 2011 22:53:25 -0400 Message-ID: From: Arnaud Lacombe To: "K. Macy" Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Hackers Subject: buf_ring(9) API precisions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 03:21:47 -0000 Hi Kip, I've got a few question about the buf_ring(9) API. 1) what means the 'drbr_' prefix. I can guess the two last letter, 'b' and 'r', for Buffer Ring, but what about 'd' and 'r' ? 2) in `sys/sys/buf_ring.h', you defined 'struct buf_ring' as: struct buf_ring { volatile uint32_t br_prod_head; volatile uint32_t br_prod_tail; int br_prod_size; int br_prod_mask; uint64_t br_drops; uint64_t br_prod_bufs; uint64_t br_prod_bytes; /* * Pad out to next L2 cache line */ uint64_t _pad0[11]; volatile uint32_t br_cons_head; volatile uint32_t br_cons_tail; int br_cons_size; int br_cons_mask; /* * Pad out to next L2 cache line */ uint64_t _pad1[14]; #ifdef DEBUG_BUFRING struct mtx *br_lock; #endif void *br_ring[0]; }; Why are you making an MD guess, the amount of padding to fit the size of a cache line, in MI API ? Strangely enough, you did not make this assumption in, say r205488 (picked randomly). Thanks in advance, - Arnaud From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 03:23:33 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13272106566B for ; Thu, 15 Sep 2011 03:23:33 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id C2D538FC1D for ; Thu, 15 Sep 2011 03:23:32 +0000 (UTC) Received: by pzk36 with SMTP id 36so414873pzk.31 for ; Wed, 14 Sep 2011 20:23:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=QqZi2/5X6mK2927Nc/pA9FK9VhbdwzjiqT64h0RqJ9g=; b=SfY/6LHFlsEK087H6ORrWNTnxUY6g/6LnlkKmwFIhFgnRGNfhXRnuzTJZ5PpjcWikz x3ElTNJd4PemXyh8DfdBo05oZM0+/QSxYEwKmqmYnrqRG0yxaEsho5qwygcFMHLiNJ9Q Hz9scTBwClk2JNfc/U37q70QoY63yMKRqVCiU= MIME-Version: 1.0 Received: by 10.68.38.9 with SMTP id c9mr1027744pbk.264.1316057012435; Wed, 14 Sep 2011 20:23:32 -0700 (PDT) Received: by 10.142.12.18 with HTTP; Wed, 14 Sep 2011 20:23:31 -0700 (PDT) In-Reply-To: References: <4D934AF4.9080503@FreeBSD.org> <742085CD-7F6F-4879-9FFD-517EC3203D52@bsdimp.com> <5AF348C8-6AB6-490D-A12E-89A51528F58F@bsdimp.com> Date: Wed, 14 Sep 2011 23:23:31 -0400 Message-ID: From: Arnaud Lacombe To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mdf@freebsd.org, "Robert N. M. Watson" , Dimitry Andric , freebsd-hackers Subject: Re: Include file search path X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 03:23:33 -0000 Hi, On Fri, Jul 8, 2011 at 5:16 PM, Arnaud Lacombe wrote: > Hi, > > On Sat, Jun 25, 2011 at 2:01 PM, Arnaud Lacombe wrot= e: >> Hi, >> >> On Mon, Jun 6, 2011 at 5:37 PM, Arnaud Lacombe wrot= e: >>> Hi, >>> >>> On Tue, May 31, 2011 at 12:23 PM, Warner Losh wrote: >>>> >>>> On May 22, 2011, at 9:48 PM, Arnaud Lacombe wrote: >>>> >>>>> Hi Warner, >>>>> >>>>> On Sat, Apr 2, 2011 at 6:49 PM, Warner Losh wrote: >>>>>> >>>>>> On Apr 2, 2011, at 1:10 PM, Robert N. M. Watson wrote: >>>>>> >>>>>>> On 2 Apr 2011, at 19:47, Warner Losh wrote: >>>>>>> >>>>>>>>> (2) Working clang/LLVM cross-compile of FreeBSD. =A0This seems li= ke a basic >>>>>>>>> =A0requirement to adopt clang/LLVM, and as far as I'm aware that'= s not yet a >>>>>>>>> =A0resolved issue? >>>>>>>> >>>>>>>> 0 work has been done here to my knowledge. =A0The world view for c= lang and our in-tree gcc differ which makes it a challenge. >>>>>>> >>>>>>> That's disappointing. I seem to recall it's more an issue of our bu= ild integration with clang/LLVM than an underlying issue in clang/LLVM? >>>>>> >>>>>> Yes. =A0The problem isn't hard, the cross compile paradigm is just a= little different. >>>>>> >>>>>>>>> We (Cambridge) are currently bringing up FreeBSD on a new soft-co= re 64-bit MIPS platform. =A0We're already using a non-base gcc for our boot= loader work, and plan to move to using clang/LLVM later in the year. =A0Th= e base system seems a bit short on detail when it comes to the above, curre= ntly. >>>>>>>> >>>>>>>> Yes. =A0I've had to add about a dozen changes so far to get close = to building with xdev compilers. =A0A similar number are needed to make it = easy to configure and add systree support, I think. >>>>>>> >>>>>>> Sounds like great progress -- do you think we'll ship 9.0 in a "jus= t works" state with regard to this? >>>>>> >>>>>> I sure hope so. =A0I'd like to have demoable stuff by BSDcan. >>>>>> >>>>> BSDCan has passed, has there been any advance made since that discuss= ion ? >>>> >>>> It is "demonstrable" but not ready to commit to the tree. =A0Needs abo= ut 4 hours of work that I've had trouble scheduling on it due to work getti= ng busier than I expected. >>>> >>> any chances to have a look at the patch or should I wait for the final = commit ? >>> >> ping ? >> > ping ? > ping, Warner ? FWIW, I guess that in 4 months, either you had time to finish the patch, or I could have found to time to complete it myself based on your incomplete version. I'd really be interested to benchmark recent, decent, compiler. Thanks, - Arnaud From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 03:13:22 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57B741065670 for ; Thu, 15 Sep 2011 03:13:22 +0000 (UTC) (envelope-from thinker.li@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1347D8FC08 for ; Thu, 15 Sep 2011 03:13:21 +0000 (UTC) Received: by ywp17 with SMTP id 17so2330549ywp.13 for ; Wed, 14 Sep 2011 20:13:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:date:message-id:to:subject:from:x-mailer:mime-version :content-type:content-transfer-encoding; bh=xj6ThdeeuTBgwoFCGPtAKiszx0M0pJpSrKcTiXTWd1U=; b=x+x3YK0FCvIsIlBPjIIEQhieleTDbk2+UMhocvDnfGqyBgMJnAvqDnA/OYIm8XSmhG JzuDn0m+yxVZ6rPj8SkMuYvVLyViPhM3fHTdOPsi0BQTG92VTiwmbxr1Ie1vBHXXxMVm m4h/RxyzFrhw4tzajGwiKtKUZqbGIsWOILWGI= Received: by 10.236.77.104 with SMTP id c68mr3135129yhe.69.1316054820463; Wed, 14 Sep 2011 19:47:00 -0700 (PDT) Received: from eeebox.branda.to (123-194-52-90.dynamic.kbronet.com.tw. [123.194.52.90]) by mx.google.com with ESMTPS id o21sm2403117yhi.8.2011.09.14.19.46.57 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Sep 2011 19:46:59 -0700 (PDT) Sender: Thinker Li Received: from localhost (localhost [127.0.0.1]) by eeebox.branda.to (8.14.4/8.14.4) with ESMTP id p8F2olgB037409 for ; Thu, 15 Sep 2011 10:50:47 +0800 (CST) (envelope-from thinker@branda.to) Date: Thu, 15 Sep 2011 10:50:47 +0800 (CST) Message-Id: <20110915.105047.104045404.thinker@eeebox.branda.to> To: freebsd-hackers@freebsd.org From: "Thinker K.F. Li" X-Mailer: Mew version 6.2 on Emacs 23.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 15 Sep 2011 03:51:04 +0000 Subject: Thread-local storage issue X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 03:13:22 -0000 Hi Guys, I was in trouble for an issue of TLS implementation of FreeBSD. It is an issue of ld-elf.so actually. If I have a thread-local variable in program, the value of the variable is not consistent after an dlopen(). For example, __thread int var = 50; void modify() { var = 100; } void show() { printf("%d\n", var); } int main(int argc, char * const *argv) { dlopen(...); modify(); show(); } If it is compiled with -fpic, it would print "50" while "100" is expected. (-fpic is required for shared objects) I have send-pr a patch as http://www.freebsd.org/cgi/query-pr.cgi?pr=160721 I need someone to review it. Thanks! From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 08:01:41 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11006106564A for ; Thu, 15 Sep 2011 08:01:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 67CD38FC0C for ; Thu, 15 Sep 2011 08:01:40 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id p8F81UTh019735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Sep 2011 11:01:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4) with ESMTP id p8F81UIr012117; Thu, 15 Sep 2011 11:01:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id p8F81U2Z012116; Thu, 15 Sep 2011 11:01:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 15 Sep 2011 11:01:30 +0300 From: Kostik Belousov To: "Thinker K.F. Li" Message-ID: <20110915080130.GL17489@deviant.kiev.zoral.com.ua> References: <20110915.105047.104045404.thinker@eeebox.branda.to> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WdUsZMUkvvqwUt1b" Content-Disposition: inline In-Reply-To: <20110915.105047.104045404.thinker@eeebox.branda.to> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-hackers@freebsd.org Subject: Re: Thread-local storage issue X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 08:01:41 -0000 --WdUsZMUkvvqwUt1b Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 15, 2011 at 10:50:47AM +0800, Thinker K.F. Li wrote: > Hi Guys, >=20 > I was in trouble for an issue of TLS implementation of FreeBSD. It is > an issue of ld-elf.so actually. If I have a thread-local variable in > program, the value of the variable is not consistent after an > dlopen(). For example, >=20 > __thread int var =3D 50; >=20 > void modify() { > var =3D 100; > } >=20 > void show() { > printf("%d\n", var); > } >=20 > int main(int argc, char * const *argv) { > dlopen(...); > modify(); > show(); > } >=20 > If it is compiled with -fpic, it would print "50" while "100" is > expected. (-fpic is required for shared objects) >=20 > I have send-pr a patch as >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D160721 >=20 > I need someone to review it. I already sent the request to re@ to commit the change. Thanks for the submission. --WdUsZMUkvvqwUt1b Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk5xsNoACgkQC3+MBN1Mb4gIXwCgjjkVsLmsEvbZsNikN8eerka/ EToAnixRF91XSkb9K78g0qq/COy3EUKw =VHws -----END PGP SIGNATURE----- --WdUsZMUkvvqwUt1b-- From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 15:39:41 2011 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4D141065694 for ; Thu, 15 Sep 2011 15:39:41 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 1A9F98FC08 for ; Thu, 15 Sep 2011 15:39:39 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA15113 for ; Thu, 15 Sep 2011 18:27:43 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E72196F.6020107@FreeBSD.org> Date: Thu, 15 Sep 2011 18:27:43 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: hackers@FreeBSD.org X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: topgit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 15:39:41 -0000 Anybody uses topgit for FreeBSD or FreeBSD related development? What's your impressions of it? Any peculiarities in the workflow? -- Andriy Gapon From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 18:50:51 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A92E106566B for ; Thu, 15 Sep 2011 18:50:51 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-vw0-f45.google.com (mail-vw0-f45.google.com [209.85.212.45]) by mx1.freebsd.org (Postfix) with ESMTP id 0689F8FC0A for ; Thu, 15 Sep 2011 18:50:50 +0000 (UTC) Received: by vws17 with SMTP id 17so4968047vws.18 for ; Thu, 15 Sep 2011 11:50:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=a41S7+WOKFpLjo1SkmJTYmEr3zc3AJwj82sXDzv3+XI=; b=w2zEbFCvwy2FPsERFmTcHtOTGVRuJypvjXhJQ7LTHNKnZqfRdvUGAJvRmQt1P+Clei Ht6AG2gVSTVIVGYY5HuW3l7n6s3j3tkx7wab7Dvd0axBRQihIpZS6DeydxwhkovSKl5x NSBG/JaMpgQr03ZSdadqFNrsQXvAUCebYQyHA= MIME-Version: 1.0 Received: by 10.52.36.101 with SMTP id p5mr228859vdj.278.1316112650312; Thu, 15 Sep 2011 11:50:50 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.113.225 with HTTP; Thu, 15 Sep 2011 11:50:50 -0700 (PDT) In-Reply-To: References: Date: Thu, 15 Sep 2011 20:50:50 +0200 X-Google-Sender-Auth: WHFOvWp2ZUP0DB6qIujC0cIh3VA Message-ID: From: "K. Macy" To: Arnaud Lacombe Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: buf_ring(9) API precisions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 18:50:51 -0000 On Thu, Sep 15, 2011 at 4:53 AM, Arnaud Lacombe wrote: > Hi Kip, > > I've got a few question about the buf_ring(9) API. > > 1) what means the 'drbr_' prefix. I can guess the two last letter, 'b' > and 'r', for Buffer Ring, but what about 'd' and 'r' ? DRiver BufRing > 2) in `sys/sys/buf_ring.h', you defined 'struct buf_ring' as: > > struct buf_ring { > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_prod_head; > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_prod_tail; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_prod_size; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_prod_mask; > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_drops; > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_prod_bufs; > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_prod_bytes; > =A0 =A0 =A0 =A0/* > =A0 =A0 =A0 =A0 * Pad out to next L2 cache line > =A0 =A0 =A0 =A0 */ > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0_pad0[11]; > > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_cons_head; > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_cons_tail; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_cons_size; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_cons_mask; > > =A0 =A0 =A0 =A0/* > =A0 =A0 =A0 =A0 * Pad out to next L2 cache line > =A0 =A0 =A0 =A0 */ > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0_pad1[14]; > #ifdef DEBUG_BUFRING > =A0 =A0 =A0 =A0struct mtx =A0 =A0 =A0 =A0 =A0 =A0 =A0*br_lock; > #endif > =A0 =A0 =A0 =A0void =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*br_ring[0]; > }; > > Why are you making an MD guess, the amount of padding to fit the size > of a cache line, in MI API ? Strangely enough, you did not make this > assumption in, say r205488 (picked randomly). It has been several years, and I haven't done any work in svn in over a year, I don't remember. I probably meant to refine it in a later iteration. If you would like to send me a patch addressing this I'd be more than happy to apply it if appropriate. Otherwise, I will deal with it some time after 9 settles. Thanks for pointing this out. Cheers From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 21:21:28 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 640C5106566C; Thu, 15 Sep 2011 21:21:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 3ECF08FC15; Thu, 15 Sep 2011 21:21:28 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id B92E646B3B; Thu, 15 Sep 2011 17:21:27 -0400 (EDT) Date: Thu, 15 Sep 2011 22:21:27 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "K. Macy" In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Hackers , Arnaud Lacombe Subject: Re: buf_ring(9) API precisions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 21:21:28 -0000 On Thu, 15 Sep 2011, K. Macy wrote: >> Why are you making an MD guess, the amount of padding to fit the size of a >> cache line, in MI API ? Strangely enough, you did not make this assumption >> in, say r205488 (picked randomly). > > It has been several years, and I haven't done any work in svn in over a > year, I don't remember. I probably meant to refine it in a later iteration. > > If you would like to send me a patch addressing this I'd be more than happy > to apply it if appropriate. Otherwise, I will deal with it some time after 9 > settles. > > Thanks for pointing this out. I'm not sure if gcc (and friends) allow __aligned(CACHE_LINE_SIZE) to be used on individual elements of a struct (causing appropriate padding to be added), but that may be one option here. Of course, that introduces a further alignment requirement on the struct itself, so a moderate amount of care would need to be used. Robert From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 15 21:28:15 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 157A1106564A; Thu, 15 Sep 2011 21:28:15 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-gx0-f177.google.com (mail-gx0-f177.google.com [209.85.161.177]) by mx1.freebsd.org (Postfix) with ESMTP id 9A1388FC16; Thu, 15 Sep 2011 21:28:14 +0000 (UTC) Received: by gxk23 with SMTP id 23so3525820gxk.8 for ; Thu, 15 Sep 2011 14:28:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=8jK0MQdtgTB3rj22ac+DIPeopZCZnXDg3QTCj9F5o18=; b=IUSnV4Mc+W8HqO3oDvVpbT6jC8MLcliOp3qzLJmIwhLePLXufNtZQv/eKgpbuCuvls BmzueSQ4vEzZDJ08JsYuI2WVKb2/FK8gPgdItwDSPiBuHbnCZiIl6s6wfwFYqzLiXzer tAEBH6MIj0H2Ee1NUsxAeOMrjhM53wxSUE/qs= MIME-Version: 1.0 Received: by 10.68.71.200 with SMTP id x8mr821595pbu.465.1316122093449; Thu, 15 Sep 2011 14:28:13 -0700 (PDT) Received: by 10.142.12.18 with HTTP; Thu, 15 Sep 2011 14:28:13 -0700 (PDT) In-Reply-To: References: Date: Thu, 15 Sep 2011 17:28:13 -0400 Message-ID: From: Arnaud Lacombe To: Robert Watson Content-Type: multipart/mixed; boundary=bcaec544eb7cdc73ac04ad018df1 Cc: FreeBSD Hackers , "K. Macy" Subject: Re: buf_ring(9) API precisions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Sep 2011 21:28:15 -0000 --bcaec544eb7cdc73ac04ad018df1 Content-Type: text/plain; charset=ISO-8859-1 Hi, On Thu, Sep 15, 2011 at 5:21 PM, Robert Watson wrote: > On Thu, 15 Sep 2011, K. Macy wrote: > >>> Why are you making an MD guess, the amount of padding to fit the size of >>> a cache line, in MI API ? Strangely enough, you did not make this assumption >>> in, say r205488 (picked randomly). >> >> It has been several years, and I haven't done any work in svn in over a >> year, I don't remember. I probably meant to refine it in a later iteration. >> >> If you would like to send me a patch addressing this I'd be more than >> happy to apply it if appropriate. Otherwise, I will deal with it some time >> after 9 settles. >> >> Thanks for pointing this out. > > I'm not sure if gcc (and friends) allow __aligned(CACHE_LINE_SIZE) to be > used on individual elements of a struct (causing appropriate padding to be > added), but that may be one option here. > It definitively does, it is used in several structure in the tree. Attached a patch to convert buf_ring(9), however, I'm not a huge fan of dedicating a full cache line to the lock pointer. - Arnaud > Of course, that introduces a > further alignment requirement on the struct itself, so a moderate amount of > care would need to be used. > > Robert > --bcaec544eb7cdc73ac04ad018df1 Content-Type: text/x-patch; charset=US-ASCII; name="buf_ring_md_padding.diff" Content-Disposition: attachment; filename="buf_ring_md_padding.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: f_gsm8zgmr0 ZGlmZiAtLWdpdCBhL3N5cy9zeXMvYnVmX3JpbmcuaCBiL3N5cy9zeXMvYnVmX3JpbmcuaAppbmRl eCA1N2U0MmU1Li4wMWYzOTllIDEwMDY0NAotLS0gYS9zeXMvc3lzL2J1Zl9yaW5nLmgKKysrIGIv c3lzL3N5cy9idWZfcmluZy5oCkBAIC00OSwyNSArNDksMTcgQEAgc3RydWN0IGJ1Zl9yaW5nIHsK IAl1aW50NjRfdAkJYnJfZHJvcHM7CiAJdWludDY0X3QJCWJyX3Byb2RfYnVmczsKIAl1aW50NjRf dAkJYnJfcHJvZF9ieXRlczsKLQkvKgotCSAqIFBhZCBvdXQgdG8gbmV4dCBMMiBjYWNoZSBsaW5l Ci0JICovCi0JdWludDY0X3QJICAJX3BhZDBbMTFdOwogCi0Jdm9sYXRpbGUgdWludDMyX3QJYnJf Y29uc19oZWFkOworCXZvbGF0aWxlIHVpbnQzMl90CWJyX2NvbnNfaGVhZCBfX2FsaWduZWQoQ0FD SEVfTElORV9TSVpFKTsKIAl2b2xhdGlsZSB1aW50MzJfdAlicl9jb25zX3RhaWw7CiAJaW50CQkg CWJyX2NvbnNfc2l6ZTsKIAlpbnQgICAgICAgICAgICAgIAlicl9jb25zX21hc2s7CiAJCi0JLyoK LQkgKiBQYWQgb3V0IHRvIG5leHQgTDIgY2FjaGUgbGluZQotCSAqLwotCXVpbnQ2NF90CSAgCV9w YWQxWzE0XTsKICNpZmRlZiBERUJVR19CVUZSSU5HCi0Jc3RydWN0IG10eAkJKmJyX2xvY2s7CisJ c3RydWN0IG10eAkJKmJyX2xvY2sgX19hbGlnbmVkKENBQ0hFX0xJTkVfU0laRSk7CiAjZW5kaWYJ Ci0Jdm9pZAkJCSpicl9yaW5nWzBdOwotfTsKKwl2b2lkCQkJKmJyX3JpbmdbMF0gX19hbGlnbmVk KENBQ0hFX0xJTkVfU0laRSk7Cit9IF9fYWxpZ25lZChDQUNIRV9MSU5FX1NJWkUpOwogCiAvKgog ICogbXVsdGktcHJvZHVjZXIgc2FmZSBsb2NrLWZyZWUgcmluZyBidWZmZXIgZW5xdWV1ZQo= --bcaec544eb7cdc73ac04ad018df1-- From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 16 01:02:57 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BB04106567B; Fri, 16 Sep 2011 01:02:57 +0000 (UTC) (envelope-from lacombar@gmail.com) Received: from mail-gw0-f50.google.com (mail-gw0-f50.google.com [74.125.83.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3A7268FC08; Fri, 16 Sep 2011 01:02:57 +0000 (UTC) Received: by gwj16 with SMTP id 16so3397183gwj.37 for ; Thu, 15 Sep 2011 18:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=4poHGr9yOPCy8sm0TA9okYEVZ2FY/y1DYh8I7/Gt8Cg=; b=ojVH9aH46DccFmRp0X5+mk03y9KT1UXSsmWx6/4Ts0hP5ccFlMrSPny6PmmOlBDVn/ nAhvohdOJ6xeLCTK5/Gh9QSCVqDPRwPsidS8VPkhF5Wmh40CaTCjW9FVMqoLGzHQY+m1 cWO6WHoPCex7eBGeNWiszoYv18V5jz42M4VJw= MIME-Version: 1.0 Received: by 10.68.8.166 with SMTP id s6mr815734pba.398.1316134975971; Thu, 15 Sep 2011 18:02:55 -0700 (PDT) Received: by 10.142.12.18 with HTTP; Thu, 15 Sep 2011 18:02:55 -0700 (PDT) In-Reply-To: References: Date: Thu, 15 Sep 2011 21:02:55 -0400 Message-ID: From: Arnaud Lacombe To: "K. Macy" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: buf_ring(9) API precisions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2011 01:02:57 -0000 Hi, On Wed, Sep 14, 2011 at 10:53 PM, Arnaud Lacombe wrote= : > Hi Kip, > > I've got a few question about the buf_ring(9) API. > > 1) what means the 'drbr_' prefix. I can guess the two last letter, 'b' > and 'r', for Buffer Ring, but what about 'd' and 'r' ? > > 2) in `sys/sys/buf_ring.h', you defined 'struct buf_ring' as: > > struct buf_ring { > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_prod_head; > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_prod_tail; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_prod_size; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_prod_mask; > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_drops; > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_prod_bufs; > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_prod_bytes; shouldn't those 3 fields be updated atomically, especially on 32bits platforms ? That might pose a problem as, AFAIK, FreeBSD do not have MI 64bits atomics operations... - Arnaud > =A0 =A0 =A0 =A0/* > =A0 =A0 =A0 =A0 * Pad out to next L2 cache line > =A0 =A0 =A0 =A0 */ > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0_pad0[11]; > > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_cons_head; > =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_cons_tail; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_cons_size; > =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_cons_mask; > > =A0 =A0 =A0 =A0/* > =A0 =A0 =A0 =A0 * Pad out to next L2 cache line > =A0 =A0 =A0 =A0 */ > =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0_pad1[14]; > #ifdef DEBUG_BUFRING > =A0 =A0 =A0 =A0struct mtx =A0 =A0 =A0 =A0 =A0 =A0 =A0*br_lock; > #endif > =A0 =A0 =A0 =A0void =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*br_ring[0]; > }; > > Why are you making an MD guess, the amount of padding to fit the size > of a cache line, in MI API ? Strangely enough, you did not make this > assumption in, say r205488 (picked randomly). > > Thanks in advance, > =A0- Arnaud > From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 16 14:41:28 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16B7F106564A for ; Fri, 16 Sep 2011 14:41:28 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id C51D58FC17 for ; Fri, 16 Sep 2011 14:41:27 +0000 (UTC) Received: by qyk4 with SMTP id 4so4436218qyk.13 for ; Fri, 16 Sep 2011 07:41:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fPC6KmtjV+jEaaEaC6YygDNQdI6GcF6RbBnZHt4M3SU=; b=YYBKkYxEmNu12VxZclxzO7/YVcYHUWl7n5z+sGUw2XI68ialW+0wGPdXK0jgYcM9yI EaE3Bs4OLWrDQ3nrkVrxQWdk2tXz7aaUr3nq0jJ0TflT8frK8rBgok/1pVYwkMLsbavy 3ihAKfqYotL7RoPWMTvm6CEnxmTQH2zz61tUc= MIME-Version: 1.0 Received: by 10.52.36.101 with SMTP id p5mr1180175vdj.278.1316184086918; Fri, 16 Sep 2011 07:41:26 -0700 (PDT) Sender: kmacybsd@gmail.com Received: by 10.52.113.225 with HTTP; Fri, 16 Sep 2011 07:41:26 -0700 (PDT) In-Reply-To: References: Date: Fri, 16 Sep 2011 16:41:26 +0200 X-Google-Sender-Auth: XptWsiEi-wAvlk9GSILZsr3iTEQ Message-ID: From: "K. Macy" To: Arnaud Lacombe Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Hackers Subject: Re: buf_ring(9) API precisions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2011 14:41:28 -0000 On Fri, Sep 16, 2011 at 3:02 AM, Arnaud Lacombe wrote: > Hi, > > On Wed, Sep 14, 2011 at 10:53 PM, Arnaud Lacombe wro= te: >> Hi Kip, >> >> I've got a few question about the buf_ring(9) API. >> >> 1) what means the 'drbr_' prefix. I can guess the two last letter, 'b' >> and 'r', for Buffer Ring, but what about 'd' and 'r' ? >> >> 2) in `sys/sys/buf_ring.h', you defined 'struct buf_ring' as: >> >> struct buf_ring { >> =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_prod_head; >> =A0 =A0 =A0 =A0volatile uint32_t =A0 =A0 =A0 br_prod_tail; >> =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_prod_size; >> =A0 =A0 =A0 =A0int =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 br_prod_mask; >> =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_drops; >> =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_prod_bufs; >> =A0 =A0 =A0 =A0uint64_t =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0br_prod_bytes; > shouldn't those 3 fields be updated atomically, especially on 32bits > platforms ? That might pose a problem as, AFAIK, FreeBSD do not have > MI 64bits atomics operations... Between the point at which br_prod_tail =3D=3D prod_head and when we update br_prod_tail to point to prod_next we are the exclusive owners of the fields in buf_ring. That is why we wait for any other enqueueing threads to update br_prod_tail to point to prod_head before continuing. Cheers /* * If there are other enqueues in progress * that preceeded us, we need to wait for them * to complete */ while (br->br_prod_tail !=3D prod_head) cpu_spinwait(); br->br_prod_bufs++; br->br_prod_bytes +=3D nbytes; br->br_prod_tail =3D prod_next; critical_exit(); From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 16 20:30:27 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 060201065679 for ; Fri, 16 Sep 2011 20:30:27 +0000 (UTC) (envelope-from crmartin@sgi.com) Received: from relay.sgi.com (relay1.sgi.com [192.48.179.29]) by mx1.freebsd.org (Postfix) with ESMTP id DB0708FC22 for ; Fri, 16 Sep 2011 20:30:26 +0000 (UTC) Received: from xmail.sgi.com (pv-excas3-dc21-nlb.corp.sgi.com [137.38.102.207]) by relay1.corp.sgi.com (Postfix) with ESMTP id 8BAAD8F8068 for ; Fri, 16 Sep 2011 13:30:26 -0700 (PDT) Received: from [10.3.0.220] (10.3.0.220) by xmail.sgi.com (137.38.102.30) with Microsoft SMTP Server (TLS) id 14.1.289.1; Fri, 16 Sep 2011 15:30:26 -0500 Message-ID: <4E73B1E1.6020306@sgi.com> Date: Fri, 16 Sep 2011 14:30:25 -0600 From: Charlie Martin User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Lightning/1.0b2 Thunderbird/3.1.13 MIME-Version: 1.0 To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.3.0.220] Subject: dtrace in FreeBSD 7.2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Sep 2011 20:30:27 -0000 I need to add some custom static dtrace probes in 7.2 apps; the online documentation refers only to 9 however. Can someone tell me how to replace what's done in bsd.dtrace.mk for 7.2? Thanks Charlie -- Charles R. (Charlie) Martin Senior Software Engineer SGI logo 1900 Pike Road Longmont, CO 80501 Phone: 303-532-0209 E-Mail: CRMartin@sgi.com Website: www.sgi.com From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 17 01:13:24 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED8DF1065670 for ; Sat, 17 Sep 2011 01:13:24 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 475D18FC08 for ; Sat, 17 Sep 2011 01:13:24 +0000 (UTC) Received: (qmail invoked by alias); 17 Sep 2011 00:46:42 -0000 Received: from p4FE3334E.dip.t-dialin.net (EHLO rho.emma.line.org) [79.227.51.78] by mail.gmx.net (mp006) with SMTP; 17 Sep 2011 02:46:42 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX1/jwIZQ+RvjcH2UWdqit1IvQRWbxCTGzcKcm0Ry6v e8RjEOSkA8u0XO Received: from [127.0.0.1] (localhost [127.0.0.1]) by rho.emma.line.org (Postfix) with ESMTP id 6A92F33C17 for ; Sat, 17 Sep 2011 02:46:39 +0200 (CEST) From: Matthias Andree To: freebsd-hackers@freebsd.org In-Reply-To: <4E73B1E1.6020306@sgi.com> References: <4E73B1E1.6020306@sgi.com> Content-Type: text/plain; charset="UTF-8" Date: Sat, 17 Sep 2011 02:46:38 +0200 Message-ID: <1316220398.47177.1.camel@rho.emma.line.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: Re: dtrace in FreeBSD 7.2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2011 01:13:25 -0000 Am Freitag, den 16.09.2011, 14:30 -0600 schrieb Charlie Martin: > I need to add some custom static dtrace probes in 7.2 apps; the online > documentation refers only to 9 however. Can someone tell me how to > replace what's done in bsd.dtrace.mk for 7.2? FreeBSD 7.2 is quite old and wasn't under extended support, hence it is no longer supported. Consider upgrading. -- Matthias Andree From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 17 05:14:18 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02D51106564A for ; Sat, 17 Sep 2011 05:14:18 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) by mx1.freebsd.org (Postfix) with ESMTP id B34228FC13 for ; Sat, 17 Sep 2011 05:14:17 +0000 (UTC) Received: from julian-mac.elischer.org (home-nat.elischer.org [67.100.89.137]) (authenticated bits=0) by vps1.elischer.org (8.14.4/8.14.4) with ESMTP id p8H5EDLU045628 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 16 Sep 2011 22:14:16 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <4E742CC8.1070900@freebsd.org> Date: Fri, 16 Sep 2011 22:14:48 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.22) Gecko/20110902 Thunderbird/3.1.14 MIME-Version: 1.0 To: Charlie Martin References: <4E73B1E1.6020306@sgi.com> In-Reply-To: <4E73B1E1.6020306@sgi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: dtrace in FreeBSD 7.2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2011 05:14:18 -0000 On 9/16/11 1:30 PM, Charlie Martin wrote: > I need to add some custom static dtrace probes in 7.2 apps; the > online documentation refers only to 9 however. Can someone tell me > how to replace what's done in bsd.dtrace.mk for 7.2? I' am not sure that user space dtrace suport was available in 7.2.. My memory is that it came in 8.x but I'm not certain. > > Thanks > > Charlie From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 17 08:06:52 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AACD106566B for ; Sat, 17 Sep 2011 08:06:52 +0000 (UTC) (envelope-from fazaeli@sepehrs.com) Received: from sepehrs.com (sepehrs.com [213.217.59.98]) by mx1.freebsd.org (Postfix) with ESMTP id 6B31E8FC0C for ; Sat, 17 Sep 2011 08:06:50 +0000 (UTC) Received: from [127.0.0.1] ([192.168.3.10]) by sepehrs.com (8.14.3/8.14.3) with ESMTP id p8H7N9B9011876 for ; Sat, 17 Sep 2011 11:53:11 +0430 (IRDT) Message-ID: <4E744BCE.7060302@sepehrs.com> Date: Sat, 17 Sep 2011 11:57:10 +0430 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.22) Gecko/20110902 Thunderbird/3.1.14 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: intel checksum offload X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2011 08:06:52 -0000 Hi list, The data sheet for intel 82576 advertises IP TX/RX checksum offload but the driver does not set CSUM_IP in ifp->if_hwassist. Does this mean that driver (and chip) do not support IP TX checksum offload or the support for TX is not yet included in the driver? _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 17 20:57:33 2011 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EA801065677 for ; Sat, 17 Sep 2011 20:57:33 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f45.google.com (mail-pz0-f45.google.com [209.85.210.45]) by mx1.freebsd.org (Postfix) with ESMTP id D8EBC8FC1F for ; Sat, 17 Sep 2011 20:57:32 +0000 (UTC) Received: by pzk33 with SMTP id 33so9697343pzk.4 for ; Sat, 17 Sep 2011 13:57:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=x4Fu8EatruGKfPX8Pd2b0ThWmujRFVRJ3V9jiosw7p8=; b=BeyZeLYhKA+8+u7cejXUpDsRkUvPxFhe944+fRH+3lVxpE0nEs43932aXd/D+QhgAJ 2KAL7drlgtGcsvEw9f/URtVrwKgs/8TLhxNF3DbtYQo/cC+fwttwKyHyGnvBpHxLRB89 342a21YhAc2zXfSPBwBGSF/1jrHhwdv1WjFiU= Received: by 10.68.50.1 with SMTP id y1mr1362167pbn.495.1316291538602; Sat, 17 Sep 2011 13:32:18 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id i8sm26182165pbl.2.2011.09.17.13.32.16 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 17 Sep 2011 13:32:17 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sat, 17 Sep 2011 13:32:18 -0700 From: YongHyeon PYUN Date: Sat, 17 Sep 2011 13:32:18 -0700 To: Hooman Fazaeli Message-ID: <20110917203218.GC13993@michelle.cdnetworks.com> References: <4E744BCE.7060302@sepehrs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4E744BCE.7060302@sepehrs.com> User-Agent: Mutt/1.4.2.3i Cc: jfv@FreeBSD.org, freebsd-hackers@freebsd.org Subject: Re: intel checksum offload X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Sep 2011 20:57:33 -0000 On Sat, Sep 17, 2011 at 11:57:10AM +0430, Hooman Fazaeli wrote: > Hi list, > > The data sheet for intel 82576 advertises IP TX/RX checksum offload > but the driver does not set CSUM_IP in ifp->if_hwassist. Does this mean that > driver (and chip) do not support IP TX checksum offload or the support for > TX is not yet included in the driver? After reading this mail, I checked em(4)/lem(4) code and noticed these drivers removed CSUM_IP capability as well. igb(4) didn't support CSUM_IP from day 1 but em(4)/lem(4) used to take advantage of IP checksum offloading capability. Given that these drivers share many code with Linux, Jack may know the details and why IP checksum offloading code was removed. Note, Linux does not use IP checksum offloading so I guess this could be oversight in shared code. BTW, hackers may not be right ML to post this kind of post. CCed to jfv@, the driver maintainer.