From owner-freebsd-current@FreeBSD.ORG Sun Jan 21 00:10:13 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1104D16A404; Sun, 21 Jan 2007 00:10:13 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id A28A313C459; Sun, 21 Jan 2007 00:10:12 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id l0L0ABrT031816; Sat, 20 Jan 2007 19:10:11 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.8/8.13.8) with ESMTP id l0L0ABTt042052; Sat, 20 Jan 2007 19:10:11 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 499AF73034; Sat, 20 Jan 2007 19:10:11 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070121001011.499AF73034@freebsd-current.sentex.ca> Date: Sat, 20 Jan 2007 19:10:11 -0500 (EST) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Scanned: ClamAV version devel-20070108, clamav-milter version devel-111206 on clamscanner1 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 00:10:13 -0000 TB --- 2007-01-20 23:05:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-01-20 23:05:01 - starting HEAD tinderbox run for arm/arm TB --- 2007-01-20 23:05:01 - cleaning the object tree TB --- 2007-01-20 23:05:30 - checking out the source tree TB --- 2007-01-20 23:05:30 - cd /tinderbox/HEAD/arm/arm TB --- 2007-01-20 23:05:30 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-01-20 23:16:30 - building world (CFLAGS=-O2 -pipe) TB --- 2007-01-20 23:16:30 - cd /src TB --- 2007-01-20 23:16:30 - /usr/bin/make -B buildworld >>> World build started on Sat Jan 20 23:16:32 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] gzip -cn /src/usr.sbin/mountd/exports.5 > exports.5.gz gzip -cn /src/usr.sbin/mountd/netgroup.5 > netgroup.5.gz gzip -cn /src/usr.sbin/mountd/mountd.8 > mountd.8.gz ===> usr.sbin/mount_portalfs (all) cc -O2 -pipe -I/src/usr.sbin/mount_portalfs/../../sbin/mount -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /src/usr.sbin/mount_portalfs/mount_portalfs.c cc -O2 -pipe -I/src/usr.sbin/mount_portalfs/../../sbin/mount -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /src/usr.sbin/mount_portalfs/activate.c /src/usr.sbin/mount_portalfs/activate.c: In function `send_reply': /src/usr.sbin/mount_portalfs/activate.c:126: warning: cast increases required alignment of target type *** Error code 1 Stop in /src/usr.sbin/mount_portalfs. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-01-21 00:10:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-01-21 00:10:11 - ERROR: failed to build world TB --- 2007-01-21 00:10:11 - tinderbox aborted TB --- 0.42 user 1.65 system 3910.03 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Sun Jan 21 03:13:31 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23FE216A402; Sun, 21 Jan 2007 03:13:31 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.freebsd.org (Postfix) with SMTP id 27E0613C428; Sun, 21 Jan 2007 03:13:29 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 20 Jan 2007 21:51:08 +0000 (GMT) Date: Sat, 20 Jan 2007 21:51:03 +0000 From: David Malone To: Bruce Evans Message-ID: <20070120215103.GA93101@walton.maths.tcd.ie> References: <20070117134022.V18339@besplex.bde.org> <20070117224812.Q23194@besplex.bde.org> <45AE7BF8.10703@fer.hr> <3bbf2fe10701171315g696bca4fi3bf676b62c06f4d@mail.gmail.com> <20070118094808.F11834@delplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070118094808.F11834@delplex.bde.org> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: Attilio Rao , freebsd-current@freebsd.org, Ivan Voras , freebsd-arch@freebsd.org Subject: Re: Optimized copy&move (was: Re: [PATCH] Mantaining turnstile aligned to 128 bytes in i386 CPUs) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 03:13:31 -0000 On Thu, Jan 18, 2007 at 11:16:19AM +1100, Bruce Evans wrote: > - the FPU routines are faster on Athlons (XP and 64 at least), but these > didn't exist until 2001. The introduction of these CPUs may have > been the trigger for turning off the FPU routines in -current in 2001. > Until then problems were limited to Pentium-1's since the dynamic > configuration prevented the routines being used on all other machines. I think a very quirky K6-2 machine that I had let us reproduce the problem fairly dependably and may have been part of the reason it was finally turned off. David. From owner-freebsd-current@FreeBSD.ORG Sun Jan 21 04:56:09 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E3D416A40B for ; Sun, 21 Jan 2007 04:56:09 +0000 (UTC) (envelope-from grafan@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by mx1.freebsd.org (Postfix) with ESMTP id 3168113C471 for ; Sun, 21 Jan 2007 04:56:09 +0000 (UTC) (envelope-from grafan@gmail.com) Received: by nz-out-0506.google.com with SMTP id i11so295217nzh for ; Sat, 20 Jan 2007 20:56:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aL7HeF1RW8wr/g/bCqloUYVPVLNAHuCHAGx3w/YMPcZxPZy8EYxq/LB6BHO11KIlVEPF527bl23fEn0LqOCNXOXx53OT1n73/ea4f4nu1nd+XsexJXNWZmC5GdIEUpz9IKUeNSqsK9XB1qBVyY25IiO22Ymh2+qJxwJ8QtYodZU= Received: by 10.114.12.9 with SMTP id 9mr5097wal.1169355368001; Sat, 20 Jan 2007 20:56:08 -0800 (PST) Received: by 10.115.19.5 with HTTP; Sat, 20 Jan 2007 20:56:07 -0800 (PST) Message-ID: <6eb82e0701202056r6f7ba27bx70f0cd330fe36b82@mail.gmail.com> Date: Sun, 21 Jan 2007 12:56:07 +0800 From: "Rong-en Fan" To: "Yuri Pankov" In-Reply-To: <45B29C7E.9050608@irbis.net.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6eb82e0701192328v4e44515bvcb3adeca8fcae115@mail.gmail.com> <6eb82e0701200015u1cf12019xd2ad65298ba87ead@mail.gmail.com> <45B29C7E.9050608@irbis.net.ru> Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP: ncurses update on the way X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 04:56:09 -0000 On 1/21/07, Yuri Pankov wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Rong-en Fan wrote: > > On 1/20/07, Rong-en Fan wrote: > >> In the next hour, I'm going to import ncurses 5.6 into base. > >> There will be a short breakage. I will send out another > >> message when it's done. > > > > It's done. > > > >> Regards, > >> Rong-En Fan > > Is there a plan to build libncursesw as well? yes. Regards, Rong-En Fan From owner-freebsd-current@FreeBSD.ORG Sun Jan 21 10:33:13 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5E90C16A400; Sun, 21 Jan 2007 10:33:13 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by mx1.freebsd.org (Postfix) with ESMTP id 39EF413C441; Sun, 21 Jan 2007 10:33:13 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-dkim-5.cisco.com ([171.68.10.79]) by sj-iport-5.cisco.com with ESMTP; 21 Jan 2007 02:33:12 -0800 Received: from sj-core-3.cisco.com (sj-core-3.cisco.com [171.68.223.137]) by sj-dkim-5.cisco.com (8.12.11/8.12.11) with ESMTP id l0LAXCNl003175; Sun, 21 Jan 2007 02:33:12 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id l0LAXCho026650; Sun, 21 Jan 2007 02:33:12 -0800 (PST) Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 21 Jan 2007 02:33:10 -0800 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 21 Jan 2007 02:33:09 -0800 Message-ID: <45B34141.4080600@cisco.com> Date: Sun, 21 Jan 2007 05:32:33 -0500 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.8) Gecko/20061029 FreeBSD/i386 SeaMonkey/1.0.6 MIME-Version: 1.0 To: John Baldwin References: <45AF7C3A.2080303@cisco.com> <200701201006.17619.jhb@freebsd.org> In-Reply-To: <200701201006.17619.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 21 Jan 2007 10:33:09.0847 (UTC) FILETIME=[8BA99E70:01C73D47] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1315; t=1169375592; x=1170239592; c=relaxed/simple; s=sjdkim5002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Re=3A=20Zone=20memory=20for=20UMA |Sender:=20; bh=Ma2j63j3yPPIlHKKNaD6UvLzU5g6PtwffpJOhZoOd8k=; b=tVf/AisCHQoaSu/Lrk62OEBbaA8DAFiC8UuCzjpKYwCtJwRI3l8YjWwFESMnu/mGr8vFzCuC 2SJoCEEpNJ1vVqkOiJpjq7NRvJDjRkz4nNZXQMtx0CSXsfos9JqdI99M; Authentication-Results: sj-dkim-5; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim5002 verified; ); Cc: freebsd-current@freebsd.org Subject: Re: Zone memory for UMA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 10:33:13 -0000 John Baldwin wrote: > On Thursday 18 January 2007 08:55, Randall Stewart wrote: >> Hi all: >> >> Query (with flame suit in place :-D) >> >> Currently the UMA zone's will hold all memory >> in them until .. well until the page deamon >> runs.. or so the "zone_drain()" comment says.. but >> I can't find that connection either. So I guess >> not at all :-0 > > uma_reclaim() drains all zones when it is called. It is called by the > pagedaemon when it is woken up to free some memory. > >> Should we think about adding some sort of garbage >> collector thread.. that could hang around slowly and >> periodically look for a zone with large numbers of free >> pages... and then drain that zone? > > pagedaemon is a sort of GC thread, but it kicks in whenever the system > is low on memory and asks other subsystems like UMA to free up some > memory. > Hmm.. Ok I see that path now that its been pointed out... but that means the crash I saw earlier was one where for some reason the PD did not wake up in time... Hmm.. I need to see if I can't recreate that crash ( I was a month behind and sup'd to current of course)... I would like to know the circumstances when this occurs :-) R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Sat Jan 20 14:06:55 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 727EF16A401 for ; Sat, 20 Jan 2007 14:06:55 +0000 (UTC) (envelope-from personrp@hotpop.com) Received: from smtp-out.hotpop.com (smtp-out.hotpop.com [38.113.3.71]) by mx1.freebsd.org (Postfix) with ESMTP id 3F13D13C469 for ; Sat, 20 Jan 2007 14:06:55 +0000 (UTC) (envelope-from personrp@hotpop.com) Received: from hotpop.com (kubrick.hotpop.com [38.113.3.105]) by smtp-out.hotpop.com (Postfix) with SMTP id 8C01440CFEA8 for ; Fri, 19 Jan 2007 22:42:52 +0000 (UTC) Received: from atomizer.opensourcebeef.net (unknown [71.61.11.4]) by smtp-1.hotpop.com (Postfix) with ESMTP id 4413C1480A7 for ; Fri, 19 Jan 2007 22:42:49 +0000 (UTC) Date: Fri, 19 Jan 2007 17:36:27 -0500 From: Rod Person To: freebsd-current@freebsd.org Message-ID: <20070119173627.15ff4286@atomizer.opensourcebeef.net> Organization: Open Source Beef Computing X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- X-Mailman-Approved-At: Sun, 21 Jan 2007 15:12:23 +0000 Subject: Problem with fsck on CURRENT?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jan 2007 14:06:55 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm not sure if this is a problem or is normal but here it is. I have an external ATAPI drive that is connected to my machine via firewire (that case also has a usb2 connection). My system crashed so I needed to fsck this disk. Now however I start fsck it does not allow me to answer 'Y' to any of the question - it answer N automatically. I've tried starting fsck with -y and that seems to do nothing! The drive is formatted with a UFS2 file system and I have to invoke fsck like this: fsck -t ufs /mnt Otherwise it claims not to be able to tell what file system type it is? I'm just wondering is this normal for external drives even if they are formatted with a native file system? Fsck doesn't act this why with my internal SCSI drives? - -- Rod "it takes an unusual mind to see the obvious." - - Alfred Whitehead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFr2K23rDijyy3LEcRAn15AJ9lLIX51ST1yTLLk2NwHW7rZ9wZbgCfXe4K CICDgjoqQSfcoRGUn0ArMsk= =oWzU -----END PGP SIGNATURE----- -- Rod "it takes an unusual mind to see the obvious." - Alfred Whitehead From owner-freebsd-current@FreeBSD.ORG Sun Jan 21 04:03:52 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EA8FC16A402; Sun, 21 Jan 2007 04:03:52 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout1.pacific.net.au (mailout1-3.pacific.net.au [61.8.2.210]) by mx1.freebsd.org (Postfix) with ESMTP id 84B8813C459; Sun, 21 Jan 2007 04:03:52 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout1.pacific.net.au (Postfix) with ESMTP id 29CF5328299; Sun, 21 Jan 2007 15:03:51 +1100 (EST) Received: from besplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (Postfix) with ESMTP id 9D5438C04; Sun, 21 Jan 2007 15:03:49 +1100 (EST) Date: Sun, 21 Jan 2007 15:03:48 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: David Malone In-Reply-To: <20070120215103.GA93101@walton.maths.tcd.ie> Message-ID: <20070121140716.W4007@besplex.bde.org> References: <20070117134022.V18339@besplex.bde.org> <20070117224812.Q23194@besplex.bde.org> <45AE7BF8.10703@fer.hr> <3bbf2fe10701171315g696bca4fi3bf676b62c06f4d@mail.gmail.com> <20070118094808.F11834@delplex.bde.org> <20070120215103.GA93101@walton.maths.tcd.ie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Sun, 21 Jan 2007 15:12:40 +0000 Cc: Attilio Rao , freebsd-current@FreeBSD.org, Ivan Voras , freebsd-arch@FreeBSD.org Subject: Re: Optimized copy&move (was: Re: [PATCH] Mantaining turnstile aligned to 128 bytes in i386 CPUs) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 04:03:53 -0000 On Sat, 20 Jan 2007, David Malone wrote: > On Thu, Jan 18, 2007 at 11:16:19AM +1100, Bruce Evans wrote: >> - the FPU routines are faster on Athlons (XP and 64 at least), but these >> didn't exist until 2001. The introduction of these CPUs may have >> been the trigger for turning off the FPU routines in -current in 2001. >> Until then problems were limited to Pentium-1's since the dynamic >> configuration prevented the routines being used on all other machines. > > I think a very quirky K6-2 machine that I had let us reproduce the > problem fairly dependably and may have been part of the reason it > was finally turned off. I just looked again at your old (2001) mail about this. The userland benchmark was flawed. It tried 3 methods sequentially without warming up caches, so all methods did unintended testing of I-cache misses (including branch target cache cache) and the first method (userland bzero) warmed up the D-cache for the other 2. The kernel runtime configuration also fails to either warm or cool the caches initially. It assumes P1 cache sizes and depends on a 1MB buffer being much larger than caches. Maybe this was not enough for K6-2. It is certainly not enough for Athlon64, but I think it would mostly cause false negatives so I don't understand why it gave a false positive for the K6-2. After fixing the userland benchmark, userland bzero did much better and your benchmark agreed with mine that FPU methods for bzero are just pessimizations on A64-AXP. However, the behaviour for bcopy is quite different on A64-AXP -- even the old FPU methods are small optimizations in some cases (on A64, about 25% in the fully-L2 cached case; little difference for other large copies). Bruce From owner-freebsd-current@FreeBSD.ORG Sun Jan 21 17:51:39 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4602416A405; Sun, 21 Jan 2007 17:51:39 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id EED3313C474; Sun, 21 Jan 2007 17:51:38 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id l0LHpVGj009348; Sun, 21 Jan 2007 10:51:37 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <45B3A821.3060605@samsco.org> Date: Sun, 21 Jan 2007 10:51:29 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0701191055u20b91c84tfabb242c9b6815fd@mail.gmail.com> <200701201041.10752.jhb@freebsd.org> <2a41acea0701201356u53dbbd94m877d4e46615d0b2f@mail.gmail.com> <45B292AB.7050503@samsco.org> <2a41acea0701201410m3ce52c0y7942182b9403037d@mail.gmail.com> In-Reply-To: <2a41acea0701201410m3ce52c0y7942182b9403037d@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Sun, 21 Jan 2007 10:51:37 -0700 (MST) X-Spam-Status: No, score=-1.2 required=3.8 tests=ALL_TRUSTED, MAILTO_TO_SPAM_ADDR autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-current@freebsd.org, Mark Atkinson Subject: Re: another msi blacklist candidate? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 17:51:39 -0000 Jack Vogel wrote: > On 1/20/07, Scott Long wrote: >> Jack Vogel wrote: >> > On 1/20/07, John Baldwin wrote: >> >> On Friday 19 January 2007 13:55, Jack Vogel wrote: >> >> > On 1/19/07, Mark Atkinson wrote: >> >> > > I upgraded a box to -current yesterday with the following pci card >> >> in it, >> >> > > (this is the msi disabled verbose boot below) but upon bootup, any >> >> heavy >> >> > > network activity caused watchdog timeouts and resets. Disabling >> >> msi via >> >> > > the two tunables fixed the problem. >> >> > > >> >> > > What info do you need on this problem? >> >> > > >> >> > > found-> vendor=0x8086, dev=0x1076, revid=0x00 >> >> > > bus=4, slot=2, func=0 >> >> > > class=02-00-00, hdrtype=0x00, mfdev=0 >> >> > > cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) >> >> > > lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), >> >> maxlat=0x00 (0 ns) >> >> > > intpin=a, irq=10 >> >> > > powerspec 2 supports D0 D3 current D0 >> >> > > MSI supports 1 message, 64 bit >> >> > > map[10]: type 1, range 32, base 0xdf9c0000, size 17, >> enabled >> >> > > pcib4: requested memory range 0xdf9c0000-0xdf9dffff: good >> >> > > map[14]: type 1, range 32, base 0xdf9e0000, size 17, >> enabled >> >> > > pcib4: requested memory range 0xdf9e0000-0xdf9fffff: good >> >> > > map[18]: type 4, range 32, base 0xdcc0, size 6, enabled >> >> > > pcib4: requested I/O range 0xdcc0-0xdcff: in range >> >> > > pcib4: matched entry for 4.2.INTA >> >> > > pcib4: slot 2 INTA hardwired to IRQ 18 >> >> > > em0: port >> >> > > 0xdcc0-0xdcff m >> >> > > em 0xdf9c0000-0xdf9dffff,0xdf9e0000-0xdf9fffff irq 18 at device >> >> 2.0 on pci4 >> >> > > em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xdf9c0000 >> >> > > em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0xdcc0 >> >> > > em0: bpf attached >> >> > > em0: Ethernet address: 00:0e:0c:6e:a1:39 >> >> > > em0: [FAST] >> >> > >> >> > Talked about this internally, and the advise here is that the em >> >> driver change >> >> > so that only PCI-E adapters can use MSI, this would eliminate the >> >> need to >> >> > blacklist in the kernel PCI code. >> >> >> >> It's not em(4) that is the problem, but the system, and I'd rather we >> >> fix it >> >> generically rather than in each driver. Maybe we should disable MSI >> >> for non-PCIe >> >> systems? >> > >> > Depends what that means, say a system HAS PCI-E, but also a PCI and/or >> > a PCI-X slot will MSI be unavailable in those slots, that's what I >> would >> > prefer. >> > >> > Jack >> >> Are you saying that MSI should only be available to PCIe devices? That >> will break legitimate PCI-X devices. > > True, the question is how many of those devices are problematic and need > blacklisting anyway? I don't have a feel for this, do you Scott? > > Jack It's up to the driver writers to keep tabs on their peripherals. If the Intel 12345 PCI-X NIC can't do MSI but the Intel 23456 PCI-X NIC can, then it's up to the driver to know that. Chipset support is the responsibility of the OS, and that's where it gets more difficult because MSI is still fairly immature on the x86/x64 platform. Scott From owner-freebsd-current@FreeBSD.ORG Sun Jan 21 22:07:35 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97D3E16A402 for ; Sun, 21 Jan 2007 22:07:35 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.freebsd.org (Postfix) with ESMTP id 1185513C459 for ; Sun, 21 Jan 2007 22:07:34 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id l0LM7Y1D006910 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 21 Jan 2007 23:07:34 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id l0LM7XdS006909 for current@freebsd.org; Sun, 21 Jan 2007 23:07:33 +0100 (CET) Date: Sun, 21 Jan 2007 23:07:33 +0100 From: Divacky Roman To: current@freebsd.org Message-ID: <20070121220733.GA6750@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: Subject: duplicate code in lipthread X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 22:07:35 -0000 Hi, I spotted that lib/libpthread/arch/i386/i386/pthread_md.c includes its own version of i386_set_gsbase. This function is defined in libc, is there any reason for it being defined in the pthread as well? if not - someone should remove that roman From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 05:06:44 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2DF5016A4C9 for ; Mon, 22 Jan 2007 05:06:44 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id BAE8313C465 for ; Mon, 22 Jan 2007 05:06:43 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so889290uge for ; Sun, 21 Jan 2007 21:06:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YLLboNdM/H3S+SNKzvGyuaXXI8YBUcnE2dYvD/DYpAXfqKl6tB+3KCu/oBO2M5QXSmeBkq6jIsSLhy4N3u6/m0ux43GhTxndoxmkntQWGhDg4dp0OqK9l9yv+WX8mf78CMcs7c1N5oScc8EOrwMQJcCAOBqsYhoNneZGC5xrrWM= Received: by 10.82.107.15 with SMTP id f15mr5924240buc.1169442402128; Sun, 21 Jan 2007 21:06:42 -0800 (PST) Received: by 10.82.127.12 with HTTP; Sun, 21 Jan 2007 21:06:42 -0800 (PST) Message-ID: <2a41acea0701212106t31b5478di8817cfda25637945@mail.gmail.com> Date: Sun, 21 Jan 2007 21:06:42 -0800 From: "Jack Vogel" To: "Scott Long" In-Reply-To: <45B3A821.3060605@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0701191055u20b91c84tfabb242c9b6815fd@mail.gmail.com> <200701201041.10752.jhb@freebsd.org> <2a41acea0701201356u53dbbd94m877d4e46615d0b2f@mail.gmail.com> <45B292AB.7050503@samsco.org> <2a41acea0701201410m3ce52c0y7942182b9403037d@mail.gmail.com> <45B3A821.3060605@samsco.org> Cc: freebsd-current@freebsd.org, Mark Atkinson Subject: Re: another msi blacklist candidate? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 05:06:44 -0000 On 1/21/07, Scott Long wrote: > Jack Vogel wrote: > > On 1/20/07, Scott Long wrote: > >> Jack Vogel wrote: > >> > On 1/20/07, John Baldwin wrote: > >> >> On Friday 19 January 2007 13:55, Jack Vogel wrote: > >> >> > On 1/19/07, Mark Atkinson wrote: > >> >> > > I upgraded a box to -current yesterday with the following pci card > >> >> in it, > >> >> > > (this is the msi disabled verbose boot below) but upon bootup, any > >> >> heavy > >> >> > > network activity caused watchdog timeouts and resets. Disabling > >> >> msi via > >> >> > > the two tunables fixed the problem. > >> >> > > > >> >> > > What info do you need on this problem? > >> >> > > > >> >> > > found-> vendor=0x8086, dev=0x1076, revid=0x00 > >> >> > > bus=4, slot=2, func=0 > >> >> > > class=02-00-00, hdrtype=0x00, mfdev=0 > >> >> > > cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) > >> >> > > lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), > >> >> maxlat=0x00 (0 ns) > >> >> > > intpin=a, irq=10 > >> >> > > powerspec 2 supports D0 D3 current D0 > >> >> > > MSI supports 1 message, 64 bit > >> >> > > map[10]: type 1, range 32, base 0xdf9c0000, size 17, > >> enabled > >> >> > > pcib4: requested memory range 0xdf9c0000-0xdf9dffff: good > >> >> > > map[14]: type 1, range 32, base 0xdf9e0000, size 17, > >> enabled > >> >> > > pcib4: requested memory range 0xdf9e0000-0xdf9fffff: good > >> >> > > map[18]: type 4, range 32, base 0xdcc0, size 6, enabled > >> >> > > pcib4: requested I/O range 0xdcc0-0xdcff: in range > >> >> > > pcib4: matched entry for 4.2.INTA > >> >> > > pcib4: slot 2 INTA hardwired to IRQ 18 > >> >> > > em0: port > >> >> > > 0xdcc0-0xdcff m > >> >> > > em 0xdf9c0000-0xdf9dffff,0xdf9e0000-0xdf9fffff irq 18 at device > >> >> 2.0 on pci4 > >> >> > > em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xdf9c0000 > >> >> > > em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0xdcc0 > >> >> > > em0: bpf attached > >> >> > > em0: Ethernet address: 00:0e:0c:6e:a1:39 > >> >> > > em0: [FAST] > >> >> > > >> >> > Talked about this internally, and the advise here is that the em > >> >> driver change > >> >> > so that only PCI-E adapters can use MSI, this would eliminate the > >> >> need to > >> >> > blacklist in the kernel PCI code. > >> >> > >> >> It's not em(4) that is the problem, but the system, and I'd rather we > >> >> fix it > >> >> generically rather than in each driver. Maybe we should disable MSI > >> >> for non-PCIe > >> >> systems? > >> > > >> > Depends what that means, say a system HAS PCI-E, but also a PCI and/or > >> > a PCI-X slot will MSI be unavailable in those slots, that's what I > >> would > >> > prefer. > >> > > >> > Jack > >> > >> Are you saying that MSI should only be available to PCIe devices? That > >> will break legitimate PCI-X devices. > > > > True, the question is how many of those devices are problematic and need > > blacklisting anyway? I don't have a feel for this, do you Scott? > > > > Jack > > It's up to the driver writers to keep tabs on their peripherals. If the > Intel 12345 PCI-X NIC can't do MSI but the Intel 23456 PCI-X NIC can, > then it's up to the driver to know that. Chipset support is the > responsibility of the OS, and that's where it gets more difficult > because MSI is still fairly immature on the x86/x64 platform. > > Scott > LOL, this conversation started because I said I was going to disallow some adapters from MSI and John said it should be in the OS not all the drivers :) I'm happy to do it the way I planned at first anyway :) Jack From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 06:14:20 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EC3AC16A403 for ; Mon, 22 Jan 2007 06:14:20 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id C1CB713C44B for ; Mon, 22 Jan 2007 06:14:20 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l0M6EIDN006143; Mon, 22 Jan 2007 00:14:18 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <45B4563D.8010507@centtech.com> Date: Mon, 22 Jan 2007 00:14:21 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070121) MIME-Version: 1.0 To: Rod Person References: <20070119173627.15ff4286@atomizer.opensourcebeef.net> In-Reply-To: <20070119173627.15ff4286@atomizer.opensourcebeef.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2476/Sun Jan 21 10:22:33 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: "freebsd-current@freebsd.org" Subject: Re: Problem with fsck on CURRENT?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 06:14:21 -0000 On 01/19/07 16:36, Rod Person wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I'm not sure if this is a problem or is normal but here it is. > > I have an external ATAPI drive that is connected to my machine via > firewire (that case also has a usb2 connection). My system crashed so I > needed to fsck this disk. Now however I start fsck it does not allow me > to answer 'Y' to any of the question - it answer N automatically. > > I've tried starting fsck with -y and that seems to do nothing! The > drive is formatted with a UFS2 file system and I have to invoke fsck > like this: > > fsck -t ufs /mnt > > Otherwise it claims not to be able to tell what file system type it is? > I'm just wondering is this normal for external drives even if they are > formatted with a native file system? Fsck doesn't act this why with my > internal SCSI drives? Without doing a background fsck, fsck won't allow writes to the disk if the partition is mounted. Try unmounting the file system, and running fsck again. Also, you should include more details about your device/partition/slices/etc in order to get a better response on the second part of your question. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology An undefined problem has an infinite number of solutions. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 07:35:15 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F15D16A402 for ; Mon, 22 Jan 2007 07:35:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by mx1.freebsd.org (Postfix) with ESMTP id 3C7BF13C457 for ; Mon, 22 Jan 2007 07:35:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1206319wxc for ; Sun, 21 Jan 2007 23:35:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; b=Zk4OM6NlPG7Wyb+4EYeSGu6aW6bhkFwBp0BIpqdbmRx1agWvkUjyOX+vWFSC7UwfpFcowr7K2NDRqzdQJ1PZoJ+bddICKk26VbktyXfAKYwVdnIO1tieZxEIJ0eFplKVmTqhAsm7xrM24d2gq4e4UycQkBn5A6+AqEIyX9cpfc4= Received: by 10.70.17.1 with SMTP id 1mr286925wxq.1169451314630; Sun, 21 Jan 2007 23:35:14 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 25sm9062453wra.2007.01.21.23.35.12; Sun, 21 Jan 2007 23:35:13 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l0M7aBhS030584 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 22 Jan 2007 16:36:11 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0M7aBJQ030583 for freebsd-current@FreeBSD.org; Mon, 22 Jan 2007 16:36:11 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 22 Jan 2007 16:36:11 +0900 From: Pyun YongHyeon To: freebsd-current@FreeBSD.org Message-ID: <20070122073611.GC29223@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="R3G7APHDIzY6R/pk" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 07:35:15 -0000 --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, It seems that some revisions of re(4) hardwares(PCIe variants?) still have Tx checksum offload issues. One user reported the issue said the attached patch fixed the issue on his box. Since there are lots of hardwares supported by re(4) I'd like to know whether the attached patch has no other regressions on re(4) hardwares. If there are no objections I'll commit it in a week. Thanks. -- Regards, Pyun YongHyeon --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_re.csum.patch" Index: if_rlreg.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_rlreg.h,v retrieving revision 1.64 diff -u -r1.64 if_rlreg.h --- if_rlreg.h 16 Jan 2007 20:35:23 -0000 1.64 +++ if_rlreg.h 20 Jan 2007 05:05:21 -0000 @@ -443,7 +443,12 @@ #define RL_RX_BUF_SZ RL_RXBUF_64 #define RL_RXBUFLEN (1 << ((RL_RX_BUF_SZ >> 11) + 13)) #define RL_TX_LIST_CNT 4 -#define RL_MIN_FRAMELEN 60 +/* + * re(4) hardware IPv4 Tx checksum offload could be mangled with 28 bytes + * or less IP packets. + */ +#define RL_TXCSUM_MINLEN 28 +#define RL_MIN_FRAMELEN (ETHER_HDR_LEN + RL_TXCSUM_MINLEN) #define RL_TXTHRESH(x) ((x) << 11) #define RL_TX_THRESH_INIT 96 #define RL_RX_FIFOTHRESH RL_RXFIFO_NOTHRESH --R3G7APHDIzY6R/pk-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 08:35:15 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 14EB116A400 for ; Mon, 22 Jan 2007 08:35:15 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6E3AB13C45E for ; Mon, 22 Jan 2007 08:35:14 +0000 (UTC) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.4/8.13.3) with ESMTP id l0M8Z7QZ071608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2007 11:35:07 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.4/8.13.1/Submit) id l0M8Z6ua071607; Mon, 22 Jan 2007 11:35:06 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 22 Jan 2007 11:35:06 +0300 From: Gleb Smirnoff To: Jack Vogel Message-ID: <20070122083506.GW4485@FreeBSD.org> References: <2a41acea0701171258k16b4c6ebuf1d4794b89d0749b@mail.gmail.com> <20070120065321.DB61216A405@hub.freebsd.org> <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> User-Agent: Mutt/1.5.6i Cc: Bill Paul , freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org, jon.otterholm@ide.resurscentrum.se Subject: Re: Lenovo X60 em workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 08:35:15 -0000 Jack, On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote: J> >> Since this was just seen, and the patch below validated as working I J> >wanted J> >> to send general email to capture this: J> >> J> >> The Lenovo X60 can have issues with long ping times, this is a KNOWN J> >> hardware problem, and Intel is working with IBM/Lenovo, a final 'fix' has J> >> not been decided on yet. Nevertheless, the patch below will work, but J> >> I do not want to check it in as its still temporary. J> >> J> >> Address questions to me, J> > J> >Okay, I have a question. Could you elaborate on just what the problem is? J> >(I mean, since it's KNOWN and all...) I'm just having a hard time figuring J> >out what problem could possibly be fixed by setting the RX interrupt J> >delay timer to a non-zero value (especially since elsewhere in the em(4) J> >source it says that doing so is a Bad Thing (tm)). J> J> saying its known to be a problem doesnt mean its cause is known :) J> They discovered that setting this eliminated the problem, but we J> immediately pointed out that this is, as you pointed out, a Bad J> Thing on other hardware, so the investigation continues, there is J> always a communication lag on these kind of things, so I dont know J> if it has been resolved yet or not. J> J> I just dont think this patch will become the final way to solve this, J> but we shall see :) Good to know that there is progress on this. Thanks! I will try the patch on my Lenovo T60 notebook, where the problem is also present. AFAIK, it is present on any Lenovo notebook with 82573 NIC. Can you please acknowledge that another bug with Lenovo + em(4) is known? I mean the problem, that em(4) isn't initialized properly on kernel boot, if the link is down. I have already reported this to you, and you said that I probably have bad hardware. Since that time, I've found several similar reports about Lenovo notebooks and em(4) driver in FreeBSD. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 09:16:10 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 848FE16A401 for ; Mon, 22 Jan 2007 09:16:10 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 21B6113C428 for ; Mon, 22 Jan 2007 09:16:09 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so423728nfc for ; Mon, 22 Jan 2007 01:16:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=cMmgxs9gcMUzd96KfpA67YzJiqVuonHYLRkOwF4lYrFwBB0uaMF8+uour3uNtZkF/vFsydRtC5XQF5se1+mjj7R3LE6anNPBEp3t1GO3vvfFkb7yhxvOEDnsZcrRPm2aMRagJKc9miN64Jo93x/iZVyIQKOq0oP+omzu2m5V+bY= Received: by 10.82.162.14 with SMTP id k14mr6262307bue.1169457368429; Mon, 22 Jan 2007 01:16:08 -0800 (PST) Received: by 10.82.106.13 with HTTP; Mon, 22 Jan 2007 01:16:08 -0800 (PST) Message-ID: Date: Mon, 22 Jan 2007 12:16:08 +0300 From: "Alexey Karagodov" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: sasyncd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 09:16:10 -0000 is there any plans to port sasyncd from OpenBSD to FreeBSD ? or just please tell, how can i do it myself From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 09:44:53 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CA1616A401 for ; Mon, 22 Jan 2007 09:44:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4940213C465 for ; Mon, 22 Jan 2007 09:44:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wr-out-0506.google.com with SMTP id 71so656516wri for ; Mon, 22 Jan 2007 01:44:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=QFC/88MucOE7duSZ/jSSNY3oCu3Mj3KtChrNbnMwnd/E7LiY+HQ5cm8EkIy9jNnDAIry/9RdRyJNnQTwJtaWik3F3R9Y48XW3Vnfb93A9yEGAQiIyo4YIDjD9uDI/LSyMY7eOYER6yyvifGOcGgv1K7DGZnSr8nyI4ra9xgiX5g= Received: by 10.90.94.2 with SMTP id r2mr5875883agb.1169459092475; Mon, 22 Jan 2007 01:44:52 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 10sm9251392wrl.2007.01.22.01.44.50; Mon, 22 Jan 2007 01:44:51 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l0M9jp21030999 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2007 18:45:51 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0M9joTe030998; Mon, 22 Jan 2007 18:45:50 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 22 Jan 2007 18:45:50 +0900 From: Pyun YongHyeon To: Sepherosa Ziehau Message-ID: <20070122094550.GE29223@cdnetworks.co.kr> References: <20070122073611.GC29223@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 09:44:53 -0000 On Mon, Jan 22, 2007 at 05:24:54PM +0800, Sepherosa Ziehau wrote: > On 1/22/07, Pyun YongHyeon wrote: > >Hi, > > > >It seems that some revisions of re(4) hardwares(PCIe variants?) still > >have Tx checksum offload issues. One user reported the issue said > >the attached patch fixed the issue on his box. > > -#define RL_MIN_FRAMELEN 60 > +/* > + * re(4) hardware IPv4 Tx checksum offload could be mangled with 28 bytes > + * or less IP packets. > + */ > +#define RL_TXCSUM_MINLEN 28 > +#define RL_MIN_FRAMELEN (ETHER_HDR_LEN + RL_TXCSUM_MINLEN) > > Does you patch mean a buggy PCIe re(4) will trash small packets padded > to 60bytes but will not trash small packets padded to 42bytes? If Yes. > "yes" is the answer, then why normal packets whose size is 60bytes > will not be trashed by a buggy PCIe re(4)? > I don't know(Only RealTek knows the details). But it seems that hardware's SM for checksum computation was confused by the padding bytes and subsequent small (retransmitted) packets which has less than a threshold frame length bytes were mangled. Maybe it didn't see extra padding bytes so its SM worked as expected. > IMHO, "fixing buggy PCIe re(4) txcsum" is not NetBSD's original > intention to narrow down the size of packets that will trigger the > re(4) txcsum bug. > Agreed. But it also fixed buggy checksum bugs in PCIe variants which does not like to expect extra padded bytes. > Best Regards, > sephe > > -- > Live Free or Die -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 09:50:44 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2938A16A401 for ; Mon, 22 Jan 2007 09:50:44 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id B802B13C4A5 for ; Mon, 22 Jan 2007 09:50:43 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so933614uge for ; Mon, 22 Jan 2007 01:50:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ucwkfwc9O+aVj+bR9LAPzLJb+mLrrPubOCntOnhSx5WIRquxJLNbgvlLWLFYsb+YpMNuJ7pHxNcRkbZelDZmkO+CFWDnjAwNtqbZ3HXSqvVjjqOtQ6IxnsVNGCKDg/iDayZUecBZOu9pmwbqMDPr9uDHOdBJ5RMlUVdoDjC0FWQ= Received: by 10.82.114.3 with SMTP id m3mr4414957buc.1169457894692; Mon, 22 Jan 2007 01:24:54 -0800 (PST) Received: by 10.78.130.18 with HTTP; Mon, 22 Jan 2007 01:24:54 -0800 (PST) Message-ID: Date: Mon, 22 Jan 2007 17:24:54 +0800 From: "Sepherosa Ziehau" To: pyunyh@gmail.com In-Reply-To: <20070122073611.GC29223@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070122073611.GC29223@cdnetworks.co.kr> Cc: freebsd-current@freebsd.org Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 09:50:44 -0000 On 1/22/07, Pyun YongHyeon wrote: > Hi, > > It seems that some revisions of re(4) hardwares(PCIe variants?) still > have Tx checksum offload issues. One user reported the issue said > the attached patch fixed the issue on his box. -#define RL_MIN_FRAMELEN 60 +/* + * re(4) hardware IPv4 Tx checksum offload could be mangled with 28 bytes + * or less IP packets. + */ +#define RL_TXCSUM_MINLEN 28 +#define RL_MIN_FRAMELEN (ETHER_HDR_LEN + RL_TXCSUM_MINLEN) Does you patch mean a buggy PCIe re(4) will trash small packets padded to 60bytes but will not trash small packets padded to 42bytes? If "yes" is the answer, then why normal packets whose size is 60bytes will not be trashed by a buggy PCIe re(4)? IMHO, "fixing buggy PCIe re(4) txcsum" is not NetBSD's original intention to narrow down the size of packets that will trigger the re(4) txcsum bug. Best Regards, sephe -- Live Free or Die From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 12:32:11 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E955B16A401; Mon, 22 Jan 2007 12:32:11 +0000 (UTC) (envelope-from chopin@sgh.waw.pl) Received: from alternator.sgh.waw.pl (alternator.sgh.waw.pl [194.145.96.100]) by mx1.freebsd.org (Postfix) with ESMTP id A8EE813C442; Mon, 22 Jan 2007 12:32:11 +0000 (UTC) (envelope-from chopin@sgh.waw.pl) Received: from localhost (localhost [127.0.0.1]) by alternator.sgh.waw.pl (Postfix) with SMTP id 6291C2AA53F; Mon, 22 Jan 2007 13:32:09 +0100 (CET) Received: from akson.sgh.waw.pl (akson.sgh.waw.pl [194.145.96.12]) by alternator.sgh.waw.pl (Postfix) with ESMTP id 475202AA471; Mon, 22 Jan 2007 13:32:09 +0100 (CET) Received: by akson.sgh.waw.pl (Postfix, from userid 100) id DA2C72CBA; Mon, 22 Jan 2007 13:29:38 +0100 (CET) Date: Mon, 22 Jan 2007 13:29:38 +0100 From: Piotr KUCHARSKI To: maxine_chen Message-ID: <20070122122938.GT28416@sgh.waw.pl> References: <20070116140715.GL28416@sgh.waw.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: ronald_cheng@proware.com.tw, pjd@freebsd.org, freebsd-current@freebsd.org Subject: Re: problem with 4T volume under FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 12:32:12 -0000 On Mon, Jan 22, 2007 at 07:27:27PM +0800, maxine_chen wrote: > The testing failed when 2 partitions with Adaptec, but when the testing > with LSI and the result is fine. Thank you for your tests. It seems to me now that the problem lies in either Adaptec adapter itself or the FreeBSD driver. p. -- Beware of he who would deny you access to information, for in his heart he dreams himself your master. -- Commissioner Pravin Lal From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 15:54:54 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8340116A409 for ; Mon, 22 Jan 2007 15:54:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 543C013C45B for ; Mon, 22 Jan 2007 15:54:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id l0MFsJ2k099205; Mon, 22 Jan 2007 10:54:31 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Jack Vogel" Date: Mon, 22 Jan 2007 10:42:34 -0500 User-Agent: KMail/1.9.1 References: <45B3A821.3060605@samsco.org> <2a41acea0701212106t31b5478di8817cfda25637945@mail.gmail.com> In-Reply-To: <2a41acea0701212106t31b5478di8817cfda25637945@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701221042.35008.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 22 Jan 2007 10:54:31 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2477/Mon Jan 22 10:10:05 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org, Mark Atkinson Subject: Re: another msi blacklist candidate? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 15:54:54 -0000 On Monday 22 January 2007 00:06, Jack Vogel wrote: > On 1/21/07, Scott Long wrote: > > Jack Vogel wrote: > > > On 1/20/07, Scott Long wrote: > > >> Jack Vogel wrote: > > >> > On 1/20/07, John Baldwin wrote: > > >> >> On Friday 19 January 2007 13:55, Jack Vogel wrote: > > >> >> > On 1/19/07, Mark Atkinson wrote: > > >> >> > > I upgraded a box to -current yesterday with the following pci card > > >> >> in it, > > >> >> > > (this is the msi disabled verbose boot below) but upon bootup, any > > >> >> heavy > > >> >> > > network activity caused watchdog timeouts and resets. Disabling > > >> >> msi via > > >> >> > > the two tunables fixed the problem. > > >> >> > > > > >> >> > > What info do you need on this problem? > > >> >> > > > > >> >> > > found-> vendor=0x8086, dev=0x1076, revid=0x00 > > >> >> > > bus=4, slot=2, func=0 > > >> >> > > class=02-00-00, hdrtype=0x00, mfdev=0 > > >> >> > > cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) > > >> >> > > lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), > > >> >> maxlat=0x00 (0 ns) > > >> >> > > intpin=a, irq=10 > > >> >> > > powerspec 2 supports D0 D3 current D0 > > >> >> > > MSI supports 1 message, 64 bit > > >> >> > > map[10]: type 1, range 32, base 0xdf9c0000, size 17, > > >> enabled > > >> >> > > pcib4: requested memory range 0xdf9c0000-0xdf9dffff: good > > >> >> > > map[14]: type 1, range 32, base 0xdf9e0000, size 17, > > >> enabled > > >> >> > > pcib4: requested memory range 0xdf9e0000-0xdf9fffff: good > > >> >> > > map[18]: type 4, range 32, base 0xdcc0, size 6, enabled > > >> >> > > pcib4: requested I/O range 0xdcc0-0xdcff: in range > > >> >> > > pcib4: matched entry for 4.2.INTA > > >> >> > > pcib4: slot 2 INTA hardwired to IRQ 18 > > >> >> > > em0: port > > >> >> > > 0xdcc0-0xdcff m > > >> >> > > em 0xdf9c0000-0xdf9dffff,0xdf9e0000-0xdf9fffff irq 18 at device > > >> >> 2.0 on pci4 > > >> >> > > em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xdf9c0000 > > >> >> > > em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0xdcc0 > > >> >> > > em0: bpf attached > > >> >> > > em0: Ethernet address: 00:0e:0c:6e:a1:39 > > >> >> > > em0: [FAST] > > >> >> > > > >> >> > Talked about this internally, and the advise here is that the em > > >> >> driver change > > >> >> > so that only PCI-E adapters can use MSI, this would eliminate the > > >> >> need to > > >> >> > blacklist in the kernel PCI code. > > >> >> > > >> >> It's not em(4) that is the problem, but the system, and I'd rather we > > >> >> fix it > > >> >> generically rather than in each driver. Maybe we should disable MSI > > >> >> for non-PCIe > > >> >> systems? > > >> > > > >> > Depends what that means, say a system HAS PCI-E, but also a PCI and/or > > >> > a PCI-X slot will MSI be unavailable in those slots, that's what I > > >> would > > >> > prefer. > > >> > > > >> > Jack > > >> > > >> Are you saying that MSI should only be available to PCIe devices? That > > >> will break legitimate PCI-X devices. > > > > > > True, the question is how many of those devices are problematic and need > > > blacklisting anyway? I don't have a feel for this, do you Scott? > > > > > > Jack > > > > It's up to the driver writers to keep tabs on their peripherals. If the > > Intel 12345 PCI-X NIC can't do MSI but the Intel 23456 PCI-X NIC can, > > then it's up to the driver to know that. Chipset support is the > > responsibility of the OS, and that's where it gets more difficult > > because MSI is still fairly immature on the x86/x64 platform. > > > > Scott > > > > LOL, this conversation started because I said I was going to disallow > some adapters from MSI and John said it should be in the OS not > all the drivers :) > > I'm happy to do it the way I planned at first anyway :) Umm, is there an errata where non-PCI-e em(4) adapters don't support MSI? If not, then don't disable MSI. Unless that is the case, the more likely cause is that the OP's chipset doesn't support MSI _at all_, and that type of issue should be in the OS. If you know from errata that non-PCI-e em(4) parts can't do MSI, then that is something you should handle in the driver. Maybe it would help if I explained how MSI works on x86: By default, the local APIC is mapped at 0xfee00000 on x86 machines (both ia32 and amd64) so writes by the CPU to that range of physical addresses never make it out of the CPU and onto the bus. As a result, that bit of address space is essentially dead to the rest of the system (there could be RAM backing it, but if you DMA'd data into it, the CPU could never access it). Thus, for MSI on x86, the chipset reuses that "dead" address space. It has a device in the chipset (probably in the MCH on Intel, it's in HT-PCI bridges on amd) that listens for writes to that address range and generates an APIC message that is sent to the appropriate CPU(s) to trigger an interrupt. All that magic is in the chipset, it's not in the CPU, it's not in any of the PCI devices sending messages (they just do normal memory writes). Assuming non PCI-e em(4) parts are capable of correctly generating a memory write (:-P) they should work fine so long as something in the chipset is "listening" for the messages to convert them into APIC interrupt messages. Older chipsets don't have anything listening. Typically what happens then is that the device gets a target abort on the memory write and asserts SERR#. On some systems this is just ignored (and you get watchdog timeouts, etc.) and on other systems this triggers an NMI. However, none of this is em(4) specific. My suggestion is that we should blacklist non-PCI-e chipsets by default (maybe with explicit whitelisting for non-PCI-e ones that do work). In a working PCI-e system if you have a non-PCI-e em(4) part that can do MSI part whose parent bridge is a PCIe-PCI bridge and the chipset has something "listening" for writes to 0xfee00000, then the memory write that MSI triggers is going to propagate up to the chipset and work just as well as for a PCI-e device in the system. In short, you should only disable devices in the driver if you know they are broken in the actual device itself, not as a poor way to try to handle broken chipsets. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 16:49:29 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 60A6E16A401; Mon, 22 Jan 2007 16:49:29 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.freebsd.org (Postfix) with ESMTP id D072113C43E; Mon, 22 Jan 2007 16:49:28 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id l0MGnRSv008466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2007 17:49:27 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id l0MGnQEX008465; Mon, 22 Jan 2007 17:49:26 +0100 (CET) Date: Mon, 22 Jan 2007 17:49:26 +0100 From: Divacky Roman To: current@freebsd.org Message-ID: <20070122164926.GA8146@stud.fit.vutbr.cz> References: <20070120170723.34c223fb@Magellan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070120170723.34c223fb@Magellan.Leidinger.net> User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: emulation@freebsd.org Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 16:49:29 -0000 On Sat, Jan 20, 2007 at 05:07:23PM +0100, Alexander Leidinger wrote: > Hi, > > today I committed the last fixes for the showstopper problems (panics) > in the linux 2.6.16 emulation. I intend to switch the default version > to 2.6.16 on i386 "soon" (see below), so please help testing it. to be more precise.. we want testing on -current on i386... any other report is useles. except for reports from p4 linuxulator branch on 2.6/amd64.. roman From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 18:30:50 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D8AF716A407 for ; Mon, 22 Jan 2007 18:30:50 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 6802213C45D for ; Mon, 22 Jan 2007 18:30:50 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so1048802uge for ; Mon, 22 Jan 2007 10:30:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LypZu9zXm94JUYUYZbaJ58muOL/ZaN/AOoIV99gXwTQfkw7mlbqN+zu3kqFtnC/q3zurzxbMYW+aIxnR2DV2XSfRFkGOhwR9ypVIimOPgPpihimPP3zNv5QU+J1ZkTRocV4TJo1sE9ltCoYW4bJP3pDekxWH+ECeE+Ge3knFU/0= Received: by 10.82.105.13 with SMTP id d13mr7218829buc.1169490648616; Mon, 22 Jan 2007 10:30:48 -0800 (PST) Received: by 10.82.127.12 with HTTP; Mon, 22 Jan 2007 10:30:48 -0800 (PST) Message-ID: <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> Date: Mon, 22 Jan 2007 10:30:48 -0800 From: "Jack Vogel" To: "Gleb Smirnoff" In-Reply-To: <20070122083506.GW4485@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0701171258k16b4c6ebuf1d4794b89d0749b@mail.gmail.com> <20070120065321.DB61216A405@hub.freebsd.org> <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> <20070122083506.GW4485@FreeBSD.org> Cc: Bill Paul , freebsd-current@freebsd.org, freebsd-stable@freebsd.org, jon.otterholm@ide.resurscentrum.se Subject: Re: Lenovo X60 em workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 18:30:50 -0000 On 1/22/07, Gleb Smirnoff wrote: > Jack, > > On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote: > J> >> Since this was just seen, and the patch below validated as working I > J> >wanted > J> >> to send general email to capture this: > J> >> > J> >> The Lenovo X60 can have issues with long ping times, this is a KNOWN > J> >> hardware problem, and Intel is working with IBM/Lenovo, a final 'fix' has > J> >> not been decided on yet. Nevertheless, the patch below will work, but > J> >> I do not want to check it in as its still temporary. > J> >> > J> >> Address questions to me, > J> > > J> >Okay, I have a question. Could you elaborate on just what the problem is? > J> >(I mean, since it's KNOWN and all...) I'm just having a hard time figuring > J> >out what problem could possibly be fixed by setting the RX interrupt > J> >delay timer to a non-zero value (especially since elsewhere in the em(4) > J> >source it says that doing so is a Bad Thing (tm)). > J> > J> saying its known to be a problem doesnt mean its cause is known :) > J> They discovered that setting this eliminated the problem, but we > J> immediately pointed out that this is, as you pointed out, a Bad > J> Thing on other hardware, so the investigation continues, there is > J> always a communication lag on these kind of things, so I dont know > J> if it has been resolved yet or not. > J> > J> I just dont think this patch will become the final way to solve this, > J> but we shall see :) > > Good to know that there is progress on this. Thanks! I will try the patch > on my Lenovo T60 notebook, where the problem is also present. AFAIK, it > is present on any Lenovo notebook with 82573 NIC. > > Can you please acknowledge that another bug with Lenovo + em(4) is known? I > mean the problem, that em(4) isn't initialized properly on kernel boot, if > the link is down. I have already reported this to you, and you said that > I probably have bad hardware. Since that time, I've found several similar > reports about Lenovo notebooks and em(4) driver in FreeBSD. Hey Gleb, Acknowledge... I can do better than that, I have a fix for this problem, and its not temporary. Here is the code change (not a patch, I'm very busy), its in hardware_init, should be obvious how to patch: /* Make sure we have a good EEPROM before we read from it */ if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { /* ** Some PCI-E parts fail the first check due to ** the link being in sleep state, call it again, ** if it fails a second time its a real issue. */ if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { device_printf(dev, "The EEPROM Checksum Is Not Valid\n"); return (EIO); } } This is already checked into my code base at Intel, I've just been too busy to do anything with it, be my guest if you wish to check it in after testing... Cheers, Jack From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 18:34:49 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C86A616A401 for ; Mon, 22 Jan 2007 18:34:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.238]) by mx1.freebsd.org (Postfix) with ESMTP id 70F4D13C4C1 for ; Mon, 22 Jan 2007 18:34:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wr-out-0506.google.com with SMTP id 68so663258wri for ; Mon, 22 Jan 2007 10:34:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=X4gBLCTQlvA0X33liZitVbnSrcmGLO0ckIjzW76tW9ed/6lwKDkxvssPMn4ieRFs29qRi0BVOkVuHlkqwIda1UqD8MFG41jCw1S3j3wTXRUD7j/0YaQKuKyP3gUq7b+x/kR7eb9d3lVSEZGNkIdu/8S0reeG/h8QGJ78ZFm5eZI= Received: by 10.82.138.6 with SMTP id l6mr5620904bud.1169490888138; Mon, 22 Jan 2007 10:34:48 -0800 (PST) Received: by 10.82.127.12 with HTTP; Mon, 22 Jan 2007 10:34:48 -0800 (PST) Message-ID: <2a41acea0701221034j42fed2a9g3934ef187e3964ca@mail.gmail.com> Date: Mon, 22 Jan 2007 10:34:48 -0800 From: "Jack Vogel" To: "Gleb Smirnoff" In-Reply-To: <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0701171258k16b4c6ebuf1d4794b89d0749b@mail.gmail.com> <20070120065321.DB61216A405@hub.freebsd.org> <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> <20070122083506.GW4485@FreeBSD.org> <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> Cc: Bill Paul , freebsd-current@freebsd.org, freebsd-stable@freebsd.org, jon.otterholm@ide.resurscentrum.se Subject: Re: Lenovo X60 em workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 18:34:49 -0000 On 1/22/07, Jack Vogel wrote: > On 1/22/07, Gleb Smirnoff wrote: > > Jack, > > > > On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote: > > J> >> Since this was just seen, and the patch below validated as working I > > J> >wanted > > J> >> to send general email to capture this: > > J> >> > > J> >> The Lenovo X60 can have issues with long ping times, this is a KNOWN > > J> >> hardware problem, and Intel is working with IBM/Lenovo, a final 'fix' has > > J> >> not been decided on yet. Nevertheless, the patch below will work, but > > J> >> I do not want to check it in as its still temporary. > > J> >> > > J> >> Address questions to me, > > J> > > > J> >Okay, I have a question. Could you elaborate on just what the problem is? > > J> >(I mean, since it's KNOWN and all...) I'm just having a hard time figuring > > J> >out what problem could possibly be fixed by setting the RX interrupt > > J> >delay timer to a non-zero value (especially since elsewhere in the em(4) > > J> >source it says that doing so is a Bad Thing (tm)). > > J> > > J> saying its known to be a problem doesnt mean its cause is known :) > > J> They discovered that setting this eliminated the problem, but we > > J> immediately pointed out that this is, as you pointed out, a Bad > > J> Thing on other hardware, so the investigation continues, there is > > J> always a communication lag on these kind of things, so I dont know > > J> if it has been resolved yet or not. > > J> > > J> I just dont think this patch will become the final way to solve this, > > J> but we shall see :) > > > > Good to know that there is progress on this. Thanks! I will try the patch > > on my Lenovo T60 notebook, where the problem is also present. AFAIK, it > > is present on any Lenovo notebook with 82573 NIC. > > > > Can you please acknowledge that another bug with Lenovo + em(4) is known? I > > mean the problem, that em(4) isn't initialized properly on kernel boot, if > > the link is down. I have already reported this to you, and you said that > > I probably have bad hardware. Since that time, I've found several similar > > reports about Lenovo notebooks and em(4) driver in FreeBSD. > > Hey Gleb, > > Acknowledge... I can do better than that, I have a fix for this problem, and > its not temporary. Here is the code change (not a patch, I'm very busy), > its in hardware_init, should be obvious how to patch: > > /* Make sure we have a good EEPROM before we read from it */ > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > /* > ** Some PCI-E parts fail the first check due to > ** the link being in sleep state, call it again, > ** if it fails a second time its a real issue. > */ > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > device_printf(dev, > "The EEPROM Checksum Is Not Valid\n"); > return (EIO); > } > } > > This is already checked into my code base at Intel, I've just been too > busy to do anything with it, be my guest if you wish to check it in after > testing... > > Cheers, > > Jack > LOL, opps, I just realized, this code reflects the new shared code that I am in the process of releasing, in order for this to work in 6.2 change 'e1000_validate_nvm_checksum' to 'em_validate_eeprom_checksum' and all should be clear :) Jack From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 17:58:41 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F9F016A416 for ; Mon, 22 Jan 2007 17:58:41 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from rusty.swaggy.net (rusty.swaggy.net [66.103.13.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3F3D913C4CC for ; Mon, 22 Jan 2007 17:58:41 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from [127.0.0.1] (helo=swaggi.com) by rusty.swaggy.net with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1H92pn-00029W-U0 for freebsd-current@freebsd.org; Mon, 22 Jan 2007 12:19:58 -0500 From: "Yuri Lukin" To: freebsd-current@freebsd.org Date: Mon, 22 Jan 2007 12:19:55 -0500 Message-Id: <20070122171648.M47935@swaggi.com> X-Mailer: swaggi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Mon, 22 Jan 2007 19:21:28 +0000 Subject: 802.11n support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 17:58:41 -0000 Just wondering if there's any plans to add support for 802.11n even though it's currently just a draft: http://wifinetnews.com/archives/007328.html From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 19:47:13 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E203F16A401 for ; Mon, 22 Jan 2007 19:47:13 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.c0mplx.org (home.c0mplx.org [213.178.180.1]) by mx1.freebsd.org (Postfix) with ESMTP id 9B99713C441 for ; Mon, 22 Jan 2007 19:47:13 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from pi by home.c0mplx.org with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1H94D9-000F9c-9j for freebsd-current@FreeBSD.ORG; Mon, 22 Jan 2007 19:48:07 +0100 Date: Mon, 22 Jan 2007 19:48:07 +0100 From: Kurt Jaeger To: freebsd-current@FreeBSD.ORG Message-ID: <20070122184807.GA26839@home.c0mplx.org> References: <20070120170723.34c223fb@Magellan.Leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070120170723.34c223fb@Magellan.Leidinger.net> Cc: Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 19:47:14 -0000 Hi! Alex Leidinger wrote: > If you use a linux program, please add compat.linux.osrelease=2.6.16 > to /etc/sysctl.conf (my desktop is running with 2.6.16 emulation since > some days already). After the next boot (or after running "sysctl > compat.linux.osrelease=2.6.16", please make sure no linux program is > running already) any linux program will start with a linux kernel > version of 2.6.16 instead of 2.4.2. Is it possible to provide a program that lists the processes running under linux emu ? -- pi@c0mplx.org +49 171 3101372 13 years to go ! From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 19:54:34 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7D66F16A401 for ; Mon, 22 Jan 2007 19:54:34 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2D1E113C45D for ; Mon, 22 Jan 2007 19:54:34 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l0MJsXsW021933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2007 11:54:34 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <45B51678.10901@errno.com> Date: Mon, 22 Jan 2007 11:54:32 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.8 (X11/20061115) MIME-Version: 1.0 To: Yuri Lukin References: <20070122171648.M47935@swaggi.com> In-Reply-To: <20070122171648.M47935@swaggi.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 802.11n support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 19:54:34 -0000 Yuri Lukin wrote: > Just wondering if there's any plans to add support for 802.11n even though > it's currently just a draft: > > http://wifinetnews.com/archives/007328.html Yes there are plans. The first step is to get work from perforce into cvs; it's got many changes that'll make the net80211 layer mods for 11n simple. Past that supporting tx aggregation is a lot of work and I haven't heard of anyone planning to do that. Sam From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 21:30:42 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 828CC16A400 for ; Mon, 22 Jan 2007 21:30:42 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.freebsd.org (Postfix) with ESMTP id 1900813C4D3 for ; Mon, 22 Jan 2007 21:30:41 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id l0MLUdfo052022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Jan 2007 22:30:39 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id l0MLUdO2052020; Mon, 22 Jan 2007 22:30:39 +0100 (CET) Date: Mon, 22 Jan 2007 22:30:39 +0100 From: Divacky Roman To: Kurt Jaeger Message-ID: <20070122213039.GA51752@stud.fit.vutbr.cz> References: <20070120170723.34c223fb@Magellan.Leidinger.net> <20070122184807.GA26839@home.c0mplx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070122184807.GA26839@home.c0mplx.org> User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: freebsd-current@freebsd.org Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 21:30:42 -0000 On Mon, Jan 22, 2007 at 07:48:07PM +0100, Kurt Jaeger wrote: > Hi! > > Alex Leidinger wrote: > > If you use a linux program, please add compat.linux.osrelease=2.6.16 > > to /etc/sysctl.conf (my desktop is running with 2.6.16 emulation since > > some days already). After the next boot (or after running "sysctl > > compat.linux.osrelease=2.6.16", please make sure no linux program is > > running already) any linux program will start with a linux kernel > > version of 2.6.16 instead of 2.4.2. > > Is it possible to provide a program that lists the processes > running under linux emu ? I dont think so... the distinguishing in kernel is done by comparing p->p_sysent. but its usually very easy to say what is a linux program just try to kldunload linux module and if that doesnt succeed look at your ps ax output for suspicous programs (acroread, skype etc.) From owner-freebsd-current@FreeBSD.ORG Mon Jan 22 23:18:38 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8853716A400 for ; Mon, 22 Jan 2007 23:18:38 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5DDCE13C467 for ; Mon, 22 Jan 2007 23:18:38 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E542147EB3; Mon, 22 Jan 2007 18:18:37 -0500 (EST) Date: Mon, 22 Jan 2007 23:18:37 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Divacky Roman In-Reply-To: <20070122213039.GA51752@stud.fit.vutbr.cz> Message-ID: <20070122231754.A17361@fledge.watson.org> References: <20070120170723.34c223fb@Magellan.Leidinger.net> <20070122184807.GA26839@home.c0mplx.org> <20070122213039.GA51752@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Kurt Jaeger , freebsd-current@freebsd.org Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 23:18:38 -0000 > On Mon, Jan 22, 2007 at 07:48:07PM +0100, Kurt Jaeger wrote: >> Hi! >> >> Alex Leidinger wrote: >>> If you use a linux program, please add compat.linux.osrelease=2.6.16 to >>> /etc/sysctl.conf (my desktop is running with 2.6.16 emulation since some >>> days already). After the next boot (or after running "sysctl >>> compat.linux.osrelease=2.6.16", please make sure no linux program is >>> running already) any linux program will start with a linux kernel version >>> of 2.6.16 instead of 2.4.2. >> >> Is it possible to provide a program that lists the processes running under >> linux emu ? > > I dont think so... the distinguishing in kernel is done by comparing > p->p_sysent. but its usually very easy to say what is a linux program > > just try to kldunload linux module and if that doesnt succeed look at your > ps ax output for suspicous programs (acroread, skype etc.) This might well be something useful to add though -- an ABI name exported via kinfo_proc or such. It would also be useful for telling whether processes are 32-bit or 64-bit native processes, etc. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Tue Jan 23 00:30:36 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00EFF16A401 for ; Tue, 23 Jan 2007 00:30:36 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id B0D7113C4A6 for ; Tue, 23 Jan 2007 00:30:35 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H99YT-000207-7I for freebsd-current@freebsd.org; Tue, 23 Jan 2007 01:30:29 +0100 Received: from 89-172-41-77.adsl.net.t-com.hr ([89.172.41.77]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 23 Jan 2007 01:30:29 +0100 Received: from ivoras by 89-172-41-77.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 23 Jan 2007 01:30:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 23 Jan 2007 01:30:09 +0100 Lines: 33 Message-ID: References: <20070120170723.34c223fb@Magellan.Leidinger.net> <20070122184807.GA26839@home.c0mplx.org> <20070122213039.GA51752@stud.fit.vutbr.cz> <20070122231754.A17361@fledge.watson.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4A01B8E88C78DA34D653638C" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-41-77.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) In-Reply-To: <20070122231754.A17361@fledge.watson.org> X-Enigmail-Version: 0.94.1.2 Sender: news Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 00:30:36 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4A01B8E88C78DA34D653638C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > This might well be something useful to add though -- an ABI name > exported via kinfo_proc or such. It would also be useful for telling > whether processes are 32-bit or 64-bit native processes, etc. Yes, please. AFAIK currently there are upto 4 ABIs an amd64 machine can have: FreeBSD32, FreeBSD64, Linux32, Linux64 (probably). If it's not now, something like that will be necessary for debugging real soon now. --------------enig4A01B8E88C78DA34D653638C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFtVcXldnAQVacBcgRAoHvAKDSU27fZ4dp/4aGc9BBbFzg2LdkWwCeJw9b BNFbLPMuQQ2y9mThhifCz8w= =WDti -----END PGP SIGNATURE----- --------------enig4A01B8E88C78DA34D653638C-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 23 07:44:13 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EAD5416A402; Tue, 23 Jan 2007 07:44:13 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id BF8EC13C461; Tue, 23 Jan 2007 07:44:13 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id 67B0228434; Tue, 23 Jan 2007 01:14:58 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id A498261C3A; Tue, 23 Jan 2007 01:14:57 -0600 (CST) Date: Tue, 23 Jan 2007 01:14:57 -0600 From: "Matthew D. Fuller" To: Jason Evans Message-ID: <20070123071457.GM50948@over-yonder.net> References: <200701172045.35137.shoesoft@gmx.net> <45B00BF5.6030200@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45B00BF5.6030200@FreeBSD.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: freebsd-current@freebsd.org, Stefan Ehmann Subject: Re: very high memory usage in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 07:44:14 -0000 On Thu, Jan 18, 2007 at 04:08:21PM -0800 I heard the voice of Jason Evans, and lo! it spake thus: > Stefan Ehmann wrote: > >[huge jpeg/png images cause memory bloat with konqueror and gtk > >apps, on -CURRENT.] This may also surface in (ports/graphics/) evince's propensity to grow without apparent bounds from scrolling around a PDF. A friend on Linux doesn't see the behavior. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Tue Jan 23 16:30:36 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5FE8416A401 for ; Tue, 23 Jan 2007 16:30:36 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 108C213C44C for ; Tue, 23 Jan 2007 16:30:36 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <45B63164.9010408@intersonic.se> Date: Tue, 23 Jan 2007 17:01:40 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: p5-Locale-gettext build error: cannot open Makefile. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 16:30:36 -0000 p5-Locale-gettext refuses to build on my -CURRENT with sources from this morning. Have rebuilt and installed world, deleted and refetched the ports tree but no avail. Build fine on another -CURRENT and on 6- of course. Is this system possibly damaged in some way? - Thanks - ===> Extracting for p5-gettext-1.05_1 => MD5 Checksum OK for gettext-1.05.tar.gz. => SHA256 Checksum OK for gettext-1.05.tar.gz. ===> p5-gettext-1.05_1 depends on file: /usr/local/bin/perl5.8.8 - found ===> Patching for p5-gettext-1.05_1 ===> p5-gettext-1.05_1 depends on file: /usr/local/bin/perl5.8.8 - found ===> Applying FreeBSD patches for p5-gettext-1.05_1 ===> p5-gettext-1.05_1 depends on file: /usr/local/bin/perl5.8.8 - found ===> p5-gettext-1.05_1 depends on shared library: intl - found ===> Configuring for p5-gettext-1.05_1 ===> Building for p5-gettext-1.05_1 make: cannot open Makefile. *** Error code 2 Stop in /usr/ports/devel/p5-Locale-gettext. From owner-freebsd-current@FreeBSD.ORG Tue Jan 23 16:33:09 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D72B16A404 for ; Tue, 23 Jan 2007 16:33:09 +0000 (UTC) (envelope-from personrp@hotpop.com) Received: from smtp-out.hotpop.com (smtp-out.hotpop.com [38.113.3.71]) by mx1.freebsd.org (Postfix) with ESMTP id 0A5B113C47E for ; Tue, 23 Jan 2007 16:33:09 +0000 (UTC) (envelope-from personrp@hotpop.com) Received: from hotpop.com (kubrick.hotpop.com [38.113.3.105]) by smtp-out.hotpop.com (Postfix) with SMTP id 26FC0412F6AE for ; Tue, 23 Jan 2007 00:08:11 +0000 (UTC) Received: from atomizer.opensourcebeef.net (unknown [71.61.11.4]) by smtp-1.hotpop.com (Postfix) with ESMTP id DFCD81481AB; Tue, 23 Jan 2007 00:08:09 +0000 (UTC) Date: Mon, 22 Jan 2007 19:04:06 -0500 From: Rod Person To: Eric Anderson Message-ID: <20070122190406.6530a327@atomizer.opensourcebeef.net> In-Reply-To: <45B4563D.8010507@centtech.com> References: <20070119173627.15ff4286@atomizer.opensourcebeef.net> <45B4563D.8010507@centtech.com> Organization: Open Source Beef Computing X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- X-Mailman-Approved-At: Tue, 23 Jan 2007 17:14:25 +0000 Cc: "freebsd-current@freebsd.org" Subject: Re: Problem with fsck on CURRENT?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 16:33:09 -0000 On Mon, 22 Jan 2007 00:14:21 -0600 Eric Anderson wrote: > Without doing a background fsck, fsck won't allow writes to the disk > if the partition is mounted. Try unmounting the file system, and > running fsck again. > Thanks, I feel really dumb now. I've been using FreeBSD for 10 years and I missed the obvious :) -- Rod ----- Empty your mind, be formless, shapeless like water. Now you put water into a cup and it becomes the cup. You put water in a bottle it becomes the bottle. You put it into a teapot it becomes the teapot. Now water can flow or it can crash. Be water, my friend. -- Bruce Lee From owner-freebsd-current@FreeBSD.ORG Tue Jan 23 22:36:09 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7804016A403 for ; Tue, 23 Jan 2007 22:36:09 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id B8F8113C4C2 for ; Tue, 23 Jan 2007 22:36:08 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id l0NMJl9w042313; Tue, 23 Jan 2007 23:19:47 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id l0NMJbpY037204 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jan 2007 23:19:37 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id l0NMJbTB037343; Tue, 23 Jan 2007 23:19:37 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id l0NMJaIR037342; Tue, 23 Jan 2007 23:19:36 +0100 (CET) (envelope-from ticso) Date: Tue, 23 Jan 2007 23:19:36 +0100 From: Bernd Walter To: Rod Person Message-ID: <20070123221935.GZ23068@cicely12.cicely.de> References: <20070119173627.15ff4286@atomizer.opensourcebeef.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070119173627.15ff4286@atomizer.opensourcebeef.net> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: "freebsd-current@freebsd.org" Subject: Re: Problem with fsck on CURRENT?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 22:36:09 -0000 On Fri, Jan 19, 2007 at 05:36:27PM -0500, Rod Person wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I'm not sure if this is a problem or is normal but here it is. > > I have an external ATAPI drive that is connected to my machine via > firewire (that case also has a usb2 connection). My system crashed so I > needed to fsck this disk. Now however I start fsck it does not allow me > to answer 'Y' to any of the question - it answer N automatically. > > I've tried starting fsck with -y and that seems to do nothing! The > drive is formatted with a UFS2 file system and I have to invoke fsck > like this: > > fsck -t ufs /mnt > > Otherwise it claims not to be able to tell what file system type it is? > I'm just wondering is this normal for external drives even if they are > formatted with a native file system? Fsck doesn't act this why with my > internal SCSI drives? fsck get's the FS type from /etc/fstab. The other part is already aswered it seems. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-current@FreeBSD.ORG Tue Jan 23 18:22:35 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F75816A400 for ; Tue, 23 Jan 2007 18:22:35 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (palm.hoeg.nl [83.98.131.212]) by mx1.freebsd.org (Postfix) with ESMTP id DD30313C4BE for ; Tue, 23 Jan 2007 18:22:34 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id E11EA1CD4A; Tue, 23 Jan 2007 19:22:33 +0100 (CET) Date: Tue, 23 Jan 2007 19:22:33 +0100 From: Ed Schouten To: FreeBSD Current Message-ID: <20070123182233.GC64263@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mu6rDKe19l+MneQx" Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) X-Mailman-Approved-At: Tue, 23 Jan 2007 23:26:23 +0000 Cc: Laurens Timmermans Subject: Support for nVidia MCP61 (S)ATA controllers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2007 18:22:35 -0000 --mu6rDKe19l+MneQx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, A classmate of mine has recently purchased a motherboard with an nVidia MCP61 chipset. Because the chipset isn't listed in the FreeBSD ATA code yet, all his disks use UDMA33. We performed some tests and the following patch causes his ATA controller to run at UDMA133 and his harddisks at SATA300. http://g-rave.nl/junk/freebsd-ata-mcp61.diff Could this patch be integrated with FreeBSD CURRENT? If so: could it be MFC'd as well? --=20 Ed Schouten WWW: http://g-rave.nl/ --mu6rDKe19l+MneQx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFtlJp52SDGA2eCwURAse0AJ430pPEBjrCt4gJjr6oyZdwm1fOYwCfUQBO S/6mat1D1iyD52RKap1YR4s= =436H -----END PGP SIGNATURE----- --mu6rDKe19l+MneQx-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 00:00:35 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A3CC716A46E; Wed, 24 Jan 2007 00:00:35 +0000 (UTC) (envelope-from louisk@cryptomonkeys.com) Received: from abeyance.cryptomonkeys.com (abeyance.cryptomonkeys.com [67.42.3.2]) by mx1.freebsd.org (Postfix) with ESMTP id 32B3713C428; Wed, 24 Jan 2007 00:00:24 +0000 (UTC) (envelope-from louisk@cryptomonkeys.com) Received: from localhost (SJC-Office-NAT-236.Mail-Abuse.ORG [168.61.10.236]) (authenticated bits=0) by abeyance.cryptomonkeys.com (8.13.8+Sun/8.13.8) with ESMTP id l0NNo36p014781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jan 2007 15:50:10 -0800 (PST) Date: Tue, 23 Jan 2007 15:50:05 -0800 From: Louis Kowolowski To: Jack Vogel Message-ID: <20070123235004.GF1504@cryptomonkeys.com> Mail-Followup-To: Jack Vogel , freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: <2a41acea0701171258k16b4c6ebuf1d4794b89d0749b@mail.gmail.com> <20070120065321.DB61216A405@hub.freebsd.org> <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> <20070122083506.GW4485@FreeBSD.org> <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> <2a41acea0701221034j42fed2a9g3934ef187e3964ca@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="1Ow488MNN9B9o/ov" Content-Disposition: inline In-Reply-To: <2a41acea0701221034j42fed2a9g3934ef187e3964ca@mail.gmail.com> User-Agent: TV Remote 3.2b X-Disclaimer: WARNING: May contain scarcasm! X-Header: "WARNING: POLITICALLY INCORRECT AREA All P.C. Personnel entering these premises will encounter gravely offensive behavior and opinions. (SEC4623. Ministry of political incorrection security act of 1995) RAMPANT INSENSITIVITY AUTHORIZED" X-GPG-Fingerprint: 7A77 80FD 3F4D 995E A807 A218 664D 2BEA 8024 37B6 X-GPG-Key: http://www.cryptomonkeys.com/~louisk/pgp.html Organization: Hopelessly Disorganized Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Lenovo X60 em workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 00:00:35 -0000 --1Ow488MNN9B9o/ov Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 22, 2007 at 10:34:48AM -0800, Jack Vogel wrote: > On 1/22/07, Jack Vogel wrote: > >On 1/22/07, Gleb Smirnoff wrote: > >> Jack, > >> > >> On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote: > >> J> >> Since this was just seen, and the patch below validated as worki= ng=20 > >I > >> J> >wanted > >> J> >> to send general email to capture this: > >> J> >> > >> J> >> The Lenovo X60 can have issues with long ping times, this is a= =20 > >KNOWN > >> J> >> hardware problem, and Intel is working with IBM/Lenovo, a final= =20 > >'fix' has > >> J> >> not been decided on yet. Nevertheless, the patch below will work= ,=20 > >but > >> J> >> I do not want to check it in as its still temporary. > >> J> >> > >> J> >> Address questions to me, > >> J> > > >> J> >Okay, I have a question. Could you elaborate on just what the=20 > >problem is? > >> J> >(I mean, since it's KNOWN and all...) I'm just having a hard time= =20 > >figuring > >> J> >out what problem could possibly be fixed by setting the RX interru= pt > >> J> >delay timer to a non-zero value (especially since elsewhere in the= =20 > >em(4) > >> J> >source it says that doing so is a Bad Thing (tm)). > >> J> > >> J> saying its known to be a problem doesnt mean its cause is known :) > >> J> They discovered that setting this eliminated the problem, but we > >> J> immediately pointed out that this is, as you pointed out, a Bad > >> J> Thing on other hardware, so the investigation continues, there is > >> J> always a communication lag on these kind of things, so I dont know > >> J> if it has been resolved yet or not. > >> J> > >> J> I just dont think this patch will become the final way to solve thi= s, > >> J> but we shall see :) > >> > >> Good to know that there is progress on this. Thanks! I will try the pa= tch > >> on my Lenovo T60 notebook, where the problem is also present. AFAIK, it > >> is present on any Lenovo notebook with 82573 NIC. > >> > >> Can you please acknowledge that another bug with Lenovo + em(4) is=20 > >known? I > >> mean the problem, that em(4) isn't initialized properly on kernel boot= ,=20 > >if > >> the link is down. I have already reported this to you, and you said th= at > >> I probably have bad hardware. Since that time, I've found several simi= lar > >> reports about Lenovo notebooks and em(4) driver in FreeBSD. > > > >Hey Gleb, > > > >Acknowledge... I can do better than that, I have a fix for this problem,= =20 > >and > >its not temporary. Here is the code change (not a patch, I'm very busy), > >its in hardware_init, should be obvious how to patch: > > > > /* Make sure we have a good EEPROM before we read from it */ > > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > > /* > > ** Some PCI-E parts fail the first check due to > > ** the link being in sleep state, call it again, > > ** if it fails a second time its a real issue. > > */ > > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > > device_printf(dev, > > "The EEPROM Checksum Is Not Valid\n"); > > return (EIO); > > } > > } > > > >This is already checked into my code base at Intel, I've just been too > >busy to do anything with it, be my guest if you wish to check it in after > >testing... > > > >Cheers, > > > >Jack > > >=20 > LOL, opps, I just realized, this code reflects the new shared code > that I am in the process of releasing, in order for this to work in > 6.2 change 'e1000_validate_nvm_checksum' to > 'em_validate_eeprom_checksum' and all should be clear :) >=20 This worked for me. (hoping it will get committed to -STABLE soonish) --=20 Louis Kowolowski KE7BAX louisk@cryptomonkeys.com Cryptomonkeys: http://www.cryptomonkeys.com/~louisk Warning: Do not point laser at remaining eye! --1Ow488MNN9B9o/ov Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFtp8sZk0r6oAkN7YRAt81AJ0aIkaFqp8wVDq2xEMeSR9jyjT66QCfXXoC 4+nUzLdBURjLtxuCOD1FEkM= =voHN -----END PGP SIGNATURE----- --1Ow488MNN9B9o/ov-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 01:46:58 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BD70916A401 for ; Wed, 24 Jan 2007 01:46:58 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 5743E13C441 for ; Wed, 24 Jan 2007 01:46:58 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so426785nfc for ; Tue, 23 Jan 2007 17:46:57 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BfnBouBmKDf+hwb1WtcIbSphbnr4AsHUuXtragpKMltcXxGLjlKOHaVwTJxR1mwniKPsx8rfsG2kSGC1GxIknp+UHjlI12RPuQ3kvtpH47A9muFy0loh7YG8KQJsdK2NN+Amj1CXMJUHa+1u+1hvV+HT+T26yljVQGzFUiE2y+w= Received: by 10.82.118.2 with SMTP id q2mr46409buc.1169603216749; Tue, 23 Jan 2007 17:46:56 -0800 (PST) Received: by 10.82.127.12 with HTTP; Tue, 23 Jan 2007 17:46:51 -0800 (PST) Message-ID: <2a41acea0701231746p5706bda4vb54cb0c83b809e1b@mail.gmail.com> Date: Tue, 23 Jan 2007 17:46:51 -0800 From: "Jack Vogel" To: "Jack Vogel" , freebsd-current@freebsd.org, freebsd-stable@freebsd.org In-Reply-To: <20070123235004.GF1504@cryptomonkeys.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0701171258k16b4c6ebuf1d4794b89d0749b@mail.gmail.com> <20070120065321.DB61216A405@hub.freebsd.org> <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> <20070122083506.GW4485@FreeBSD.org> <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> <2a41acea0701221034j42fed2a9g3934ef187e3964ca@mail.gmail.com> <20070123235004.GF1504@cryptomonkeys.com> Cc: Subject: Re: Lenovo X60 em workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 01:46:58 -0000 On 1/23/07, Louis Kowolowski wrote: > On Mon, Jan 22, 2007 at 10:34:48AM -0800, Jack Vogel wrote: > > On 1/22/07, Jack Vogel wrote: > > >On 1/22/07, Gleb Smirnoff wrote: > > >> Jack, > > >> > > >> On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote: > > >> J> >> Since this was just seen, and the patch below validated as working > > >I > > >> J> >wanted > > >> J> >> to send general email to capture this: > > >> J> >> > > >> J> >> The Lenovo X60 can have issues with long ping times, this is a > > >KNOWN > > >> J> >> hardware problem, and Intel is working with IBM/Lenovo, a final > > >'fix' has > > >> J> >> not been decided on yet. Nevertheless, the patch below will work, > > >but > > >> J> >> I do not want to check it in as its still temporary. > > >> J> >> > > >> J> >> Address questions to me, > > >> J> > > > >> J> >Okay, I have a question. Could you elaborate on just what the > > >problem is? > > >> J> >(I mean, since it's KNOWN and all...) I'm just having a hard time > > >figuring > > >> J> >out what problem could possibly be fixed by setting the RX interrupt > > >> J> >delay timer to a non-zero value (especially since elsewhere in the > > >em(4) > > >> J> >source it says that doing so is a Bad Thing (tm)). > > >> J> > > >> J> saying its known to be a problem doesnt mean its cause is known :) > > >> J> They discovered that setting this eliminated the problem, but we > > >> J> immediately pointed out that this is, as you pointed out, a Bad > > >> J> Thing on other hardware, so the investigation continues, there is > > >> J> always a communication lag on these kind of things, so I dont know > > >> J> if it has been resolved yet or not. > > >> J> > > >> J> I just dont think this patch will become the final way to solve this, > > >> J> but we shall see :) > > >> > > >> Good to know that there is progress on this. Thanks! I will try the patch > > >> on my Lenovo T60 notebook, where the problem is also present. AFAIK, it > > >> is present on any Lenovo notebook with 82573 NIC. > > >> > > >> Can you please acknowledge that another bug with Lenovo + em(4) is > > >known? I > > >> mean the problem, that em(4) isn't initialized properly on kernel boot, > > >if > > >> the link is down. I have already reported this to you, and you said that > > >> I probably have bad hardware. Since that time, I've found several similar > > >> reports about Lenovo notebooks and em(4) driver in FreeBSD. > > > > > >Hey Gleb, > > > > > >Acknowledge... I can do better than that, I have a fix for this problem, > > >and > > >its not temporary. Here is the code change (not a patch, I'm very busy), > > >its in hardware_init, should be obvious how to patch: > > > > > > /* Make sure we have a good EEPROM before we read from it */ > > > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > > > /* > > > ** Some PCI-E parts fail the first check due to > > > ** the link being in sleep state, call it again, > > > ** if it fails a second time its a real issue. > > > */ > > > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > > > device_printf(dev, > > > "The EEPROM Checksum Is Not Valid\n"); > > > return (EIO); > > > } > > > } > > > > > >This is already checked into my code base at Intel, I've just been too > > >busy to do anything with it, be my guest if you wish to check it in after > > >testing... > > > > > >Cheers, > > > > > >Jack > > > > > > > LOL, opps, I just realized, this code reflects the new shared code > > that I am in the process of releasing, in order for this to work in > > 6.2 change 'e1000_validate_nvm_checksum' to > > 'em_validate_eeprom_checksum' and all should be clear :) > > > This worked for me. > > (hoping it will get committed to -STABLE soonish) OK, hint taken, I'll try and get that committed asap. Jack From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 02:01:33 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 834A216A405; Wed, 24 Jan 2007 02:01:33 +0000 (UTC) (envelope-from Alex.Kovalenko@verizon.net) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.freebsd.org (Postfix) with ESMTP id 6192213C4C2; Wed, 24 Jan 2007 02:01:33 +0000 (UTC) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([70.21.176.159]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JCC002G2OA3V0UD@vms048.mailsrvcs.net>; Tue, 23 Jan 2007 20:01:16 -0600 (CST) Date: Tue, 23 Jan 2007 21:01:09 -0500 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <20070120170723.34c223fb@Magellan.Leidinger.net> To: Alexander Leidinger Message-id: <1169604069.1132.3.camel@RabbitsDen.RabbitsLawn.verizon.net> MIME-version: 1.0 X-Mailer: Evolution 2.8.2.1 FreeBSD GNOME Team Port Content-type: text/plain Content-transfer-encoding: 7bit References: <20070120170723.34c223fb@Magellan.Leidinger.net> Cc: emulation@freebsd.org, current@freebsd.org Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 02:01:33 -0000 On Sat, 2007-01-20 at 17:07 +0100, Alexander Leidinger wrote: > Hi, > > today I committed the last fixes for the showstopper problems (panics) > in the linux 2.6.16 emulation. I intend to switch the default version > to 2.6.16 on i386 "soon" (see below), so please help testing it. > > More recent linux distributions (e.g. FC5) require a 2.6 kernel and > don't work with 2.4.2 anymore. And because FC4 is "abandon-ware" (no > security fixes from fedoralegacy anymore), getting 2.6.16 emulation up > an running is very important. > > If you use a linux program, please add compat.linux.osrelease=2.6.16 > to /etc/sysctl.conf (my desktop is running with 2.6.16 emulation since > some days already). After the next boot (or after running "sysctl > compat.linux.osrelease=2.6.16", please make sure no linux program is > running already) any linux program will start with a linux kernel > version of 2.6.16 instead of 2.4.2. The default linux base port (FC4) > will then use different code paths (e.g. within glibc). In case you > want to switch back to the 2.4.2 emulation without a reboot, please > make sure no linux program is running anymore. > > So far we fixed all known/repeatable problems with acroread, > realplayer, skype and linux firefox. If you encounter strange behavior > with any linux program, please tell us (emulation@freebsd.org) which > program you used, how to repeat the problem, what the problem is, and > if it only is visible with 2.6.16 or with 2.4.2 too. You should also > watch out for messages in the dmesg (unimplemented system calls or other > stuff, this is used to determine the priority of missing syscalls). > Please also have a look at http://wiki.FreeBSD.org/linux-kernel, I > intend to document the known problems there. If you find your problem > there, please tell us about it if you are willing to test fixes. > > We are specially interested in reports (good or bad) on SMP systems. > Please beat the hell out of the linuxulator! > > On amd64 systems we have not the same functionality as on i386, missing > are futexes and TLS. In P4 we already have the futex part covered, but > the TLS part is still missing (anyone with a clue about the kernel side > of TLS on amd64 is welcome to give a hint or two to jkim@ and > rdivacky@). So if you get a message about missing futexes or TLS on > amd64: we know about it (testers for the futex stuff are welcome, but > first you need to use a program which uses futexes and complains). > > As long as we get problem reports with 2.6.16 I will not switch the > default to 2.6.16. If we don't get a report at all, I will switch the > default on i386 to 2.6.16 in two weeks. If we get some problem reports, > we will push back the switch a little bit depending on the severity of > the problem. > > Bye, > Alexander. > With current of yesterday and compat.linux.osrelease=2.6.16 Acrobat Reader, Real Player and Firefox (including Flash plugin) seem to behave on my ThinkPad X60 (SMP machine). Admittedly use was light, but hopefully this report will encourage more people to try switching to new linuxolator. -- Alexandre "Sunny" Kovalenko From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 07:14:03 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id CE9E916A401; Wed, 24 Jan 2007 07:14:03 +0000 (UTC) In-Reply-To: <20070122073611.GC29223@cdnetworks.co.kr> from Pyun YongHyeon at "Jan 22, 2007 04:36:11 pm" To: pyunyh@gmail.com Date: Wed, 24 Jan 2007 07:14:03 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20070124071403.CE9E916A401@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 07:14:03 -0000 > Hi, > > It seems that some revisions of re(4) hardwares(PCIe variants?) still > have Tx checksum offload issues. One user reported the issue said > the attached patch fixed the issue on his box. > Since there are lots of hardwares supported by re(4) I'd like to know > whether the attached patch has no other regressions on re(4) hardwares. > If there are no objections I'll commit it in a week. > > Thanks. > -- > Regards, > Pyun YongHyeon Unfortunately, your patch will break the rl(4) driver, which uses the same header file and also uses RL_MIN_FRAMELEN (and which expects it to be 60). Of course you can easily fix this by making rl(4) and re(4) use different #defines. It may also be a regression for older 8169 cards. There's already a workaround for a TX checksum offload problem wth some of the PCI 8169 cards, which depends on RL_MIN_FRAMELEN being 60. Changing RL_MIN_FRAMELEN may break the workaround for these chips. I'm very confused as to why the chip botches the TX checksumming in this case. Unfortunately, most of this confusion stems from the fact that you didn't specify exactly which chip rev the user with this problem has, or give a test case to trip the bug. I'm assuming this yet another problem with small IP fragments being mangled. That being the case, it should be possible to trip the bug with "ping -s 1473 ." (1473 is 1 byte too large to fit into a 1500 byte frame, which will cause a 1 byte fragment to be sent.) I thought I tested this with my sample PCIe cards though, and didn't see a problem. I'll have to try it again tomorrow. In any case, you can't check this patch in as-is. It may fix things for this one particular NIC, but it will break things for others. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 07:44:04 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C02D16A404; Wed, 24 Jan 2007 07:44:04 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from webaccess-cl.virtdom.com (webaccess-cl.virtdom.com [216.240.101.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2608713C4D9; Wed, 24 Jan 2007 07:44:04 +0000 (UTC) (envelope-from jroberson@chesapeake.net) Received: from [10.0.0.1] (63-226-247-187.tukw.qwest.net [63.226.247.187]) (authenticated bits=0) by webaccess-cl.virtdom.com (8.13.6/8.13.6) with ESMTP id l0O7huAg015967 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Wed, 24 Jan 2007 02:43:57 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Tue, 23 Jan 2007 23:44:15 -0800 (PST) From: Jeff Roberson X-X-Sender: jroberson@10.0.0.1 To: sos@freebsd.org, Ed Schouten In-Reply-To: <20070123182233.GC64263@hoeg.nl> Message-ID: <20070123234350.F564@10.0.0.1> References: <20070123182233.GC64263@hoeg.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current , Laurens Timmermans Subject: Re: Support for nVidia MCP61 (S)ATA controllers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 07:44:04 -0000 Soren maintains the ata code. I just forwarded this message to him to make sure he sees it. Thanks for the report, Jeff On Tue, 23 Jan 2007, Ed Schouten wrote: > Hello, > > A classmate of mine has recently purchased a motherboard with an nVidia > MCP61 chipset. Because the chipset isn't listed in the FreeBSD ATA code > yet, all his disks use UDMA33. We performed some tests and the following > patch causes his ATA controller to run at UDMA133 and his harddisks at > SATA300. > > http://g-rave.nl/junk/freebsd-ata-mcp61.diff > > Could this patch be integrated with FreeBSD CURRENT? If so: could it be > MFC'd as well? > > -- > Ed Schouten > WWW: http://g-rave.nl/ > From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 10:34:06 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C540C16A402 for ; Wed, 24 Jan 2007 10:34:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227]) by mx1.freebsd.org (Postfix) with ESMTP id 77B2B13C471 for ; Wed, 24 Jan 2007 10:34:06 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so133365wxc for ; Wed, 24 Jan 2007 02:34:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=AgouYRV3Vf4/FYqSVionJ/SdAEw2AGQfVXi55az5PVwMS5qb5MxSjUTSQV/ROJUx9KfAKJX5AGKisNsW7jBD55mMBiYhWwMOHzsKr7mTUVj+cBaqB9MtNwk1O5sV+V5h6mX8GG29CVAohGnw9sG115/hT+L6mNJDopgvqX3Zjeo= Received: by 10.90.119.15 with SMTP id r15mr381541agc.1169634845632; Wed, 24 Jan 2007 02:34:05 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id 26sm979342wra.2007.01.24.02.34.02; Wed, 24 Jan 2007 02:34:04 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l0OAZU2A039450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Jan 2007 19:35:30 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0OAZTC6039449; Wed, 24 Jan 2007 19:35:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 24 Jan 2007 19:35:29 +0900 From: Pyun YongHyeon To: Bill Paul Message-ID: <20070124103529.GC37721@cdnetworks.co.kr> References: <20070122073611.GC29223@cdnetworks.co.kr> <20070124071403.CE9E916A401@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070124071403.CE9E916A401@hub.freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@FreeBSD.ORG Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 10:34:06 -0000 On Wed, Jan 24, 2007 at 07:14:03AM +0000, Bill Paul wrote: > > Hi, > > > > It seems that some revisions of re(4) hardwares(PCIe variants?) still > > have Tx checksum offload issues. One user reported the issue said > > the attached patch fixed the issue on his box. > > Since there are lots of hardwares supported by re(4) I'd like to know > > whether the attached patch has no other regressions on re(4) hardwares. > > If there are no objections I'll commit it in a week. > > > > Thanks. > > -- > > Regards, > > Pyun YongHyeon > > Unfortunately, your patch will break the rl(4) driver, which uses the > same header file and also uses RL_MIN_FRAMELEN (and which expects it to > be 60). Of course you can easily fix this by making rl(4) and re(4) use > different #defines. It may also be a regression for older 8169 cards. > There's already a workaround for a TX checksum offload problem wth > some of the PCI 8169 cards, which depends on RL_MIN_FRAMELEN being 60. > Changing RL_MIN_FRAMELEN may break the workaround for these chips. > Ah, I missed that. Thank you for pointing out. > I'm very confused as to why the chip botches the TX checksumming in > this case. Unfortunately, most of this confusion stems from the fact > that you didn't specify exactly which chip rev the user with this > problem has, or give a test case to trip the bug. > Sorry. Here is the information I've got from a user who owns problematic hardware. > laptop: Asus a6je > card: class=0x020000 card=0x11f51043 chip=0x816810ec rev=0x01 hdr=0x00 > vendor=Realtek Semiconductor > device=RTL8168/8111 PCI-E Gigabit Ethernet NIC > On stock re(4) no TCP connections are available on this hardware. Just type "http://www.gmail.com" on browser is sufficient to reproduce on his hardware. If you want captured traffic I can sent it for you even though it's captured on sending host with re(4). I think you can easily spot which packets checksum were broken as many TCP resends are repeated for a sequence number. > I'm assuming this yet another problem with small IP fragments being > mangled. That being the case, it should be possible to trip the bug > with "ping -s 1473 ." (1473 is 1 byte too large to fit into > a 1500 byte frame, which will cause a 1 byte fragment to be sent.) > I thought I tested this with my sample PCIe cards though, and didn't > see a problem. I'll have to try it again tomorrow. > It seems that the hardware in question does not like extra padded bytes for TCP packets. AFAIK the hardware worked without any paddings for non-TCP packets. I couldn't test UDP case due to lack of hardwares but I guess this paticular chip has a working checksum offload implementation. I could have checked a chip revision for the padding work-around but I can't sure which revisions would break the assumtion so I followed NetBSD approach. I've searched all NetBSD archives for the re(4) checksum offload issues but I've failed to find so I thought their fix really works for most hardwares. AFAIK the originator said that "ping -s 1473" without padding work-around also worked on his system. So I guess it breaks checksum only if it sees extra padded bytes in TCP packet. > In any case, you can't check this patch in as-is. It may fix things > for this one particular NIC, but it will break things for others. > Ok, I'll wait for your results and opinions. Thank you very much for looking this issue! > -Bill > > -- > ============================================================================= > -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu > wpaul@windriver.com | Wind River Systems > ============================================================================= > you're just BEGGING to face the moose > ============================================================================= -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 10:37:32 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9696D16A409 for ; Wed, 24 Jan 2007 10:37:32 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id 194BE13C4B9 for ; Wed, 24 Jan 2007 10:37:31 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so119053uge for ; Wed, 24 Jan 2007 02:37:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type; b=RhD6QFVUlK0H+0HXP9NeDImLQxmUNCmVIe1oi5V/+LXfAgu3DMAQW4vjaer9YR/u3Zf/Jv1bzfi71MvwY8LzH5HbeXuvQfpOSUgBl40Qa6eeb0aBY/YWZgPmc5NRHDc7BIYi3N3nb5qeFDd548xSIeTDV+zkUt8AsGnQ4IWobgU= Received: by 10.66.252.4 with SMTP id z4mr471151ugh.1169635050941; Wed, 24 Jan 2007 02:37:30 -0800 (PST) Received: from ?192.168.123.202? ( [195.241.221.201]) by mx.google.com with ESMTP id i39sm781353ugd.2007.01.24.02.37.29; Wed, 24 Jan 2007 02:37:29 -0800 (PST) Message-ID: <45B736DE.1000100@gmail.com> Date: Wed, 24 Jan 2007 11:37:18 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: Bill Paul References: <20070124071403.CE9E916A401@hub.freebsd.org> In-Reply-To: <20070124071403.CE9E916A401@hub.freebsd.org> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/mixed; boundary="------------040206020202080206020709" Cc: pyunyh@gmail.com, freebsd-current@freebsd.org Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 10:37:32 -0000 This is a multi-part message in MIME format. --------------040206020202080206020709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Bill Paul schreef: [...] > I'm very confused as to why the chip botches the TX checksumming in > this case. Unfortunately, most of this confusion stems from the fact > that you didn't specify exactly which chip rev the user with this > problem has, or give a test case to trip the bug. > I am that user, using this card, found in Asus A6JE laptops. From pciconf: card: class=0x020000 card=0x11f51043 chip=0x816810ec rev=0x01 hdr=0x00 vendor=Realtek Semiconductor device=RTL8168/8111 PCI-E Gigabit Ethernet NIC > I'm assuming this yet another problem with small IP fragments being > mangled. That being the case, it should be possible to trip the bug > with "ping -s 1473 ." (1473 is 1 byte too large to fit into > a 1500 byte frame, which will cause a 1 byte fragment to be sent.) > I thought I tested this with my sample PCIe cards though, and didn't > see a problem. I'll have to try it again tomorrow. > ping -s 1473 succeeds both with and without the patch (i.e. ping gives timings), I've included two tcpdumps for further analysis. The bug is visible when logging in to sites such as gmail.com or nl.bol.com (a Dutch shopping site), or when connecting Thunderbird to pop.gmail.com (which uses POP3 with SSL) > > -Bill > > -- Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 --------------040206020202080206020709 Content-Type: application/octet-stream; name="re0.orig" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="re0.orig" 1MOyoQIABAAAAAAAAAAAAGAAAAABAAAAkTS3Rfr1CAAqAAAAKgAAAP///////wAY87eJNAgG AAEIAAYEAAEAGPO3iTTAqHvKAAAAAAAAwKh7/pE0t0Xz9wgAPAAAADwAAAAAGPO3iTQAUBhH 5DwIBgABCAAGBAACAFAYR+Q8wKh7/gAY87eJNMCoe8oAAAAAAAAAAAAAAAAAAAAAAACRNLdF BfgIADwAAAA8AAAAAFAYR+Q8ABjzt4k0CABFAAAVPtsAuUABAADAqHvKwKh7/sAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAkjS3RaH4CABgAAAA6gUAAABQGEfkPAAY87eJNAgARQAF3D7c IABAAQAAwKh7ysCoe/4IAJn6sd0AAUW3NJIACPiBCAkKCwwNDg8QERITFBUWFxgZGhscHR4f ICEiIyQlJicoKSorLC0uLzAxMjM0NZI0t0Wv+AgAPAAAADwAAAAAUBhH5DwAGPO3iTQIAEUA ABU+3AC5QAEAAMCoe8rAqHv+wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACSNLdFAP8IAGAA AADqBQAAABjzt4k0AFAYR+Q8CABFAAXc/A8gAEAB3/fAqHv+wKh7ygAAofqx3QABRbc0kgAI +IEICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1kzS3RWz8 CABgAAAA6gUAAABQGEfkPAAY87eJNAgARQAF3D7dIABAAQAAwKh7ysCoe/4IAJYjsd0AAkW3 NJMACPxWCAkKCwwNDg8QERITFBUWFxgZGhscHR4fICEiIyQlJicoKSorLC0uLzAxMjM0NZM0 t0V4/AgAPAAAADwAAAAAUBhH5DwAGPO3iTQIAEUAABU+3QC5QAEAAMCoe8rAqHv+wAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAACTNLdFuQIJAGAAAADqBQAAABjzt4k0AFAYR+Q8CABFAAXc /Q8gAEAB3vfAqHv+wKh7ygAAniOx3QACRbc0kwAI/FYICQoLDA0ODxAREhMUFRYXGBkaGxwd Hh8gISIjJCUmJygpKissLS4vMDEyMzQ1kzS3RcMCCQA8AAAAPAAAAAAY87eJNABQGEfkPAgA RQAAFf0PALlAAQQGwKh7/sCoe8rAAKH6sd0AAUW3NJIACPiBCAkKCwwNDg8QEZQ0t0VMAAkA YAAAAOoFAAAAUBhH5DwAGPO3iTQIAEUABdw+3iAAQAEAAMCoe8rAqHv+CACSSrHdAANFtzSU AAkALQgJCgsMDQ4PEBESExQVFhcYGRobHB0eHyAhIiMkJSYnKCkqKywtLi8wMTIzNDWUNLdF WQAJADwAAAA8AAAAAFAYR+Q8ABjzt4k0CABFAAAVPt4AuUABAADAqHvKwKh7/sAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAlDS3RZYGCQBgAAAA6gUAAAAY87eJNABQGEfkPAgARQAF3P4P IABAAd33wKh7/sCoe8oAAJpKsd0AA0W3NJQACQAtCAkKCwwNDg8QERITFBUWFxgZGhscHR4f ICEiIyQlJicoKSorLC0uLzAxMjM0NZQ0t0WiBgkAPAAAADwAAAAAGPO3iTQAUBhH5DwIAEUA ABX+DwC5QAEDBsCoe/7AqHvKwACeI7HdAAJFtzSTAAj8VggJCgsMDQ4PEBGVNLdFIgQJAGAA AADqBQAAAFAYR+Q8ABjzt4k0CABFAAXcPt8gAEABAADAqHvKwKh7/ggAjnKx3QAERbc0lQAJ BAMICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1lTS3RTAE CQA8AAAAPAAAAABQGEfkPAAY87eJNAgARQAAFT7fALlAAQAAwKh7ysCoe/7AAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAJU0t0VuCgkAYAAAAOoFAAAAGPO3iTQAUBhH5DwIAEUABdz/DyAA QAHc98Coe/7AqHvKAACWcrHdAARFtzSVAAkEAwgJCgsMDQ4PEBESExQVFhcYGRobHB0eHyAh IiMkJSYnKCkqKywtLi8wMTIzNDWVNLdFegoJADwAAAA8AAAAABjzt4k0AFAYR+Q8CABFAAAV /w8AuUABAgbAqHv+wKh7ysAAmkqx3QADRbc0lAAJAC0ICQoLDA0ODxARljS3RfkHCQBgAAAA 6gUAAABQGEfkPAAY87eJNAgARQAF3D7gIABAAQAAwKh7ysCoe/4IAIqZsd0ABUW3NJYACQfa CAkKCwwNDg8QERITFBUWFxgZGhscHR4fICEiIyQlJicoKSorLC0uLzAxMjM0NZY0t0UHCAkA PAAAADwAAAAAUBhH5DwAGPO3iTQIAEUAABU+4AC5QAEAAMCoe8rAqHv+wAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAACWNLdFQA4JAGAAAADqBQAAABjzt4k0AFAYR+Q8CABFAAXcABAgAEAB 2/fAqHv+wKh7ygAAkpmx3QAFRbc0lgAJB9oICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIj JCUmJygpKissLS4vMDEyMzQ1ljS3RUwOCQA8AAAAPAAAAAAY87eJNABQGEfkPAgARQAAFQAQ ALlAAQEGwKh7/sCoe8rAAJZysd0ABEW3NJUACQQDCAkKCwwNDg8QEZc0t0XQCwkAYAAAAOoF AAAAUBhH5DwAGPO3iTQIAEUABdw+4SAAQAEAAMCoe8rAqHv+CACGwbHdAAZFtzSXAAkLsAgJ CgsMDQ4PEBESExQVFhcYGRobHB0eHyAhIiMkJSYnKCkqKywtLi8wMTIzNDWXNLdF3QsJADwA AAA8AAAAAFAYR+Q8ABjzt4k0CABFAAAVPuEAuUABAADAqHvKwKh7/sAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAlzS3RRoSCQBgAAAA6gUAAAAY87eJNABQGEfkPAgARQAF3AEQIABAAdr3 wKh7/sCoe8oAAI7Bsd0ABkW3NJcACQuwCAkKCwwNDg8QERITFBUWFxgZGhscHR4fICEiIyQl JicoKSorLC0uLzAxMjM0NZc0t0UnEgkAPAAAADwAAAAAGPO3iTQAUBhH5DwIAEUAABUBEAC5 QAEABsCoe/7AqHvKwACSmbHdAAVFtzSWAAkH2ggJCgsMDQ4PEBE= --------------040206020202080206020709 Content-Type: application/octet-stream; name="re0.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="re0.patch" 1MOyoQIABAAAAAAAAAAAAGAAAAABAAAATTS3RZenAwBgAAAA6gUAAABQGEfkPAAY87eJNAgA RQAF3D7WIABAAQAAwKh7ysCoe/4IALBi7NwAAEW3NE0AA6dlCAkKCwwNDg8QERITFBUWFxgZ GhscHR4fICEiIyQlJicoKSorLC0uLzAxMjM0NU00t0WppwMAKgAAACoAAAAAUBhH5DwAGPO3 iTQIAEUAABU+1gC5QAEAAMCoe8rAqHv+wAAAAAAAAABNNLdF6K0DAGAAAADqBQAAABjzt4k0 AFAYR+Q8CABFAAXc6Q8gAEAB8vfAqHv+wKh7ygAAuGLs3AAARbc0TQADp2UICQoLDA0ODxAR EhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1TjS3RRSqAwBgAAAA6gUAAABQ GEfkPAAY87eJNAgARQAF3D7XIABAAQAAwKh7ysCoe/4IAK3P7NwAAUW3NE4AA6n2CAkKCwwN Dg8QERITFBUWFxgZGhscHR4fICEiIyQlJicoKSorLC0uLzAxMjM0NU40t0UiqgMAKgAAACoA AAAAUBhH5DwAGPO3iTQIAEUAABU+1wC5QAEAAMCoe8rAqHv+wAAAAAAAAABONLdFSLEDAGAA AADqBQAAABjzt4k0AFAYR+Q8CABFAAXc6g8gAEAB8ffAqHv+wKh7ygAAtc/s3AABRbc0TgAD qfYICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1TjS3RVKx AwA8AAAAPAAAAAAY87eJNABQGEfkPAgARQAAFeoPALlAARcGwKh7/sCoe8rAALhi7NwAAEW3 NE0AA6dlCAkKCwwNDg8QEU80t0XTsQMAYAAAAOoFAAAAUBhH5DwAGPO3iTQIAEUABdw+2CAA QAEAAMCoe8rAqHv+CACmEezcAAJFtzRPAAOxsggJCgsMDQ4PEBESExQVFhcYGRobHB0eHyAh IiMkJSYnKCkqKywtLi8wMTIzNDVPNLdF4LEDACoAAAAqAAAAAFAYR+Q8ABjzt4k0CABFAAAV PtgAuUABAADAqHvKwKh7/sAAAAAAAAAATzS3RSO4AwBgAAAA6gUAAAAY87eJNABQGEfkPAgA RQAF3OsPIABAAfD3wKh7/sCoe8oAAK4R7NwAAkW3NE8AA7GyCAkKCwwNDg8QERITFBUWFxgZ GhscHR4fICEiIyQlJicoKSorLC0uLzAxMjM0NU80t0UvuAMAPAAAADwAAAAAGPO3iTQAUBhH 5DwIAEUAABXrDwC5QAEWBsCoe/7AqHvKwAC1z+zcAAFFtzROAAOp9ggJCgsMDQ4PEBFQNLdF LLcDAGAAAADqBQAAAFAYR+Q8ABjzt4k0CABFAAXcPtkgAEABAADAqHvKwKh7/ggAoMDs3AAD Rbc0UAADtwEICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1 UDS3RT+3AwAqAAAAKgAAAABQGEfkPAAY87eJNAgARQAAFT7ZALlAAQAAwKh7ysCoe/7AAAAA AAAAAFA0t0V1vQMAYAAAAOoFAAAAGPO3iTQAUBhH5DwIAEUABdzsDyAAQAHv98Coe/7AqHvK AACowOzcAANFtzRQAAO3AQgJCgsMDQ4PEBESExQVFhcYGRobHB0eHyAhIiMkJSYnKCkqKywt Li8wMTIzNDVQNLdFg70DADwAAAA8AAAAABjzt4k0AFAYR+Q8CABFAAAV7A8AuUABFQbAqHv+ wKh7ysAArhHs3AACRbc0TwADsbIICQoLDA0ODxARUTS3RXK9AwBgAAAA6gUAAABQGEfkPAAY 87eJNAgARQAF3D7aIABAAQAAwKh7ysCoe/4IAJp27NwABEW3NFEAA71JCAkKCwwNDg8QERIT FBUWFxgZGhscHR4fICEiIyQlJicoKSorLC0uLzAxMjM0NVE0t0WBvQMAKgAAACoAAAAAUBhH 5DwAGPO3iTQIAEUAABU+2gC5QAEAAMCoe8rAqHv+wAAAAAAAAABRNLdFusMDAGAAAADqBQAA ABjzt4k0AFAYR+Q8CABFAAXc7Q8gAEAB7vfAqHv+wKh7ygAAonbs3AAERbc0UQADvUkICQoL DA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1UTS3RcfDAwA8AAAA PAAAAAAY87eJNABQGEfkPAgARQAAFe0PALlAARQGwKh7/sCoe8rAAKjA7NwAA0W3NFAAA7cB CAkKCwwNDg8QEQ== --------------040206020202080206020709-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 11:12:17 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9AB0716A405 for ; Wed, 24 Jan 2007 11:12:17 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.freebsd.org (Postfix) with ESMTP id 89B9A13C4C5 for ; Wed, 24 Jan 2007 11:12:17 +0000 (UTC) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.13.6) with ESMTP id l0OBCGeO054949; Wed, 24 Jan 2007 03:12:16 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id l0OBCGfM054948; Wed, 24 Jan 2007 03:12:16 -0800 (PST) (envelope-from rizzo) Date: Wed, 24 Jan 2007 03:12:16 -0800 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20070124031216.A54472@xorpc.icir.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Cc: Subject: visibility of symbols defined in a kld module ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 11:12:17 -0000 I have the following problem while building a compat layer for compiling linux drivers on FreeBSD: a piece of code (let's restrict to a kld if it makes things simpler) needs to register some information to the system calling a function: usb_register(&some_data) where some_data is a structure containing various info (callbacks etc) for the code. The problem is, i need to hook the argument of usb_register() to the kld. If i write /* in linux_module_header.h */ extern void *my_module_info; #define usb_register(p) my_module_info = p /* in linux_driver_stub.c, linked together with the rest of the code */ #include "linux_module_header.h" void *my_module_info; I get what i want, but then my_module_info is present in all modules compiled with the same trick, so what happens when the modules are kldloaded ? Does this symbol conflict (i.e. is this equivalent to RTLD_GLOBAL) or each one sees its own symbols (i.e. like RTLD_LOCAL) ? And besides, this would almost surely fail if i compile these things not as modules but as part of the kernel. The other trick i can think of is using some preprocessor-magic to create unique names for the symbol, e.g. compile each kld with -DDRIVER_NAME=pwc, -DDRIVER_NAME=gspca, -DDRIVER_NAME=dvb and then have /* in linux_module_header.h */ #define MODINFO_NAME module_ ## DRIVER_NAME ## _info extern void *MODINFO_NAME; #define usb_register(p) MODINFO_NAME = p /* in linux_driver_stub.c, linked together with the rest of the code */ #include "linux_module_header.h" void *MODINFO_NAME; This way each module has a different symbol and there are no conflict. Other ideas ? cheers luigi From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 12:21:15 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3125B16A408 for ; Wed, 24 Jan 2007 12:21:15 +0000 (UTC) (envelope-from pbowen@fastmail.fm) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id EF5EC13C4CC for ; Wed, 24 Jan 2007 12:21:14 +0000 (UTC) (envelope-from pbowen@fastmail.fm) Received: from out1.internal (unknown [10.202.2.149]) by out1.messagingengine.com (Postfix) with ESMTP id C9E8394909 for ; Wed, 24 Jan 2007 07:01:50 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by out1.internal (MEProxy); Wed, 24 Jan 2007 07:01:50 -0500 X-Sasl-enc: JX0DK+kK4+aJLn6SWHzzPAQlbvhVbe+0Dt6YGPK2K3Sn 1169640110 Received: from [10.51.13.64] (unknown [204.110.228.254]) by mail.messagingengine.com (Postfix) with ESMTP id 5C6EA13565 for ; Wed, 24 Jan 2007 07:01:49 -0500 (EST) Message-ID: <45B74A72.9080108@fastmail.fm> Date: Wed, 24 Jan 2007 06:00:50 -0600 From: Patrick Bowen User-Agent: Thunderbird 1.5.0.9 (X11/20070114) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: WiFi driver companies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 12:21:15 -0000 Which of the wifi drivers are supported by chipset companies that provide source and documentation to the Open Source community? I'd like to support those companies that support FreeBSD. I think that Ralink is one of those companies, but I believe there are others. Thanks, Patrick From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 12:46:58 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B077116A402; Wed, 24 Jan 2007 12:46:58 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw4.york.ac.uk (mail-gw4.york.ac.uk [144.32.128.249]) by mx1.freebsd.org (Postfix) with ESMTP id 66FFF13C45A; Wed, 24 Jan 2007 12:46:53 +0000 (UTC) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw4.york.ac.uk (8.13.6/8.13.6) with ESMTP id l0OCF5fo024597; Wed, 24 Jan 2007 12:15:05 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.8/8.13.6) with ESMTP id l0OCEw7D059698; Wed, 24 Jan 2007 12:15:04 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.8/8.13.6/Submit) id l0OCEve4059697; Wed, 24 Jan 2007 12:14:57 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Jack Vogel In-Reply-To: <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> References: <2a41acea0701171258k16b4c6ebuf1d4794b89d0749b@mail.gmail.com> <20070120065321.DB61216A405@hub.freebsd.org> <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> <20070122083506.GW4485@FreeBSD.org> <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 24 Jan 2007 12:14:57 +0000 Message-Id: <1169640897.59181.20.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: Bill Paul , jon.otterholm@ide.resurscentrum.se, Gleb Smirnoff , freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Lenovo X60 em workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 12:46:58 -0000 On Mon, 2007-01-22 at 10:30 -0800, Jack Vogel wrote: > On 1/22/07, Gleb Smirnoff wrote: > > Jack, > > > > On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote: > > J> >> Since this was just seen, and the patch below validated as working I > > J> >wanted > > J> >> to send general email to capture this: > > J> >> > > J> >> The Lenovo X60 can have issues with long ping times, this is a KNOWN > > J> >> hardware problem, and Intel is working with IBM/Lenovo, a final 'fix' has > > J> >> not been decided on yet. Nevertheless, the patch below will work, but > > J> >> I do not want to check it in as its still temporary. > > J> >> > > J> >> Address questions to me, > > J> > > > J> >Okay, I have a question. Could you elaborate on just what the problem is? > > J> >(I mean, since it's KNOWN and all...) I'm just having a hard time figuring > > J> >out what problem could possibly be fixed by setting the RX interrupt > > J> >delay timer to a non-zero value (especially since elsewhere in the em(4) > > J> >source it says that doing so is a Bad Thing (tm)). > > J> > > J> saying its known to be a problem doesnt mean its cause is known :) > > J> They discovered that setting this eliminated the problem, but we > > J> immediately pointed out that this is, as you pointed out, a Bad > > J> Thing on other hardware, so the investigation continues, there is > > J> always a communication lag on these kind of things, so I dont know > > J> if it has been resolved yet or not. > > J> > > J> I just dont think this patch will become the final way to solve this, > > J> but we shall see :) > > > > Good to know that there is progress on this. Thanks! I will try the patch > > on my Lenovo T60 notebook, where the problem is also present. AFAIK, it > > is present on any Lenovo notebook with 82573 NIC. > > > > Can you please acknowledge that another bug with Lenovo + em(4) is known? I > > mean the problem, that em(4) isn't initialized properly on kernel boot, if > > the link is down. I have already reported this to you, and you said that > > I probably have bad hardware. Since that time, I've found several similar > > reports about Lenovo notebooks and em(4) driver in FreeBSD. > > Hey Gleb, > > Acknowledge... I can do better than that, I have a fix for this problem, and > its not temporary. Here is the code change (not a patch, I'm very busy), > its in hardware_init, should be obvious how to patch: > > /* Make sure we have a good EEPROM before we read from it */ > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > /* > ** Some PCI-E parts fail the first check due to > ** the link being in sleep state, call it again, > ** if it fails a second time its a real issue. > */ > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > device_printf(dev, > "The EEPROM Checksum Is Not Valid\n"); > return (EIO); > } > } > > This is already checked into my code base at Intel, I've just been too > busy to do anything with it, be my guest if you wish to check it in after > testing... Just to add another datapoint - and for the archives - this also appears to fix an issue with the Toshiba Tecra M5L. The "EEPROM Checksum Is Not Valid" message would appear on boot if there was no link on the interface, although the interface would appear to work fine from then on. With this patch, the message no longer appears. I also have problems with connections to networks (only seen when connected to 10 meg half duplex hubs) with long delays on some packets (which I'm assuming is the issue that started this thread) - I haven't been able to verify yet that either patch fixes that, though. Gavin From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 13:36:17 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BCB016A401 for ; Wed, 24 Jan 2007 13:36:17 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 333E813C467 for ; Wed, 24 Jan 2007 13:36:17 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1H9hpY-000NMl-Du; Wed, 24 Jan 2007 15:06:24 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Luigi Rizzo In-reply-to: <20070124031216.A54472@xorpc.icir.org> References: <20070124031216.A54472@xorpc.icir.org> Comments: In-reply-to Luigi Rizzo message dated "Wed, 24 Jan 2007 03:12:16 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 24 Jan 2007 15:06:24 +0200 From: Danny Braniss Message-ID: Cc: current@freebsd.org Subject: Re: visibility of symbols defined in a kld module ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 13:36:17 -0000 > I have the following problem while building a compat layer for compiling > linux drivers on FreeBSD: > a piece of code (let's restrict to a kld if it makes things simpler) > needs to register some information to the system calling a function: > > usb_register(&some_data) > > where some_data is a structure containing various info (callbacks etc) > for the code. > The problem is, i need to hook the argument of usb_register() to the kld. > > If i write > > /* in linux_module_header.h */ > extern void *my_module_info; > > #define usb_register(p) my_module_info = p > > /* in linux_driver_stub.c, linked together with the rest of the code */ > > #include "linux_module_header.h" > void *my_module_info; > > I get what i want, but then my_module_info is present in all modules > compiled with the same trick, so what happens when the modules are > kldloaded ? Does this symbol conflict (i.e. is this equivalent to RTLD_GLOBAL) > or each one sees its own symbols (i.e. like RTLD_LOCAL) ? > > And besides, this would almost surely fail if i compile these things > not as modules but as part of the kernel. > > The other trick i can think of is using some preprocessor-magic to > create unique names for the symbol, e.g. compile each kld with > -DDRIVER_NAME=pwc, -DDRIVER_NAME=gspca, -DDRIVER_NAME=dvb and then have > > /* in linux_module_header.h */ > #define MODINFO_NAME module_ ## DRIVER_NAME ## _info > > extern void *MODINFO_NAME; > > #define usb_register(p) MODINFO_NAME = p > > /* in linux_driver_stub.c, linked together with the rest of the code */ > > #include "linux_module_header.h" > void *MODINFO_NAME; > > This way each module has a different symbol and there are no conflict. > Other ideas ? /* in linux_module_header.h */ #define LINUX_MODULE(name) \ static __inline usb_register(p)\ {\ extern void *module_##name##_info;\ module_##name##_info = p;\ } #define LINUX_MODULE_DCL(name)\ LINUX_MODULE(name)\ void *module_##name##_info /* in linux_driver_stub.c */ #include "linux_module_header.h" LINUX_MODULE_DCL(pwc); /* and in the rest of the code */ #include "linux_module_header.h" LINUX_MODULE(pwc); cheers, danny From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 14:26:27 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8BC316A401 for ; Wed, 24 Jan 2007 14:26:27 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from rusty.kulnet.kuleuven.ac.be (rusty.kulnet.kuleuven.ac.be [134.58.240.42]) by mx1.freebsd.org (Postfix) with ESMTP id 69CBC13C45A for ; Wed, 24 Jan 2007 14:26:27 +0000 (UTC) (envelope-from tijl@ulyssis.org) Received: from localhost (localhost [127.0.0.1]) by rusty.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 852ED1D7813; Wed, 24 Jan 2007 15:26:26 +0100 (CET) Received: from smtp02.kuleuven.be (lepidus.kulnet.kuleuven.ac.be [134.58.240.72]) by rusty.kulnet.kuleuven.ac.be (Postfix) with ESMTP id 626CC1D788A; Wed, 24 Jan 2007 15:26:25 +0100 (CET) Received: from kalimero.kotnet.org (kalimero.kotnet.org [10.4.16.222]) by smtp02.kuleuven.be (Postfix) with ESMTP id 2DFBC2CAA72; Wed, 24 Jan 2007 15:26:25 +0100 (CET) Received: from kalimero.kotnet.org (kalimero.kotnet.org [127.0.0.1]) by kalimero.kotnet.org (8.13.8/8.13.8) with ESMTP id l0OEQN4C003757; Wed, 24 Jan 2007 15:26:24 +0100 (CET) (envelope-from tijl@ulyssis.org) From: Tijl Coosemans To: freebsd-current@freebsd.org Date: Wed, 24 Jan 2007 15:26:19 +0100 User-Agent: KMail/1.9.5 References: <20070120170723.34c223fb@Magellan.Leidinger.net> <1169604069.1132.3.camel@RabbitsDen.RabbitsLawn.verizon.net> In-Reply-To: <1169604069.1132.3.camel@RabbitsDen.RabbitsLawn.verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701241526.23353.tijl@ulyssis.org> X-Virus-Scanned: by KULeuven Antivirus Cluster Cc: emulation@freebsd.org, Alexander Leidinger , "Alexandre \"Sunny\" Kovalenko" Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 14:26:27 -0000 On Wednesday 24 January 2007 03:01, Alexandre "Sunny" Kovalenko wrote: > With current of yesterday and compat.linux.osrelease=2.6.16 Acrobat > Reader, Real Player and Firefox (including Flash plugin) seem to behave What flash version? Flash plugin 9 is still very unstable for me (2.4.2 and 2.6.16). Any YouTube video crashes it after anywhere from 5 to 50 seconds. From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 14:41:14 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2364C16A403; Wed, 24 Jan 2007 14:41:14 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.freebsd.org (Postfix) with ESMTP id AB1A613C45A; Wed, 24 Jan 2007 14:41:13 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id l0OEfBCe026281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Jan 2007 15:41:11 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id l0OEfB0d026280; Wed, 24 Jan 2007 15:41:11 +0100 (CET) Date: Wed, 24 Jan 2007 15:41:11 +0100 From: Divacky Roman To: Tijl Coosemans Message-ID: <20070124144111.GA25708@stud.fit.vutbr.cz> References: <20070120170723.34c223fb@Magellan.Leidinger.net> <1169604069.1132.3.camel@RabbitsDen.RabbitsLawn.verizon.net> <200701241526.23353.tijl@ulyssis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200701241526.23353.tijl@ulyssis.org> User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: emulation@freebsd.org, Alexander Leidinger , freebsd-current@freebsd.org, Alexandre Sunny Kovalenko Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 14:41:14 -0000 On Wed, Jan 24, 2007 at 03:26:19PM +0100, Tijl Coosemans wrote: > On Wednesday 24 January 2007 03:01, Alexandre "Sunny" Kovalenko wrote: > > With current of yesterday and compat.linux.osrelease=2.6.16 Acrobat > > Reader, Real Player and Firefox (including Flash plugin) seem to behave > > What flash version? Flash plugin 9 is still very unstable for me (2.4.2 > and 2.6.16). Any YouTube video crashes it after anywhere from 5 to 50 > seconds. same here.. but people report problems on 6.x as well so I dont think its problem of linuxulator (I might be wrong of course) From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 15:45:43 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E95616A406 for ; Wed, 24 Jan 2007 15:45:43 +0000 (UTC) (envelope-from moellera@googlemail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id D149B13C45D for ; Wed, 24 Jan 2007 15:45:42 +0000 (UTC) (envelope-from moellera@googlemail.com) Received: by ug-out-1314.google.com with SMTP id o2so181882uge for ; Wed, 24 Jan 2007 07:45:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:user-agent:mime-version:to:subject:content-type:content-transfer-encoding:from; b=dG3rhUQ9lii3m/6FfWKBEu/SV2oSNc3UtgsCCAre18dO3OsFmNFIpGb3Qh0EbsUQAecY31WsUit83Wpzbg1KjmTGSJCODntGZrNjSNhxtgMld+Ip8nAdNfGP5MD73IFNbvgLyrpBU4qphHGzpIIVtLl5A8hh1Xf9bvfaiR67BdE= Received: by 10.66.242.20 with SMTP id p20mr1174664ugh.1169651837200; Wed, 24 Jan 2007 07:17:17 -0800 (PST) Received: from ?192.168.0.2? ( [80.132.233.142]) by mx.google.com with ESMTP id 27sm1147193ugp.2007.01.24.07.17.16; Wed, 24 Jan 2007 07:17:16 -0800 (PST) Message-ID: <45B778DD.4060204@gmail.com> Date: Wed, 24 Jan 2007 16:18:53 +0100 User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit From: Andreas Moeller Cc: Subject: [PATCH] if_em comments X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 15:45:43 -0000 Hello, there are two tiny errors in if_em.c. Sorry for wasting your time. ;-) --- if_em.c~ 2007-01-24 16:06:15.000000000 +0100 +++ if_em.c 2007-01-24 16:06:53.000000000 +0100 @@ -806,7 +806,7 @@ * XXX * Since resetting hardware takes a very long time * and results in link renegotiation we only - * initialize the hardware only when it is absolutely + * initialize the hardware when it is absolutely * required. */ ifp->if_flags |= IFF_UP; @@ -2103,7 +2103,7 @@ adapter->hw.hw_addr = (uint8_t *)&adapter->osdep.mem_bus_space_handle; if (adapter->hw.mac_type > em_82543) { - /* Figure our where our IO BAR is ? */ + /* Figure out where our IO BAR is ? */ for (rid = PCIR_BAR(0); rid < PCIR_CIS;) { val = pci_read_config(dev, rid, 4); if (EM_BAR_TYPE(val) == EM_BAR_TYPE_IO) { From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 16:11:41 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59E3016A403 for ; Wed, 24 Jan 2007 16:11:41 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id EB59A13C44B for ; Wed, 24 Jan 2007 16:11:40 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so187779uge for ; Wed, 24 Jan 2007 08:11:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SibRFPpmS41Do+UjtY7gmZem96yfAtoUiGGbDujpLciMijS20jX7PclbLou6TuAvK0bOOFF1I1rIvr2LcLb9+Jo7tRo6fTyLmyxrMooQMRvn9qPyVUKt1rhoLYQNj9Rq342+cCs/dwc/EnS6plI5JBz1rblHDccq9dCH7UksqsA= Received: by 10.82.105.13 with SMTP id d13mr257348buc.1169655099130; Wed, 24 Jan 2007 08:11:39 -0800 (PST) Received: by 10.82.191.16 with HTTP; Wed, 24 Jan 2007 08:11:38 -0800 (PST) Message-ID: Date: Wed, 24 Jan 2007 08:11:38 -0800 From: "Kip Macy" To: "Patrick Bowen" , current@freebsd.org In-Reply-To: <45B74A72.9080108@fastmail.fm> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45B74A72.9080108@fastmail.fm> Cc: Subject: Re: WiFi driver companies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 16:11:41 -0000 It has frequently been mentioned that Ralink is open. However, I have no vendor contact information so I cannot confirm that. For maintaining and extending the ralink drivers I rely on the linux driver put out by ralink as a reference. The atheros driver is extremely well supported, and for the foreseeable future will continue to be your best choice when using freebsd. To the best of my knowledege the only chipset which has publicly available documentation is the Prism II with Intersil firmware - which is supported by wi(4) (which I wish everyone would throwaway so I could stop throwing band-aid after band-aid at it and spend the time adding 11n support). Cheers, Kip On 1/24/07, Patrick Bowen wrote: > Which of the wifi drivers are supported by chipset companies that > provide source and documentation to the Open Source community? I'd like > to support those companies that support FreeBSD. > > > I think that Ralink is one of those companies, but I believe there are > others. > > Thanks, > Patrick > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 17:03:44 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C831B16A401 for ; Wed, 24 Jan 2007 17:03:44 +0000 (UTC) (envelope-from jr@jrssite.com) Received: from iris.acsalaska.net (iris.acsalaska.net [209.112.173.229]) by mx1.freebsd.org (Postfix) with ESMTP id 94D6E13C441 for ; Wed, 24 Jan 2007 17:03:44 +0000 (UTC) (envelope-from jr@jrssite.com) Received: from [127.0.0.1] (209-193-47-24-cdsl-rb1.fai.acsalaska.net [209.193.47.24]) by iris.acsalaska.net (8.13.8/8.13.8) with ESMTP id l0OGpwoh053612; Wed, 24 Jan 2007 07:51:59 -0900 (AKST) (envelope-from jr@jrssite.com) Message-ID: <45B79066.90203@jrssite.com> Date: Wed, 24 Jan 2007 07:59:18 -0900 From: JR Dalrymple User-Agent: Thunderbird 1.5.0.4 (X11/20060621) MIME-Version: 1.0 To: Kip Macy , current@freebsd.org References: <45B74A72.9080108@fastmail.fm> In-Reply-To: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020002080608000008080608" X-ACS-Spam-Status: no X-ACS-Spam-Score: 2 (xx) X-ACS-Spam-Tests: ACS_BOGUS_LOCALHOST X-ACS-Scanned-By: MD 2.57; SA 3.1.6; spamdefang 1.117 Cc: Subject: Re: WiFi driver companies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 17:03:45 -0000 This is a cryptographically signed message in MIME format. --------------ms020002080608000008080608 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Kip Macy wrote: > which is supported by wi(4) > (which I wish everyone would throwaway so I could stop throwing > band-aid after band-aid at it and spend the time adding 11n support). > You tell me what you'd prefer to spend your time writing code for, and that is what I'll buy in the future. -JR --------------ms020002080608000008080608 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII9zCC AtYwggI/oAMCAQICEHDdyABj2Sfcf2e9Vu2bd1UwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UE BhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA2MDgyNDAyMjcxNloX DTA3MDgyNDAyMjcxNlowQDEfMB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEdMBsG CSqGSIb3DQEJARYOanJAanJzc2l0ZS5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK AoIBAQDpumaOInLMznNEI5UNZbYoGfmtxVSzI2WSzxi0u5bJr8HOMQeBnwH9q8rWexWoj8LI fmcaeLslIFzWJ3EUWFJlHy1zt8lRGKE7Q85hw2YXQE+SzNY1zXlFkit/MSF7ghkb73N70DkU tN/N/7TWKtait2nNFk0sYoaj7nkC+zluU7NyNSU5uPOjQsg2fhhHzvOoYTVg1wT2bdnZI1hS ShMph6TvBih4TCLRv4WirM/96wUJ3Q3e7RsUy6EuJLYMPIzU9YBmFlgxm/vsYYJw0uaN5He5 n2GUyLcXPZdSQak+/ILyjuqU1TX0h2PoCwmvKd19Ydc+Xc6jGkZsU9usQ3p3AgMBAAGjKzAp MBkGA1UdEQQSMBCBDmpyQGpyc3NpdGUuY29tMAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEF BQADgYEArfsPYvQj2BNmBZkx3Y8Y8yQUDCIbMhARdCyZAx8B0vwZQMhuhBfejpHXl9fzUp+e ZRO4bThPhTbHlcZlx2a02RR003ckudoFusQgzPAApTsWDxOojd1uBsv76Zt9CVH18M3t3lb9 Ey7JXvGWWqyXsaS1N8PbqP9rsSVY4D0NNygwggLWMIICP6ADAgECAhBw3cgAY9kn3H9nvVbt m3dVMA0GCSqGSIb3DQEBBQUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQTAeFw0wNjA4MjQwMjI3MTZaFw0wNzA4MjQwMjI3MTZaMEAxHzAdBgNVBAMT FlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxHTAbBgkqhkiG9w0BCQEWDmpyQGpyc3NpdGUuY29t MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6bpmjiJyzM5zRCOVDWW2KBn5rcVU syNlks8YtLuWya/BzjEHgZ8B/avK1nsVqI/CyH5nGni7JSBc1idxFFhSZR8tc7fJURihO0PO YcNmF0BPkszWNc15RZIrfzEhe4IZG+9ze9A5FLTfzf+01irWordpzRZNLGKGo+55Avs5blOz cjUlObjzo0LINn4YR87zqGE1YNcE9m3Z2SNYUkoTKYek7wYoeEwi0b+FoqzP/esFCd0N3u0b FMuhLiS2DDyM1PWAZhZYMZv77GGCcNLmjeR3uZ9hlMi3Fz2XUkGpPvyC8o7qlNU19Idj6AsJ ryndfWHXPl3OoxpGbFPbrEN6dwIDAQABoyswKTAZBgNVHREEEjAQgQ5qckBqcnNzaXRlLmNv bTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBAK37D2L0I9gTZgWZMd2PGPMkFAwi GzIQEXQsmQMfAdL8GUDIboQX3o6R15fX81KfnmUTuG04T4U2x5XGZcdmtNkUdNN3JLnaBbrE IMzwAKU7Fg8TqI3dbgbL++mbfQlR9fDN7d5W/RMuyV7xllqsl7GktTfD26j/a7ElWOA9DTco MIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTATBgNV BAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUg Q29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEk MCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxw ZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIz NTk1OVowYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkp IEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGf MA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31 W/Iadr1/DDph8r9RzgHU5VAKMNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV 84J3PQO+K/67GD4Hv0CAAmTXp6a7n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GU MIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAwQwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50 aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJlZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkG A1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwyLTEzODANBgkqhkiG9w0BAQUF AAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9MIbj4Nh+qLZ82L8D0HFAgk3A8/a3h YWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowgT2Vfldr394fWxghOrvbqNOUQ Gls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCA2QwggNgAgEBMHYwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0 ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhBw3cgAY9kn3H9nvVbtm3dVMAkGBSsO AwIaBQCgggHDMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA3 MDEyNDE2NTkxOFowIwYJKoZIhvcNAQkEMRYEFBxm8c7EgNKOe444QOSRKCcXHdRQMFIGCSqG SIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFA MAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGFBgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYT AlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNU aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQcN3IAGPZJ9x/Z71W7Zt3VTCB hwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQQIQcN3IAGPZJ9x/Z71W7Zt3VTANBgkqhkiG9w0BAQEFAASCAQAE1Smk8vxg kBpOOqyy019drNYT81cRMofsCcFkSNnp1oa7UxkZFmh2hd6IQmrBDknc8QKzUtfQwb+DTEKW mgkpaYon1QM/pBrXI5XoEruw1BsIHD85eQIkD9skpeJU+QC38zj0vWA93M+gRAI4FZkgZHZU bV7K8H9jM3g9fDln+yz2U38jGBNGb7ZlZnw8Aa5k77KXOYKqXO9xOea7eF1+BxkiB2MJPz98 vo3JaDGRBHRqcL9jq5Lbe3fcyvs46OF9KiaCy/uAIsEkiJMWsTg/ZV6iprPx9t/2d0kyOyLw FNBIc/GfXkmu8nAK9/mzhfUnm2EjyPJXq+R0o7nHjXHSAAAAAAAA --------------ms020002080608000008080608-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 18:10:52 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DCFF816A400 for ; Wed, 24 Jan 2007 18:10:52 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id ADAA813C43E for ; Wed, 24 Jan 2007 18:10:52 +0000 (UTC) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l0OHsRdF037907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Jan 2007 09:54:28 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <45B79D53.5080503@errno.com> Date: Wed, 24 Jan 2007 09:54:27 -0800 From: Sam Leffler User-Agent: Thunderbird 1.5.0.8 (X11/20061115) MIME-Version: 1.0 To: Kip Macy References: <45B74A72.9080108@fastmail.fm> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Patrick Bowen , current@freebsd.org Subject: Re: WiFi driver companies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 18:10:52 -0000 Kip Macy wrote: > It has frequently been mentioned that Ralink is open. However, I have > no vendor contact information so I cannot confirm that. For > maintaining and extending the ralink drivers I rely on the linux > driver put out by ralink as a reference. The atheros driver is > extremely well supported, and for the foreseeable future will continue > to be your best choice when using freebsd. To the best of my > knowledege the only chipset which has publicly available documentation > is the Prism II with Intersil firmware - which is supported by wi(4) > (which I wish everyone would throwaway so I could stop throwing > band-aid after band-aid at it and spend the time adding 11n support). FWIW the Prism docs were never public; they were just so widely circulated under the table that it just seemed like that :) I know of no wifi vendors that openly distribute information about their products (though something makes me think atmel does/did?). ralink has never responded to my requests for information despite various folks claims. Most vendors just stick out linux drivers and people take 'em apart to do bsd drivers. Sam From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 19:02:03 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id E80FB16A403; Wed, 24 Jan 2007 19:02:03 +0000 (UTC) In-Reply-To: <45B736DE.1000100@gmail.com> from Rene Ladan at "Jan 24, 2007 11:37:18 am" To: r.c.ladan@gmail.com (Rene Ladan) Date: Wed, 24 Jan 2007 19:02:03 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM829511406-21919-0_ Content-Transfer-Encoding: 7bit Message-Id: <20070124190203.E80FB16A403@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: pyunyh@gmail.com, freebsd-current@freebsd.org Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 19:02:04 -0000 --ELM829511406-21919-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Bill Paul schreef: > [...] > > > I'm very confused as to why the chip botches the TX checksumming in > > this case. Unfortunately, most of this confusion stems from the fact > > that you didn't specify exactly which chip rev the user with this > > problem has, or give a test case to trip the bug. > > > I am that user, using this card, found in Asus A6JE laptops. From pciconf: > > card: class=0x020000 card=0x11f51043 chip=0x816810ec rev=0x01 hdr=0x00 > vendor=Realtek Semiconductor > device=RTL8168/8111 PCI-E Gigabit Ethernet NIC > > > I'm assuming this yet another problem with small IP fragments being > > mangled. That being the case, it should be possible to trip the bug > > with "ping -s 1473 ." (1473 is 1 byte too large to fit into > > a 1500 byte frame, which will cause a 1 byte fragment to be sent.) > > I thought I tested this with my sample PCIe cards though, and didn't > > see a problem. I'll have to try it again tomorrow. > > > ping -s 1473 succeeds both with and without the patch (i.e. > ping gives timings), I've included two tcpdumps for further analysis. Unfortunately, these packet dumps don't help me: I need a packet dump that shows the failure, and these don't. > The bug is visible when logging in to sites such as gmail.com or > nl.bol.com (a Dutch shopping site), or when connecting Thunderbird to > pop.gmail.com (which uses POP3 with SSL) Hm. Ok, apparently the TCP segments that cause the problem look like this: 10:41:54.607019 00:03:47:a6:3f:c0 > 00:00:0c:07:ac:2e, ethertype IPv4 (0x0800), length 54: 147.11.46.221.63693 > 216.239.57.83.80: . ack 1 win 65535 I captured this by doing 'telnet gmail.com 80' from my system at work. I contrived a quick test where I wrote a small routine to send a packet with exactly these contents and duplicated the problem with my sample 8111B/8168B card (the frame isn't mangled as badly as the small IP fragment case, but the TCP checksum is wrong). The RTL8101E (10/100) PCIe adapter also botches the checksum in the same way. The earlier PCI cards do not. Based on testing with my sample adapters, I think the right thing to do is skip the software padding in the TCP case. It appears that even the older 8169 adapters that botch the small IP fragment case will correctly handle this small TCP segment case. I'm attaching a patch which should fix the problem without breaking the workaround for other NICs. If you verify that this patch also fixes your problem, then this patch should be checked in instead of the other one. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= --ELM829511406-21919-0_ Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename=re.patch Content-Description: re.patch Content-Transfer-Encoding: 7bit --- if_re.c.orig Wed Jan 24 10:38:14 2007 +++ if_re.c Wed Jan 24 10:40:06 2007 @@ -2075,9 +2075,13 @@ * the mbuf chain has too many fragments so the coalescing code * below can assemble the packet into a single buffer that's * padded out to the mininum frame size. + * + * Note: this appears unnecessary for TCP, and doing for TCP + * with PCIe adapters seems to result in bad checksums. */ - if (arg.rl_flags && (*m_head)->m_pkthdr.len < RL_MIN_FRAMELEN) + if (arg.rl_flags && !(arg.rl_flags & CSUM_TCP) && + (*m_head)->m_pkthdr.len < RL_MIN_FRAMELEN) error = EFBIG; else error = bus_dmamap_load_mbuf(sc->rl_ldata.rl_mtag, map, --ELM829511406-21919-0_-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 19:13:09 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id D17A016A403; Wed, 24 Jan 2007 19:13:09 +0000 (UTC) In-Reply-To: <20070124190203.E80FB16A403@hub.freebsd.org> from Bill Paul at "Jan 24, 2007 07:02:03 pm" To: wpaul@FreeBSD.ORG (Bill Paul) Date: Wed, 24 Jan 2007 19:13:09 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="ELM82951187:-21975-0_" Content-Transfer-Encoding: 7bit Message-Id: <20070124191309.D17A016A403@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: pyunyh@gmail.com, freebsd-current@freebsd.org, r.c.ladan@gmail.com Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 19:13:09 -0000 --ELM82951187:-21975-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Based on testing with my sample adapters, I think the right thing to do > is skip the software padding in the TCP case. It appears that even > the older 8169 adapters that botch the small IP fragment case will correctly > handle this small TCP segment case. I'm attaching a patch which should > fix the problem without breaking the workaround for other NICs. If you > verify that this patch also fixes your problem, then this patch should > be checked in instead of the other one. Crap... I just realized as I hit the send button that I was testing for the wrong flag in the rl_flags field. I'm sending the patch again, hopefully correct this time. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= --ELM82951187:-21975-0_ Content-Type: text/plain; charset=US-ASCII Content-Disposition: attachment; filename=re.patch Content-Description: re.patch Content-Transfer-Encoding: 7bit --- if_re.c.orig Wed Jan 24 10:38:14 2007 +++ if_re.c Wed Jan 24 11:06:21 2007 @@ -2075,9 +2075,13 @@ * the mbuf chain has too many fragments so the coalescing code * below can assemble the packet into a single buffer that's * padded out to the mininum frame size. + * + * Note: this appears unnecessary for TCP, and doing it for TCP + * with PCIe adapters seems to result in bad checksums. */ - if (arg.rl_flags && (*m_head)->m_pkthdr.len < RL_MIN_FRAMELEN) + if (arg.rl_flags && !(arg.rl_flags & RL_TDESC_CMD_TCPCSUM) && + (*m_head)->m_pkthdr.len < RL_MIN_FRAMELEN) error = EFBIG; else error = bus_dmamap_load_mbuf(sc->rl_ldata.rl_mtag, map, --ELM82951187:-21975-0_-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 23:36:49 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3D6F16A401 for ; Wed, 24 Jan 2007 23:36:48 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 81A4C13C4A6 for ; Wed, 24 Jan 2007 23:36:48 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so280035uge for ; Wed, 24 Jan 2007 15:36:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=AToOexL8KS+IaELIWQJU9B60eaOv0wVWWUgl3Oqn0Cuk59kqfSOXYeVSIrIe6Le1NSEVO35OnKk7+HQq+vaCscEgvAWpBhlEa7swiOWwXFVaMvmhDwLCc0tVqzb0d6YNF8VppCuBLafehsUskgavK8Q2dIlWMV3KZLjaeH4qMug= Received: by 10.82.169.4 with SMTP id r4mr573285bue.1169681807126; Wed, 24 Jan 2007 15:36:47 -0800 (PST) Received: by 10.82.127.12 with HTTP; Wed, 24 Jan 2007 15:36:47 -0800 (PST) Message-ID: <2a41acea0701241536y18826df0u3c27da5e7d611a0e@mail.gmail.com> Date: Wed, 24 Jan 2007 15:36:47 -0800 From: "Jack Vogel" To: "Gavin Atkinson" In-Reply-To: <1169640897.59181.20.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0701171258k16b4c6ebuf1d4794b89d0749b@mail.gmail.com> <20070120065321.DB61216A405@hub.freebsd.org> <2a41acea0701201435g6f960b40r3cf0552d87ab2bfd@mail.gmail.com> <20070122083506.GW4485@FreeBSD.org> <2a41acea0701221030x52dd8821pd858ae7e6740ce92@mail.gmail.com> <1169640897.59181.20.camel@buffy.york.ac.uk> Cc: Bill Paul , jon.otterholm@ide.resurscentrum.se, Gleb Smirnoff , freebsd-stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Lenovo X60 em workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 23:36:49 -0000 On 1/24/07, Gavin Atkinson wrote: > On Mon, 2007-01-22 at 10:30 -0800, Jack Vogel wrote: > > On 1/22/07, Gleb Smirnoff wrote: > > > Jack, > > > > > > On Sat, Jan 20, 2007 at 02:35:17PM -0800, Jack Vogel wrote: > > > J> >> Since this was just seen, and the patch below validated as working I > > > J> >wanted > > > J> >> to send general email to capture this: > > > J> >> > > > J> >> The Lenovo X60 can have issues with long ping times, this is a KNOWN > > > J> >> hardware problem, and Intel is working with IBM/Lenovo, a final 'fix' has > > > J> >> not been decided on yet. Nevertheless, the patch below will work, but > > > J> >> I do not want to check it in as its still temporary. > > > J> >> > > > J> >> Address questions to me, > > > J> > > > > J> >Okay, I have a question. Could you elaborate on just what the problem is? > > > J> >(I mean, since it's KNOWN and all...) I'm just having a hard time figuring > > > J> >out what problem could possibly be fixed by setting the RX interrupt > > > J> >delay timer to a non-zero value (especially since elsewhere in the em(4) > > > J> >source it says that doing so is a Bad Thing (tm)). > > > J> > > > J> saying its known to be a problem doesnt mean its cause is known :) > > > J> They discovered that setting this eliminated the problem, but we > > > J> immediately pointed out that this is, as you pointed out, a Bad > > > J> Thing on other hardware, so the investigation continues, there is > > > J> always a communication lag on these kind of things, so I dont know > > > J> if it has been resolved yet or not. > > > J> > > > J> I just dont think this patch will become the final way to solve this, > > > J> but we shall see :) > > > > > > Good to know that there is progress on this. Thanks! I will try the patch > > > on my Lenovo T60 notebook, where the problem is also present. AFAIK, it > > > is present on any Lenovo notebook with 82573 NIC. > > > > > > Can you please acknowledge that another bug with Lenovo + em(4) is known? I > > > mean the problem, that em(4) isn't initialized properly on kernel boot, if > > > the link is down. I have already reported this to you, and you said that > > > I probably have bad hardware. Since that time, I've found several similar > > > reports about Lenovo notebooks and em(4) driver in FreeBSD. > > > > Hey Gleb, > > > > Acknowledge... I can do better than that, I have a fix for this problem, and > > its not temporary. Here is the code change (not a patch, I'm very busy), > > its in hardware_init, should be obvious how to patch: > > > > /* Make sure we have a good EEPROM before we read from it */ > > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > > /* > > ** Some PCI-E parts fail the first check due to > > ** the link being in sleep state, call it again, > > ** if it fails a second time its a real issue. > > */ > > if (e1000_validate_nvm_checksum(&adapter->hw) < 0) { > > device_printf(dev, > > "The EEPROM Checksum Is Not Valid\n"); > > return (EIO); > > } > > } > > > > This is already checked into my code base at Intel, I've just been too > > busy to do anything with it, be my guest if you wish to check it in after > > testing... > > Just to add another datapoint - and for the archives - this also appears > to fix an issue with the Toshiba Tecra M5L. The "EEPROM Checksum Is Not > Valid" message would appear on boot if there was no link on the > interface, although the interface would appear to work fine from then > on. With this patch, the message no longer appears. > > I also have problems with connections to networks (only seen when > connected to 10 meg half duplex hubs) with long delays on some packets > (which I'm assuming is the issue that started this thread) - I haven't > been able to verify yet that either patch fixes that, though. Nice to know its fixing more than expected. Let me know about the last issue when you verify it. Crises have me consumed at work right now, will try to get time to commit by this weekend. Jack From owner-freebsd-current@FreeBSD.ORG Wed Jan 24 23:52:54 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7691516A400 for ; Wed, 24 Jan 2007 23:52:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 33AF613C43E for ; Wed, 24 Jan 2007 23:52:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id f47so130088pye for ; Wed, 24 Jan 2007 15:52:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=DjnZgyzBeOy9XBbOn6r5RL+jtmQCn4PVjPavBOV61iuEvYgZ048qSrewdZ6fUVRZJJwLOM4fFkWTkJsPU2Xhn+TXL3pxOlcju5YktCom3i7+bg2uBALRLOSQSEDbxmhzBzXQ6QrK5GJOyEKP8FOLpGUbNhVU67WiQuIke5rTJ78= Received: by 10.35.126.7 with SMTP id d7mr2565072pyn.1169682773560; Wed, 24 Jan 2007 15:52:53 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTP id f57sm1280545pyh.2007.01.24.15.52.50; Wed, 24 Jan 2007 15:52:52 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id l0ONsP37041670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Jan 2007 08:54:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l0ONsOwm041669; Thu, 25 Jan 2007 08:54:24 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 25 Jan 2007 08:54:24 +0900 From: Pyun YongHyeon To: Bill Paul Message-ID: <20070124235424.GA41550@cdnetworks.co.kr> References: <45B736DE.1000100@gmail.com> <20070124190203.E80FB16A403@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070124190203.E80FB16A403@hub.freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@FreeBSD.ORG, Rene Ladan Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jan 2007 23:52:54 -0000 On Wed, Jan 24, 2007 at 07:02:03PM +0000, Bill Paul wrote: > > Bill Paul schreef: > > [...] > > > > > I'm very confused as to why the chip botches the TX checksumming in > > > this case. Unfortunately, most of this confusion stems from the fact > > > that you didn't specify exactly which chip rev the user with this > > > problem has, or give a test case to trip the bug. > > > > > I am that user, using this card, found in Asus A6JE laptops. From pciconf: > > > > card: class=0x020000 card=0x11f51043 chip=0x816810ec rev=0x01 hdr=0x00 > > vendor=Realtek Semiconductor > > device=RTL8168/8111 PCI-E Gigabit Ethernet NIC > > > > > I'm assuming this yet another problem with small IP fragments being > > > mangled. That being the case, it should be possible to trip the bug > > > with "ping -s 1473 ." (1473 is 1 byte too large to fit into > > > a 1500 byte frame, which will cause a 1 byte fragment to be sent.) > > > I thought I tested this with my sample PCIe cards though, and didn't > > > see a problem. I'll have to try it again tomorrow. > > > > > ping -s 1473 succeeds both with and without the patch (i.e. > > ping gives timings), I've included two tcpdumps for further analysis. > > Unfortunately, these packet dumps don't help me: I need a packet dump > that shows the failure, and these don't. > > > The bug is visible when logging in to sites such as gmail.com or > > nl.bol.com (a Dutch shopping site), or when connecting Thunderbird to > > pop.gmail.com (which uses POP3 with SSL) > > Hm. Ok, apparently the TCP segments that cause the problem look like > this: > > 10:41:54.607019 00:03:47:a6:3f:c0 > 00:00:0c:07:ac:2e, ethertype IPv4 (0x0800), > length 54: 147.11.46.221.63693 > 216.239.57.83.80: . ack 1 win 65535 > > I captured this by doing 'telnet gmail.com 80' from my system at work. > I contrived a quick test where I wrote a small routine to send a packet > with exactly these contents and duplicated the problem with my sample > 8111B/8168B card (the frame isn't mangled as badly as the small IP > fragment case, but the TCP checksum is wrong). The RTL8101E (10/100) PCIe > adapter also botches the checksum in the same way. The earlier PCI cards > do not. > > Based on testing with my sample adapters, I think the right thing to do > is skip the software padding in the TCP case. It appears that even > the older 8169 adapters that botch the small IP fragment case will correctly > handle this small TCP segment case. I'm attaching a patch which should > fix the problem without breaking the workaround for other NICs. If you > verify that this patch also fixes your problem, then this patch should > be checked in instead of the other one. > Since you have the problematic hardware in hand would you verify it works for small UDP case?(i.e. 28 bytes, IP header 20 bytes, UDP header 8 bytes). If you already checked UDP case please ignore this mail. Thank you. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 00:51:51 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CDF9216A400; Thu, 25 Jan 2007 00:51:51 +0000 (UTC) (envelope-from Alex.Kovalenko@verizon.net) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.freebsd.org (Postfix) with ESMTP id B08CD13C455; Thu, 25 Jan 2007 00:51:51 +0000 (UTC) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([70.21.176.159]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JCE001EOFPZ9C04@vms042.mailsrvcs.net>; Wed, 24 Jan 2007 18:51:36 -0600 (CST) Date: Wed, 24 Jan 2007 19:51:25 -0500 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <200701241526.23353.tijl@ulyssis.org> To: Tijl Coosemans Message-id: <1169686286.33062.0.camel@RabbitsDen.RabbitsLawn.verizon.net> MIME-version: 1.0 X-Mailer: Evolution 2.8.2.1 FreeBSD GNOME Team Port Content-type: text/plain Content-transfer-encoding: 7bit References: <20070120170723.34c223fb@Magellan.Leidinger.net> <1169604069.1132.3.camel@RabbitsDen.RabbitsLawn.verizon.net> <200701241526.23353.tijl@ulyssis.org> Cc: emulation@freebsd.org, Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 00:51:51 -0000 On Wed, 2007-01-24 at 15:26 +0100, Tijl Coosemans wrote: > On Wednesday 24 January 2007 03:01, Alexandre "Sunny" Kovalenko wrote: > > With current of yesterday and compat.linux.osrelease=2.6.16 Acrobat > > Reader, Real Player and Firefox (including Flash plugin) seem to behave > > What flash version? Flash plugin 9 is still very unstable for me (2.4.2 > and 2.6.16). Any YouTube video crashes it after anywhere from 5 to 50 > seconds. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Nothing nearly that advanced: RabbitsDen# pkg_info | grep flash linux-flashplugin-7.0r69 Adobe Flash Player NPAPI Plugin RabbitsDen# -- Alexandre "Sunny" Kovalenko From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 13:23:14 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D815216A404 for ; Thu, 25 Jan 2007 13:23:14 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id 726C813C442 for ; Thu, 25 Jan 2007 13:23:14 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so418545uge for ; Thu, 25 Jan 2007 05:23:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=oNS1cVnQeSigDfEI+lp0DKv5oVcuYatmopC/jQQvAaFW/G5l/De/AiJ/f+gZaM012QYAgTHJcF1Kh4Bad59I6HRgh04wV+wtlHKdVMe2zh/tWE4lPqQzLSQ3vs8tDNw8onUGLQhdQElq+HjA6TFnN1YX94xjpr+mMjh/4M2STJY= Received: by 10.67.22.2 with SMTP id z2mr2702601ugi.1169731393336; Thu, 25 Jan 2007 05:23:13 -0800 (PST) Received: from ?192.168.123.202? ( [195.241.221.201]) by mx.google.com with ESMTP id q40sm2785630ugc.2007.01.25.05.23.11; Thu, 25 Jan 2007 05:23:12 -0800 (PST) Message-ID: <45B8AF3E.9030807@gmail.com> Date: Thu, 25 Jan 2007 14:23:10 +0100 From: Rene Ladan User-Agent: Thunderbird 1.5.0.9 (X11/20070119) MIME-Version: 1.0 To: Bill Paul References: <20070124191309.D17A016A403@hub.freebsd.org> In-Reply-To: <20070124191309.D17A016A403@hub.freebsd.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Pyun YongHyeon , current@freebsd.org Subject: Re: Call for re(4) checksum offload testers. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 13:23:14 -0000 Bill Paul schreef: >> Based on testing with my sample adapters, I think the right thing to do >> is skip the software padding in the TCP case. It appears that even >> the older 8169 adapters that botch the small IP fragment case will correctly >> handle this small TCP segment case. I'm attaching a patch which should >> fix the problem without breaking the workaround for other NICs. If you >> verify that this patch also fixes your problem, then this patch should >> be checked in instead of the other one. > > Crap... I just realized as I hit the send button that I was testing > for the wrong flag in the rl_flags field. I'm sending the patch again, > hopefully correct this time. > I just confirmed that I can download email messages in Thunderbird using this patch. Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 14:35:22 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8AAB816A402; Thu, 25 Jan 2007 14:35:22 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (meestal.stack.nl [131.155.140.141]) by mx1.freebsd.org (Postfix) with ESMTP id 4EA5D13C467; Thu, 25 Jan 2007 14:35:22 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 45DFE4AE71; Thu, 25 Jan 2007 15:18:17 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id 2984422890; Thu, 25 Jan 2007 15:18:17 +0100 (CET) Date: Thu, 25 Jan 2007 15:18:17 +0100 From: Jilles Tjoelker To: Robert Watson Message-ID: <20070125141816.GA73998@stack.nl> References: <20070120170723.34c223fb@Magellan.Leidinger.net> <20070122184807.GA26839@home.c0mplx.org> <20070122213039.GA51752@stud.fit.vutbr.cz> <20070122231754.A17361@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070122231754.A17361@fledge.watson.org> X-Operating-System: FreeBSD 5.5-RELEASE-p1 i386 User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Divacky Roman , Kurt Jaeger , freebsd-current@freebsd.org Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 14:35:22 -0000 On Mon, Jan 22, 2007 at 11:18:37PM +0000, Robert Watson wrote: > >just try to kldunload linux module and if that doesnt succeed look at your > >ps ax output for suspicous programs (acroread, skype etc.) > This might well be something useful to add though -- an ABI name exported > via kinfo_proc or such. It would also be useful for telling whether > processes are 32-bit or 64-bit native processes, etc. The /proc//etype file shows this, for example % cat /proc/$$/etype FreeBSD ELF32 You need procfs mounted which is undesirable. The code is in /sys/fs/procfs/procfs_type.c by the way. -- Jilles Tjoelker From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 16:15:47 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C836916A409 for ; Thu, 25 Jan 2007 16:15:47 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6BE5B13C459 for ; Thu, 25 Jan 2007 16:15:47 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0PGE85O028929; Thu, 25 Jan 2007 09:14:09 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 25 Jan 2007 09:14:39 -0700 (MST) Message-Id: <20070125.091439.332275221.imp@bsdimp.com> To: karagodov@gmail.com From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 25 Jan 2007 09:14:09 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: sasyncd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 16:15:47 -0000 In message: "Alexey Karagodov" writes: : is there any plans to port sasyncd from OpenBSD to FreeBSD ? : or just please tell, how can i do it myself Copy the sources to a copy of the FreeBSD tree (save a copy for later) while (compile problems) { type make fix problems } while (runting problems) { fix problems type make } From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 16:18:41 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA7A116A400 for ; Thu, 25 Jan 2007 16:18:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 4EECC13C4BF for ; Thu, 25 Jan 2007 16:18:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0PGGrwV028955; Thu, 25 Jan 2007 09:16:54 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 25 Jan 2007 09:17:24 -0700 (MST) Message-Id: <20070125.091724.-854262499.imp@bsdimp.com> To: lists@swaggi.com From: "M. Warner Losh" In-Reply-To: <20070122171648.M47935@swaggi.com> References: <20070122171648.M47935@swaggi.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 25 Jan 2007 09:16:54 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: 802.11n support? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 16:18:41 -0000 In message: <20070122171648.M47935@swaggi.com> "Yuri Lukin" writes: : Just wondering if there's any plans to add support for 802.11n even though : it's currently just a draft: : : http://wifinetnews.com/archives/007328.html Short answer: yes. Longer answer: I've seen a few developers talking about how to add 802.11n support to the net80211 layer. This will take a little time, so I'm not going to 'out' them until they are ready to come forward. 802.11n adds a lot of stuff, and it isn't just a simple dropin. Warner From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 18:02:18 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B86E116A4A9 for ; Thu, 25 Jan 2007 18:02:17 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6B5D313C45B for ; Thu, 25 Jan 2007 18:02:17 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0PHwbt4029844; Thu, 25 Jan 2007 10:58:38 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 25 Jan 2007 10:59:08 -0700 (MST) Message-Id: <20070125.105908.1120073565.imp@bsdimp.com> To: sam@errno.com From: "M. Warner Losh" In-Reply-To: <45B79D53.5080503@errno.com> References: <45B74A72.9080108@fastmail.fm> <45B79D53.5080503@errno.com> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 25 Jan 2007 10:58:39 -0700 (MST) Cc: kip.macy@gmail.com, pbowen@fastmail.fm, current@freebsd.org Subject: Re: WiFi driver companies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 18:02:18 -0000 In message: <45B79D53.5080503@errno.com> Sam Leffler writes: : Kip Macy wrote: : > It has frequently been mentioned that Ralink is open. However, I have : > no vendor contact information so I cannot confirm that. For : > maintaining and extending the ralink drivers I rely on the linux : > driver put out by ralink as a reference. The atheros driver is : > extremely well supported, and for the foreseeable future will continue : > to be your best choice when using freebsd. To the best of my : > knowledege the only chipset which has publicly available documentation : > is the Prism II with Intersil firmware - which is supported by wi(4) : > (which I wish everyone would throwaway so I could stop throwing : > band-aid after band-aid at it and spend the time adding 11n support). : : FWIW the Prism docs were never public; they were just so widely : circulated under the table that it just seemed like that :) There was a time that one could get access to them fairly easily. You'd download an NDA that said "I won't give copies of this to anybody, but open source drivers are OK," sign it, fax it back and get an access code for the web site. While not, strictly speaking, public, there was a well beaten path for obtaining it. When Intersil sold off the Prism chips, this went away with the new owners, at least initially. I tried a few times after the sale to get updated docs to no avail and then gave up. Warner From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 19:50:35 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6264B16A401 for ; Thu, 25 Jan 2007 19:50:35 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id E8B4913C44C for ; Thu, 25 Jan 2007 19:50:34 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l0PJoOiG003503; Fri, 26 Jan 2007 06:50:24 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l0PJoOW9003502; Fri, 26 Jan 2007 06:50:24 +1100 (EST) (envelope-from peter) Date: Fri, 26 Jan 2007 06:50:24 +1100 From: Peter Jeremy To: "M. Warner Losh" Message-ID: <20070125195024.GL822@turion.vk2pj.dyndns.org> References: <20070125.091439.332275221.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="z4+8/lEcDcG5Ke9S" Content-Disposition: inline In-Reply-To: <20070125.091439.332275221.imp@bsdimp.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-current@freebsd.org, karagodov@gmail.com Subject: Re: sasyncd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 19:50:35 -0000 --z4+8/lEcDcG5Ke9S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 2007-Jan-25 09:14:39 -0700, M. Warner Losh wrote: >In message: > "Alexey Karagodov" writes: >: is there any plans to port sasyncd from OpenBSD to FreeBSD ? >: or just please tell, how can i do it myself > >Copy the sources to a copy of the FreeBSD tree >(save a copy for later) >while (compile problems) { > type make > fix problems >} >while (runting problems) { > fix problems > type make >} diff -u {original sources} {working sources} | send-pr "Port of sasyncd fro= m OpenBSD" --=20 Peter Jeremy --z4+8/lEcDcG5Ke9S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFuQoA/opHv/APuIcRApvoAJ9gXzQ5ETTuBoU0HIlh7El/C9iTYQCeIR/x 1GLDKIedRGxZz3mV49WJ9u0= =oda6 -----END PGP SIGNATURE----- --z4+8/lEcDcG5Ke9S-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 22:06:23 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0926316A403 for ; Thu, 25 Jan 2007 22:06:23 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outR.internet-mail-service.net (outR.internet-mail-service.net [216.240.47.241]) by mx1.freebsd.org (Postfix) with ESMTP id 9709B13C465 for ; Thu, 25 Jan 2007 22:06:22 +0000 (UTC) (envelope-from julian@elischer.org) Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Thu, 25 Jan 2007 13:45:37 -0800 Received: from [10.251.23.190] (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id D49DB125AC4 for ; Thu, 25 Jan 2007 14:06:20 -0800 (PST) Message-ID: <45B929D5.2040901@elischer.org> Date: Thu, 25 Jan 2007 14:06:13 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: chinese use of FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 22:06:23 -0000 The freebsd.org "in the media" page says that some people in China are using FreeBSD and that lenovo is involved. http://www.pacificepoch.com/newsstories/82819_0_5_0_M/ Does anyone have more information on this? Have we received any patches from them? Are any of our chinese committers involved with this project? Does Lenovo have any support for their hardware for us? :-) Julian From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 22:29:29 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6385016A401 for ; Thu, 25 Jan 2007 22:29:29 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id 0AEF513C471 for ; Thu, 25 Jan 2007 22:29:28 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so341375ana for ; Thu, 25 Jan 2007 14:29:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ctFeOOlP9tdzubLXnHKBd7UVMnxIUnkYQv0W/3GE/xrGylTXhcXfCrZg0nlAgyyHTXHH9P689hqyRIvrK1apcA+B151QUJaPgRBKEk3LPAB+zeZw6Z1suuxS+NrdFCcmhxH2GssAKjqAi1CicA4x805TEySNeOAb/10ec8mA9A8= Received: by 10.78.158.11 with SMTP id g11mr1943120hue.1169764165307; Thu, 25 Jan 2007 14:29:25 -0800 (PST) Received: by 10.78.164.20 with HTTP; Thu, 25 Jan 2007 14:29:25 -0800 (PST) Message-ID: Date: Fri, 26 Jan 2007 01:29:25 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "Julian Elischer" In-Reply-To: <45B929D5.2040901@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45B929D5.2040901@elischer.org> X-Google-Sender-Auth: 778a91acbfe7a75b Cc: FreeBSD Current Subject: Re: chinese use of FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 22:29:29 -0000 On 1/26/07, Julian Elischer wrote: > The freebsd.org "in the media" page says that some people in China are > using FreeBSD and that lenovo is involved. > > http://www.pacificepoch.com/newsstories/82819_0_5_0_M/ > > Does anyone have more information on this? > > Have we received any patches from them? > Are any of our chinese committers involved with this project? > Does Lenovo have any support for their hardware for us? :-) There was a presentation about this at EuroBSDCon. The idea is sane (FreeBSD kernel + Linux userland + liters of some glue), the only thing that got me suspicious was the fact that some of the open-source software to be produced will allegedly be only available in binary form and for some money. I guess we were a bit lost in translation, but that's how it sounded. The developers want to give back some code, but this is a government project and it felt like there was going to be some difficulty... From owner-freebsd-current@FreeBSD.ORG Thu Jan 25 23:00:15 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A5A6F16A401; Thu, 25 Jan 2007 23:00:14 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5EF2213C471; Thu, 25 Jan 2007 23:00:14 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 767FE1A3C1C; Thu, 25 Jan 2007 15:00:13 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7CE9C5156B; Thu, 25 Jan 2007 18:00:08 -0500 (EST) Date: Thu, 25 Jan 2007 18:00:08 -0500 From: Kris Kennaway To: Peter Wemm Message-ID: <20070125230008.GA73226@xor.obsecurity.org> References: <200701252226.l0PMQfEb057961@repoman.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <200701252226.l0PMQfEb057961@repoman.freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: objformat (Re: cvs commit: src/usr.bin Makefile src/usr.bin/objformat Makefile objformat.1 objformat.c) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jan 2007 23:00:15 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 25, 2007 at 10:26:41PM +0000, Peter Wemm wrote: > peter 2007-01-25 22:26:41 UTC >=20 > FreeBSD src repository >=20 > Modified files: > usr.bin Makefile=20 > Removed files: > usr.bin/objformat Makefile objformat.1 objformat.c=20 > Log: > Retire objformat(1) as threatened in 2002. > =20 > Laughed-at-by: kris This was well past expiry date, as evidenced by the previous commit log to objformat.c: --- date: 2002/09/17 01:49:00; author: peter; state: Exp; lines: +3 -48 Initiate deorbit burn for the i386-only a.out related support. Moves are under way to move the remnants of the a.out toolchain to ports. As the comment in src/Makefile said, this stuff is deprecated and one should not expect this to remain beyond 4.0-REL. It has already lasted WAY beyond that. --- However it does catch us in ports with our pants down a bit: bsd.port.mk:PORTOBJFORMAT!=3D ${TEST} -x /usr/bin/objformat && /usr= /bin/objformat || ${ECHO_CMD} aout i.e. it defaults to aout :-O If you're in the habit of aggressively removing binaries from your system (i.e. you delete /usr/binobjformat) or you install 7.0 on a fresh system, you might need to add PORTOBJFORMAT?=3Delf in your /etc/make.conf until we can get it fixed in ports (workaround is easy, but digging out all the old a.out legacy crap will take more work, because it also extends into various patchfiles etc). Unfortunately this bogus form of the test seems to have also migrated upstream into various vendor packages (grep -r objformat /usr/src/{contrib,crypto} to see what I mean), so they may need to be fixed too. Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFuTZ3Wry0BWjoQKURAqfeAKCe0V/Oe5+fK8SDKSHxQF8EOLFZqgCeMbXm tHlhj0I68m/uti/ZZR3fuZM= =nPIH -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 03:15:55 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA34216A4EC for ; Fri, 26 Jan 2007 03:15:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 8B7EF13C4A3 for ; Fri, 26 Jan 2007 03:15:55 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0Q2OOCE034475 for ; Thu, 25 Jan 2007 19:24:26 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 25 Jan 2007 19:24:48 -0700 (MST) Message-Id: <20070125.192448.-432840241.imp@bsdimp.com> To: current@freebsd.org From: "M. Warner Losh" X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 25 Jan 2007 19:24:26 -0700 (MST) Cc: Subject: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 03:15:55 -0000 On a lark, I just got a combo USB/Firewire external disk drive. I ran some crude benchmarks, and I was surprised by what I found. This is on a fairly stock -current kernel. Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. This is with a simple dd command: When the enclosure was attached as firewire, I got these numbers: dd if=/dev/da0 of=/dev/null bs=1m count=1000 1048576000 bytes transferred in 25.867655 secs (40536183 bytes/sec) 1048576000 bytes transferred in 25.886887 secs (40506068 bytes/sec) 1048576000 bytes transferred in 25.880712 secs (40515733 bytes/sec) when it was attached via usb (same disk): dd if=/dev/da1 of=/dev/null bs=1m count=1000 1048576000 bytes transferred in 91.098764 secs (11510321 bytes/sec) and for comparison (apples to oranges, I know): dd if=/dev/ad0 of=/dev/null bs=1m count=1000 1048576000 bytes transferred in 32.173160 secs (32591639 bytes/sec) 1048576000 bytes transferred in 32.139310 secs (32625965 bytes/sec) 1048576000 bytes transferred in 32.114549 secs (32651120 bytes/sec) Summary: firewire 40.5 MB/s usb 11.5 MB/s ata 32.6 MB/s So why the huge difference? This is all the more amaizing because 400Mb/s is 50MB/s.[*] Warner P.S. This is on my amd64 laptop, which may be why ata didn't do so well. P.P.S: ad0: 114473MB at ata0-master UDMA100 firewire: da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 194481MB (398297088 512 byte sectors: 255H 63S/T 24792C) usb: da1: Fixed Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 194481MB (398297088 512 byte sectors: 255H 63S/T 24792C) P.P.P.S. M == 10^6 here. From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 03:26:42 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECDE016AA52 for ; Fri, 26 Jan 2007 03:26:42 +0000 (UTC) (envelope-from kevin.foo@zaidibrahim.com) Received: from tba.zaidibrahim.com (tba.zaidibrahim.com [202.75.165.180]) by mx1.freebsd.org (Postfix) with ESMTP id 117F913C491 for ; Fri, 26 Jan 2007 03:26:41 +0000 (UTC) (envelope-from kevin.foo@zaidibrahim.com) thread-index: AcdA9cC/OFoF7N+ySCKKXm9ccSNpKA== X-MessageTextProcessor: DisclaimIt (2.60.261) [Zaid Ibrahim & Co., Kuala Lumpur, Malaysia] Received: from mzimyklex02.zaidibrahim.com ([10.209.33.203]) by tba.zaidibrahim.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 10:57:44 +0800 Received: from b3ta.zaidibrahim.com ([10.209.46.120]) by mzimyklex02.zaidibrahim.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 Jan 2007 10:57:44 +0800 From: "Kevin Foo" Organization: Zaid Ibrahim & Co. To: Date: Fri, 26 Jan 2007 10:58:16 +0800 User-Agent: - References: <45B929D5.2040901@elischer.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Content-Class: urn:content-classes:message Importance: normal Priority: normal Message-ID: <200701261058.17261.kevin.foo@zaidibrahim.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2757 X-OriginalArrivalTime: 26 Jan 2007 02:57:44.0464 (UTC) FILETIME=[C087D100:01C740F5] Subject: Re: chinese use of FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 03:26:43 -0000 Sounds like a mimic of Debian GNU/kFreeBSD to me. http://www.debian.org/ports/kfreebsd-gnu/ http://english.chinamil.com.cn/site2/columns/2006-02/14/content_420257.ht= m --=20 Regards, Kevin Foo Key fingerprint : 4B23 FC1C E50B 9693 CCDD 2A7D A048 E909 8924 9BDD Public key : = http://keyserver.linux.it/pks/lookup?op=3Dget&search=3D0x89249BDD On Friday 26 January 2007 06:29, Andrew Pantyukhin wrote: > There was a presentation about this at EuroBSDCon. The > idea is sane (FreeBSD kernel + Linux userland + liters > of some glue), the only thing that got me suspicious > was the fact that some of the open-source software to > be produced will allegedly be only available in binary > form and for some money. I guess we were a bit lost in > translation, but that's how it sounded. >=20 > The developers want to give back some code, but this > is a government project and it felt like there was > going to be some difficulty... > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" >=20 *****************************Internet Email Confidentiality Footer = *****************************=20 Legal Privilege & Confidentiality=20 -------------------------------------------------------------------------= -------------------------------------------------------------------------= ------------- This email contains privileged and/or confidential information. If you = are not the intended recipient (or responsible for delivery of the = message to such person) or if you have inadvertently received this = email, you should destroy or delete this message and notify the sender = by reply email accordingly. If you or your employer do not consent to = using Internet email for messages of this kind please advise immediately = by sending an email to the sender of this message . All opinions, = conclusions and other information in this message that do not relate to = the official business of Zaid Ibrahim & Co shall be understood as = neither given nor endorsed by Zaid Ibrahim & Co. Our company accepts no = liability for the content of this email, or for the consequences of any = actions taken on the basis of the information provided, unless that = information is subsequently confirmed in writing. =20 Caveat=20 -------------------------------------------------------------------------= -------------------------------------------------------------------------= -----------WARNING: Computer viruses can be transmitted via email, and = you should check this email and any attachments for the presence of = viruses. Zaid Ibrahim & Co accepts no liability for any damage caused by = any virus transmitted by this email. Our employees are expressly = required not to make defamatory statements nor infringe or authorise any = infringement of copyright or any other legal right via any = communications. Any such communication is contrary to our company policy = and outside the scope of the employment of said individual. We will not = be liable for such communication.=20 From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 03:28:02 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12DE816AA47 for ; Fri, 26 Jan 2007 03:28:02 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id A663A13C481 for ; Fri, 26 Jan 2007 03:28:01 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id A7039EB72AB; Fri, 26 Jan 2007 11:28:00 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id BDH5BU11LPgz; Fri, 26 Jan 2007 11:27:53 +0800 (CST) Received: from [10.217.12.122] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id DDD61EB72A7; Fri, 26 Jan 2007 11:27:50 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:x-enigmail-version:content-type; b=oP8+kBi0/jpxm61crsgs06KxYTxU/RNxXASDwHG2Li9453NIBz243xp0qeXwpuq7w sG3pRSl7L5tMnuVoVnCPg== Message-ID: <45B97535.5070900@delphij.net> Date: Fri, 26 Jan 2007 11:27:49 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: freebsd-current@freebsd.org, marcel@FreeBSD.org X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigBF086E9AB316EE56D8E3E638" Cc: Subject: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 03:28:02 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBF086E9AB316EE56D8E3E638 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi, I got this with a freshly checked out -CURRENT code, when doing "make universe" at powerpc stage 4.2: mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-omit-frame-pointer -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=3Dgnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c *** Error code 2 Stop in /usr/src/gnu/lib/csu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. But I did not received any tinderbox breakage report I guess there is something wrong? This is a cross build environment running FreeBSD/amd64 7.0-CURRENT which is rebuilt 3 days ago. Thanks in advance! Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enigBF086E9AB316EE56D8E3E638 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFuXU1OfuToMruuMARA0f3AJ9OEoJubt7DS8rTyXkSkkaZDb6RzwCaA+iW x0SEZbNEMq+7d8c+AcGJ58I= =Hffw -----END PGP SIGNATURE----- --------------enigBF086E9AB316EE56D8E3E638-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 03:57:55 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C9B4216A400 for ; Fri, 26 Jan 2007 03:57:55 +0000 (UTC) (envelope-from akm@theinternet.com.au) Received: from fallbackmx01.syd.optusnet.com.au (fallbackmx01.syd.optusnet.com.au [211.29.132.93]) by mx1.freebsd.org (Postfix) with ESMTP id 6702B13C4AE for ; Fri, 26 Jan 2007 03:57:55 +0000 (UTC) (envelope-from akm@theinternet.com.au) Received: from mail32.syd.optusnet.com.au (mail32.syd.optusnet.com.au [211.29.132.63]) by fallbackmx01.syd.optusnet.com.au (8.12.11.20060308/8.12.11) with ESMTP id l0PGKvG4017817 for ; Fri, 26 Jan 2007 03:20:59 +1100 Received: from camelot.theinternet.com.au (c211-30-103-113.carlnfd1.nsw.optusnet.com.au [211.30.103.113]) by mail32.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l0PGKOEa024689; Fri, 26 Jan 2007 03:20:35 +1100 Received: by camelot.theinternet.com.au (Postfix, from userid 1000) id E811A6257; Fri, 26 Jan 2007 03:20:18 +1100 (EST) Date: Fri, 26 Jan 2007 03:20:18 +1100 From: Andrew Milton To: "M. Warner Losh" Message-ID: <20070125162018.GG683@camelot.theinternet.com.au> Mail-Followup-To: "M. Warner Losh" , freebsd-current@freebsd.org References: <20070125.091439.332275221.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070125.091439.332275221.imp@bsdimp.com> User-Agent: Mutt/1.5.9i Cc: freebsd-current@freebsd.org Subject: Re: sasyncd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 03:57:55 -0000 +-------[ M. Warner Losh ]---------------------- | In message: | "Alexey Karagodov" writes: | : is there any plans to port sasyncd from OpenBSD to FreeBSD ? | : or just please tell, how can i do it myself | | Copy the sources to a copy of the FreeBSD tree | (save a copy for later) | while (compile problems) { | type make | fix problems | } | while (runting problems) { | fix problems | type make | } runting? :-) Is that somewhere between running and runtime? -- Andrew Milton akm@theinternet.com.au From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 04:23:20 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECA4216A403 for ; Fri, 26 Jan 2007 04:23:20 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.173]) by mx1.freebsd.org (Postfix) with ESMTP id D796413C484 for ; Fri, 26 Jan 2007 04:23:18 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout03/MantshX 4.0) with ESMTP id l0Q49U3v023053; Thu, 25 Jan 2007 20:09:32 -0800 (PST) Received: from [192.168.1.2] (c-67-164-11-148.hsd1.ca.comcast.net [67.164.11.148]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id l0Q49Q79015955 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Jan 2007 20:09:28 -0800 (PST) In-Reply-To: <45B97535.5070900@delphij.net> References: <45B97535.5070900@delphij.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 25 Jan 2007 20:08:07 -0800 To: LI Xin X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: FreeBSD Current Subject: Re: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 04:23:21 -0000 On Jan 25, 2007, at 7:27 PM, LI Xin wrote: > mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR > -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config > -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. > -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools > /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c > cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR > -finhibit-size-directive -fno-inline-functions -fno-exceptions > -fno-zero-initialized-in-bss -fno-omit-frame-pointer > -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config > -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. > -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=gnu89 -g0 > -DCRT_BEGIN -c -o crtbegin.o > /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c > *** Error code 2 > But I did not received any tinderbox breakage report I guess there is > something wrong? This is a cross build environment running > FreeBSD/amd64 7.0-CURRENT which is rebuilt 3 days ago. I tried cross-builds before without problems. This was 2 or 3 months ago on a i386. I haven't tried it on a amd64 machine though. Other than that, I'm not aware of any problems as I just finished a native powerpc build with a fresh source tree. Was this a -jX build by any chance? -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 05:50:14 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F16A216A402; Fri, 26 Jan 2007 05:50:14 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id B4AB913C458; Fri, 26 Jan 2007 05:50:14 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0Q5lBun036007; Thu, 25 Jan 2007 22:47:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 25 Jan 2007 22:46:42 -0700 (MST) Message-Id: <20070125.224642.353412237.imp@bsdimp.com> To: cperciva@freebsd.org From: "M. Warner Losh" In-Reply-To: <45B9895B.9020709@freebsd.org> References: <20070125.192448.-432840241.imp@bsdimp.com> <45B9895B.9020709@freebsd.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 25 Jan 2007 22:47:11 -0700 (MST) Cc: current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 05:50:15 -0000 In message: <45B9895B.9020709@freebsd.org> Colin Percival writes: : M. Warner Losh wrote: : > On a lark, I just got a combo USB/Firewire external disk drive. I ran : > some crude benchmarks, and I was surprised by what I found. This is : > on a fairly stock -current kernel. : > : > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. : : Either amd64 is slower than i386, there has been a performance regression : between 6.2-RELEASE and whatever version of FreeBSD you're running, or you : have a rather slow external drive. I get 25MB/s from my Vantec Nexstar3 : USB 2.0 enclosure: : : http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html Still, 25MB/s is no 40MB/s... Warner From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 05:56:12 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D583E16A405 for ; Fri, 26 Jan 2007 05:56:12 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 80BD413C48C for ; Fri, 26 Jan 2007 05:56:12 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 90C80EB72F4; Fri, 26 Jan 2007 13:56:11 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id uk+-ipyGysyf; Fri, 26 Jan 2007 13:56:04 +0800 (CST) Received: from [10.217.12.122] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 0AADCEB72EE; Fri, 26 Jan 2007 13:56:04 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to:cc: subject:references:in-reply-to:x-enigmail-version:content-type; b=ct5MD01tw0rsk8/o/4/Edw0Xu9Ddq4KuvOgcN/CZapEGazL+PXEkSRvL1Huk7b9kC piTFXEV4APZcHC/+Xp4Wg== Message-ID: <45B997ED.7000605@delphij.net> Date: Fri, 26 Jan 2007 13:55:57 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Marcel Moolenaar References: <45B97535.5070900@delphij.net> In-Reply-To: X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig0219265EC30E30BB28BCA512" Cc: FreeBSD Current Subject: Re: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 05:56:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0219265EC30E30BB28BCA512 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Marcel Moolenaar wrote: >=20 > On Jan 25, 2007, at 7:27 PM, LI Xin wrote: >=20 >> mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR >> -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config >> -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. >> -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools >> /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c >> cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR >> -finhibit-size-directive -fno-inline-functions -fno-exceptions >> -fno-zero-initialized-in-bss -fno-omit-frame-pointer >> -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config= >> -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. >> -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=3Dgnu89 -g0 >> -DCRT_BEGIN -c -o crtbegin.o >> /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c >> *** Error code 2 >=20 >> But I did not received any tinderbox breakage report I guess there is >> something wrong? This is a cross build environment running >> FreeBSD/amd64 7.0-CURRENT which is rebuilt 3 days ago. >=20 > I tried cross-builds before without problems. This was > 2 or 3 months ago on a i386. I haven't tried it on a > amd64 machine though. Other than that, I'm not aware > of any problems as I just finished a native powerpc > build with a fresh source tree. >=20 > Was this a -jX build by any chance? Nope, I have removed -jX and cleaned the whole tree after I have realized there is a build issue, no luck :-( Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig0219265EC30E30BB28BCA512 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFuZftOfuToMruuMARA3I0AKCHsv5fvMlaoqQWy1J3CE2pnCwlBACfSXgJ bmTODgCHTfmn86u04eF6i7E= =dAuL -----END PGP SIGNATURE----- --------------enig0219265EC30E30BB28BCA512-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 05:56:36 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6146016A402 for ; Fri, 26 Jan 2007 05:56:36 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4051813C48A for ; Fri, 26 Jan 2007 05:56:36 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd2mr5so.prod.shaw.ca (pd2mr5so-qfe3.prod.shaw.ca [10.0.141.8]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JCG00GW4LM5MF80@l-daemon> for current@freebsd.org; Thu, 25 Jan 2007 21:54:05 -0700 (MST) Received: from pn2ml5so.prod.shaw.ca ([10.0.121.149]) by pd2mr5so.prod.shaw.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0JCG004CWLM5DAA2@pd2mr5so.prod.shaw.ca> for current@freebsd.org; Thu, 25 Jan 2007 21:54:05 -0700 (MST) Received: from hexahedron.daemonology.net ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0JCG00DAGLLY3JF2@l-daemon> for current@freebsd.org; Thu, 25 Jan 2007 21:53:59 -0700 (MST) Received: (qmail 5065 invoked from network); Fri, 26 Jan 2007 04:53:48 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Fri, 26 Jan 2007 04:53:48 +0000 Date: Thu, 25 Jan 2007 20:53:47 -0800 From: Colin Percival In-reply-to: <20070125.192448.-432840241.imp@bsdimp.com> To: "M. Warner Losh" Message-id: <45B9895B.9020709@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 References: <20070125.192448.-432840241.imp@bsdimp.com> User-Agent: Thunderbird 1.5.0.9 (X11/20061227) Cc: current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 05:56:36 -0000 M. Warner Losh wrote: > On a lark, I just got a combo USB/Firewire external disk drive. I ran > some crude benchmarks, and I was surprised by what I found. This is > on a fairly stock -current kernel. > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. Either amd64 is slower than i386, there has been a performance regression between 6.2-RELEASE and whatever version of FreeBSD you're running, or you have a rather slow external drive. I get 25MB/s from my Vantec Nexstar3 USB 2.0 enclosure: http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html Colin Percival From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 06:06:38 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88A4716A401 for ; Fri, 26 Jan 2007 06:06:38 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id 20D4213C46B for ; Fri, 26 Jan 2007 06:06:38 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd2mr7so.prod.shaw.ca (pd2mr7so-qfe3.prod.shaw.ca [10.0.141.10]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JCG00GWPOZ2MPA0@l-daemon> for current@freebsd.org; Thu, 25 Jan 2007 23:06:38 -0700 (MST) Received: from pn2ml8so.prod.shaw.ca ([10.0.121.152]) by pd2mr7so.prod.shaw.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0JCG00HZXOZ2BTX1@pd2mr7so.prod.shaw.ca> for current@freebsd.org; Thu, 25 Jan 2007 23:06:38 -0700 (MST) Received: from hexahedron.daemonology.net ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0JCG005G8OYSBHK0@l-daemon> for current@freebsd.org; Thu, 25 Jan 2007 23:06:34 -0700 (MST) Received: (qmail 5371 invoked from network); Fri, 26 Jan 2007 06:06:17 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Fri, 26 Jan 2007 06:06:17 +0000 Date: Thu, 25 Jan 2007 22:06:17 -0800 From: Colin Percival In-reply-to: <20070125.224642.353412237.imp@bsdimp.com> To: "M. Warner Losh" Message-id: <45B99A59.6070902@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 References: <20070125.192448.-432840241.imp@bsdimp.com> <45B9895B.9020709@freebsd.org> <20070125.224642.353412237.imp@bsdimp.com> User-Agent: Thunderbird 1.5.0.9 (X11/20061227) Cc: current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 06:06:38 -0000 M. Warner Losh wrote: > In message: <45B9895B.9020709@freebsd.org> > Colin Percival writes: > : M. Warner Losh wrote: > : > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > : > : I get 25MB/s from my Vantec Nexstar3 > : USB 2.0 enclosure: > : > : http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html > > Still, 25MB/s is no 40MB/s... Sure, but it means that the performance issues aren't simply a global "USB 2.0 is bad". What does `diskinfo -c` say about your firewire and USB interfaces? Colin Percival From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 06:12:57 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27BD016A400 for ; Fri, 26 Jan 2007 06:12:57 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id C6E6813C458 for ; Fri, 26 Jan 2007 06:12:56 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id l0Q6ClRg044614; Thu, 25 Jan 2007 23:12:52 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <45B99BD6.3000709@samsco.org> Date: Thu, 25 Jan 2007 23:12:38 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: "M. Warner Losh" References: <20070125.192448.-432840241.imp@bsdimp.com> In-Reply-To: <20070125.192448.-432840241.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Thu, 25 Jan 2007 23:12:52 -0700 (MST) X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 06:12:57 -0000 M. Warner Losh wrote: > On a lark, I just got a combo USB/Firewire external disk drive. I ran > some crude benchmarks, and I was surprised by what I found. This is > on a fairly stock -current kernel. > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > This is with a simple dd command: > > When the enclosure was attached as firewire, I got these numbers: > > dd if=/dev/da0 of=/dev/null bs=1m count=1000 > 1048576000 bytes transferred in 25.867655 secs (40536183 bytes/sec) > 1048576000 bytes transferred in 25.886887 secs (40506068 bytes/sec) > 1048576000 bytes transferred in 25.880712 secs (40515733 bytes/sec) > > when it was attached via usb (same disk): > dd if=/dev/da1 of=/dev/null bs=1m count=1000 > 1048576000 bytes transferred in 91.098764 secs (11510321 bytes/sec) > > > and for comparison (apples to oranges, I know): > > dd if=/dev/ad0 of=/dev/null bs=1m count=1000 > 1048576000 bytes transferred in 32.173160 secs (32591639 bytes/sec) > 1048576000 bytes transferred in 32.139310 secs (32625965 bytes/sec) > 1048576000 bytes transferred in 32.114549 secs (32651120 bytes/sec) > > Summary: > > firewire 40.5 MB/s Pretty much the speed I would expect. Yeah, it's not 50MB/s, but the firewire stack is under Giant so it's adding latency that is probably not optimal for getting the disk to cluster the reads. > usb 11.5 MB/s umass still bounces all I/O through a local buffer, right? That'll add a lot of latency, on top of the Giant-induced latency. > ata 32.6 MB/s Laptop drives are notoriously slow. This is a 4200RPM drive, while your firewire and USB drives are probably 5400 or 7200 RPM. It's also 2.5", so it has a smaller average linear velocity under the heads than a 3.5" drive. > > So why the huge difference? This is all the more amaizing because > 400Mb/s is 50MB/s.[*] > > Warner > > P.S. This is on my amd64 laptop, which may be why ata didn't do so > well. amd64 will only give a penalty to ATA if you have more than 4GB of RAM. Scott From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 06:15:34 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1291D16A401 for ; Fri, 26 Jan 2007 06:15:34 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 32A5713C4B0 for ; Fri, 26 Jan 2007 06:15:32 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id D223CEB72F7; Fri, 26 Jan 2007 14:15:28 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id QNL7aGz4ueoS; Fri, 26 Jan 2007 14:15:14 +0800 (CST) Received: from [10.217.12.122] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 5C860EB2723; Fri, 26 Jan 2007 14:15:13 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to:cc: subject:references:in-reply-to:x-enigmail-version:content-type; b=AY+WG5WwafzMa1hzANkmS6QK1eLcgMpeP8j/s6B8ilalLo+QabYM6HFyPqi1Uv2nz eyaKpBDn/iXIW3OmeslZg== Message-ID: <45B99C6E.2030803@delphij.net> Date: Fri, 26 Jan 2007 14:15:10 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: LI Xin References: <45B97535.5070900@delphij.net> <45B997ED.7000605@delphij.net> In-Reply-To: <45B997ED.7000605@delphij.net> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig995953CB395FAE671B12DAED" Cc: Marcel Moolenaar , FreeBSD Current Subject: Re: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 06:15:34 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig995953CB395FAE671B12DAED Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Latest build shows this: (What does Assembler messages: FATAL: can't create crtbegin.o: Invalid bfd target mean for me, by the way?) -------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=3D/usr/obj/powerpc MACHINE_ARCH=3Dpowerpc= MACHINE=3Dpowerpc CPUTYPE=3D GROFF_BIN_PATH=3D/usr/obj/powerpc/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=3D/usr/obj/powerpc/usr/src/tmp/legacy/usr/share/groff_fon= t GROFF_TMAC_PATH=3D/usr/obj/powerpc/usr/src/tmp/legacy/usr/share/tmac _SHLIBDIRPREFIX=3D/usr/obj/powerpc/usr/src/tmp INSTALL=3D"sh /usr/src/tools/install.sh" PATH=3D/usr/obj/powerpc/usr/src/tmp/legacy/usr/sbin:/usr/obj/powerpc/usr/= src/tmp/legacy/usr/bin:/usr/obj/powerpc/usr/src/tmp/legacy/usr/games:/usr= /obj/powerpc/usr/src/tmp/usr/sbin:/usr/obj/powerpc/usr/src/tmp/usr/bin:/u= sr/obj/powerpc/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin make -f Makefile.inc1 DESTDIR=3D/usr/obj/powerpc/usr/src/tmp -DNO_FSCHG -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DWITHOUT_NLS -DWITHOUT_PROFILE libraries cd /usr/src; make -f Makefile.inc1 _startup_libs; make -f Makefile.inc1 _prebuild_libs; make -f Makefile.inc1 _generic_libs; =3D=3D=3D> gnu/lib/csu (obj,depend,all,install) make -f /usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=3D/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=3D/usr/src/gnu/lib/csu/../../../contrib/gcc tconfig.h echo '#ifndef GCC_TCONFIG_H' > tconfig.h echo '#define GCC_TCONFIG_H' >> tconfig.h echo '#ifdef IN_GCC' >> tconfig.h echo '# include "ansidecl.h"' >> tconfig.h echo '#endif' >> tconfig.h echo '#define USED_FOR_TARGET' >> tconfig.h echo '#endif /* GCC_TCONFIG_H */' >> tconfig.h make -f /usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=3D/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=3D/usr/src/gnu/lib/csu/../../../contrib/gcc tm.h echo '#ifndef GCC_TM_H' > tm.h echo '#define GCC_TM_H' >> tm.h echo '#ifdef IN_GCC' >> tm.h echo '#include "rs6000/rs6000.h"' >> tm.h echo '#include "dbxelf.h"' >> tm.h echo '#include "elfos.h"' >> tm.h echo '#include "freebsd-native.h"' >> tm.h echo '#include "freebsd-spec.h"' >> tm.h echo '#include "freebsd.h"' >> tm.h echo '#include "rs6000/sysv4.h"' >> tm.h echo '#include "rs6000/freebsd.h"' >> tm.h echo '#include "defaults.h"' >> tm.h echo '#if !defined GENERATOR_FILE && !defined USED_FOR_TARGET' >> tm.h echo '# include "insn-constants.h"' >> tm.h echo '# include "insn-flags.h"' >> tm.h echo '#endif' >> tm.h echo '#endif' >> tm.h echo '#define EXTRA_MODES_FILE "rs6000/rs6000-modes.def"' >> tm.h echo '#endif /* GCC_TM_H */' >> tm.h rm -f .depend mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-omit-frame-pointer -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=3Dgnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c Assembler messages: FATAL: can't create crtbegin.o: Invalid bfd target In file included from ./tm.h:10, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/rs6000/sysv4.h:24:1: warning: "NO_IMPLICIT_EXTERN_C" redefined In file included from ./tm.h:9, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/freebsd.h:69:1: warning: this is the location of the previous definition In file included from ./tm.h:10, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/rs6000/sysv4.h:1349:1: warning: "HANDLE_PRAGMA_PACK_PUSH_POP" redefined In file included from ./tm.h:9, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/freebsd.h:99:1: warning: this is the location of the previous definition *** Error code 2 Stop in /usr/src/gnu/lib/csu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [1] Exit 1 make buildworld TARGET=3Dpowerpc __MAKE_CONF=3D/dev/null > _.powerpc.buildworld Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig995953CB395FAE671B12DAED Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFuZxuOfuToMruuMARA8gMAJ9DwK4RoCD7fZnX47Vg30tat94gTwCfSK6Y Q3LZjlgsu/uRaeY2F5hmAAo= =lc5Z -----END PGP SIGNATURE----- --------------enig995953CB395FAE671B12DAED-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 06:29:43 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C83916A402 for ; Fri, 26 Jan 2007 06:29:43 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.175]) by mx1.freebsd.org (Postfix) with ESMTP id 87F3813C484 for ; Fri, 26 Jan 2007 06:29:43 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin04-en2 [10.13.10.149]) by smtpout.mac.com (Xserve/8.12.11/smtpout05/MantshX 4.0) with ESMTP id l0Q6TYQI003327; Thu, 25 Jan 2007 22:29:34 -0800 (PST) Received: from [172.23.10.62] (nat-service4.juniper.net [66.129.225.151]) (authenticated bits=0) by mac.com (Xserve/smtpin04/MantshX 4.0) with ESMTP id l0Q6TSD7009190 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Jan 2007 22:29:29 -0800 (PST) In-Reply-To: <45B99C6E.2030803@delphij.net> References: <45B97535.5070900@delphij.net> <45B997ED.7000605@delphij.net> <45B99C6E.2030803@delphij.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1C63ACE4-DD1E-4FDB-A36B-F3D9650773EF@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Thu, 25 Jan 2007 22:28:08 -0800 To: LI Xin X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: FreeBSD Current Subject: Re: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 06:29:43 -0000 On Jan 25, 2007, at 10:15 PM, LI Xin wrote: > Latest build shows this: > > (What does Assembler messages: > FATAL: can't create crtbegin.o: Invalid bfd target > mean for me, by the way?) This probably means that the wrong compiler driver or assembler is being picked up. One that doesn't isn't targeting powerpc. I'll fire-up a cross-build on my amd64 and get back to you... > Stop in /usr/src. > > [1] Exit 1 make buildworld TARGET=powerpc > __MAKE_CONF=/dev/null > _.powerpc.buildworld What happens if you set TARGET_ARCH instead of TARGET? -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 06:43:22 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F0E216A407 for ; Fri, 26 Jan 2007 06:43:22 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id C1FE513C4A3 for ; Fri, 26 Jan 2007 06:43:21 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so598742uge for ; Thu, 25 Jan 2007 22:43:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=k8VlOVGzv0Hp8rlLXx7XLY9k9OjAzaDq+ro7jklJSIj+XUq6DcPAAoKck+QaSyoqbDwV8R5ys/+NW0B+WdxTcBwcZYKDaRyvIJyDd88DB19JBYZsIpIcJnUCd2zPs2MmFd6QMKHjvUhMXLpyZEgsCY1Tc9njUKvND5HwXG75Bm4= Received: by 10.78.136.9 with SMTP id j9mr2082887hud.1169793800065; Thu, 25 Jan 2007 22:43:20 -0800 (PST) Received: by 10.78.164.20 with HTTP; Thu, 25 Jan 2007 22:43:20 -0800 (PST) Message-ID: Date: Fri, 26 Jan 2007 09:43:20 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "Colin Percival" In-Reply-To: <45B9895B.9020709@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070125.192448.-432840241.imp@bsdimp.com> <45B9895B.9020709@freebsd.org> X-Google-Sender-Auth: e568a4c7696c5c0d Cc: current@freebsd.org, "M. Warner Losh" Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 06:43:22 -0000 On 1/26/07, Colin Percival wrote: > M. Warner Losh wrote: > > On a lark, I just got a combo USB/Firewire external disk drive. I ran > > some crude benchmarks, and I was surprised by what I found. This is > > on a fairly stock -current kernel. > > > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > > Either amd64 is slower than i386, there has been a performance regression > between 6.2-RELEASE and whatever version of FreeBSD you're running, or you > have a rather slow external drive. I get 25MB/s from my Vantec Nexstar3 > USB 2.0 enclosure: > > http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html I've always (since 5.x I think) got 25Mb/s on i386 and half that on amd64, no matter what equipment I try. From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 07:07:40 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2757716A400; Fri, 26 Jan 2007 07:07:40 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 422DC13C494; Fri, 26 Jan 2007 07:07:38 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe07.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 395484261; Fri, 26 Jan 2007 08:07:33 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 08:07:09 +0100 User-Agent: KMail/1.9.5 References: <20070125.192448.-432840241.imp@bsdimp.com> <45B9895B.9020709@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701260807.09055.hselasky@c2i.net> Cc: "M. Warner Losh" , current@freebsd.org, Colin Percival Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 07:07:40 -0000 On Friday 26 January 2007 07:43, Andrew Pantyukhin wrote: > On 1/26/07, Colin Percival wrote: > > M. Warner Losh wrote: > > > On a lark, I just got a combo USB/Firewire external disk drive. I ran > > > some crude benchmarks, and I was surprised by what I found. This is > > > on a fairly stock -current kernel. > > > > > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > > > > Either amd64 is slower than i386, there has been a performance regression > > between 6.2-RELEASE and whatever version of FreeBSD you're running, or > > you have a rather slow external drive. I get 25MB/s from my Vantec > > Nexstar3 USB 2.0 enclosure: > > > > http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html > > I've always (since 5.x I think) got 25Mb/s on i386 > and half that on amd64, no matter what equipment I > try. 1) Maybe this has something to do with the interrupt threshold. Does changing: EHCI_CMD_ITC_2 into EHCI_CMD_ITC_1 increase performance, in "ehci.c" ? 2) You could try setting the transfer multiplier, "EHCI_QH_SET_MULT()" to 3 for HIGH-speed bulk/control transfers, but not interrupt transfers. The EHCI manual states that the USB host controller can choose to ignore this field, but what if it doesn't? 3) How about the new USB stack? Any difference? --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 07:13:20 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BC7E116A400 for ; Fri, 26 Jan 2007 07:13:20 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 8968E13C483 for ; Fri, 26 Jan 2007 07:13:19 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 9CD0BEB7320; Fri, 26 Jan 2007 15:13:15 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id B2E8AvGR74pS; Fri, 26 Jan 2007 15:13:11 +0800 (CST) Received: from [10.217.12.122] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 6FA9EEB1FFF; Fri, 26 Jan 2007 15:13:10 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to:cc: subject:references:in-reply-to:x-enigmail-version:content-type; b=XCnqOxGRfslUJQxR5v/qH2TTkQF8NUerTmyJCMLggGl1dRCPJWCf/IaNVYoI89+1h IfRymVePqU8OJf2kdBwsg== Message-ID: <45B9AA00.3030906@delphij.net> Date: Fri, 26 Jan 2007 15:13:04 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Marcel Moolenaar References: <45B97535.5070900@delphij.net> <45B997ED.7000605@delphij.net> <45B99C6E.2030803@delphij.net> <1C63ACE4-DD1E-4FDB-A36B-F3D9650773EF@mac.com> In-Reply-To: <1C63ACE4-DD1E-4FDB-A36B-F3D9650773EF@mac.com> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigAB71B9972A64F6172AB8F714" Cc: FreeBSD Current Subject: Re: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 07:13:20 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigAB71B9972A64F6172AB8F714 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Marcel Moolenaar wrote: >=20 > On Jan 25, 2007, at 10:15 PM, LI Xin wrote: >=20 >> Latest build shows this: >> >> (What does Assembler messages: >> FATAL: can't create crtbegin.o: Invalid bfd target >> mean for me, by the way?) >=20 > This probably means that the wrong compiler driver or > assembler is being picked up. One that doesn't isn't > targeting powerpc. >=20 > I'll fire-up a cross-build on my amd64 and get back > to you... >=20 >> Stop in /usr/src. >> >> [1] Exit 1 make buildworld TARGET=3Dpowerpc >> __MAKE_CONF=3D/dev/null > _.powerpc.buildworld >=20 > What happens if you set TARGET_ARCH instead of TARGET? Still same problem... Do we have a public reference PowerPC box for committers to test changes? This is the only platform I have not tested my gzip related changes :-) mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-zero-initialized-in-bss -fno-omit-frame-pointer -fno-unit-at-a-time -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -std=3Dgnu89 -g0 -DCRT_BEGIN -c -o crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c Assembler messages: FATAL: can't create crtbegin.o: Invalid bfd target In file included from ./tm.h:10, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/rs6000/sysv4.h:24:1: warning: "NO_IMPLICIT_EXTERN_C" redefined In file included from ./tm.h:9, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/freebsd.h:69:1: warning: this is the location of the previous definition In file included from ./tm.h:10, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/rs6000/sysv4.h:1349:1: warning: "HANDLE_PRAGMA_PACK_PUSH_POP" redefined In file included from ./tm.h:9, from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:64: /usr/src/gnu/lib/csu/../../../contrib/gcc/config/freebsd.h:99:1: warning: this is the location of the previous definition *** Error code 2 Stop in /usr/src/gnu/lib/csu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. [1] Exit 1 make buildworld TARGET_ARCH=3Dpowerp= c __MAKE_CONF=3D/dev/null > ... Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enigAB71B9972A64F6172AB8F714 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFuaoAOfuToMruuMARA6jFAJwKeazFTGasBI3Jw16B0Qtka/qP3ACgh7Al JP2Jacu9GO0OMpINtNbshoE= =S7Rc -----END PGP SIGNATURE----- --------------enigAB71B9972A64F6172AB8F714-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 08:07:41 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9B09316A404; Fri, 26 Jan 2007 08:07:41 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 6C0DD13C48A; Fri, 26 Jan 2007 08:07:40 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe07.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 395484261; Fri, 26 Jan 2007 08:07:33 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 08:07:09 +0100 User-Agent: KMail/1.9.5 References: <20070125.192448.-432840241.imp@bsdimp.com> <45B9895B.9020709@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701260807.09055.hselasky@c2i.net> Cc: "M. Warner Losh" , current@freebsd.org, Colin Percival Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 08:07:41 -0000 On Friday 26 January 2007 07:43, Andrew Pantyukhin wrote: > On 1/26/07, Colin Percival wrote: > > M. Warner Losh wrote: > > > On a lark, I just got a combo USB/Firewire external disk drive. I ran > > > some crude benchmarks, and I was surprised by what I found. This is > > > on a fairly stock -current kernel. > > > > > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > > > > Either amd64 is slower than i386, there has been a performance regression > > between 6.2-RELEASE and whatever version of FreeBSD you're running, or > > you have a rather slow external drive. I get 25MB/s from my Vantec > > Nexstar3 USB 2.0 enclosure: > > > > http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html > > I've always (since 5.x I think) got 25Mb/s on i386 > and half that on amd64, no matter what equipment I > try. 1) Maybe this has something to do with the interrupt threshold. Does changing: EHCI_CMD_ITC_2 into EHCI_CMD_ITC_1 increase performance, in "ehci.c" ? 2) You could try setting the transfer multiplier, "EHCI_QH_SET_MULT()" to 3 for HIGH-speed bulk/control transfers, but not interrupt transfers. The EHCI manual states that the USB host controller can choose to ignore this field, but what if it doesn't? 3) How about the new USB stack? Any difference? --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 09:52:15 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9508916A405 for ; Fri, 26 Jan 2007 09:52:15 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id E600513C483 for ; Fri, 26 Jan 2007 09:52:14 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 26 Jan 2007 09:52:13 -0000 Received: from h081217095052.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.95.52] by mail.gmx.net (mp038) with SMTP; 26 Jan 2007 10:52:13 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 10:52:11 +0100 User-Agent: KMail/1.9.5 References: <20070125.192448.-432840241.imp@bsdimp.com> In-Reply-To: <20070125.192448.-432840241.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701261052.12435.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: "M. Warner Losh" Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 09:52:15 -0000 On Friday 26 January 2007 03:24, M. Warner Losh wrote: > On a lark, I just got a combo USB/Firewire external disk drive. I ran > some crude benchmarks, and I was surprised by what I found. This is > on a fairly stock -current kernel. > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > This is with a simple dd command: On my i386 notebook with USB 2.0 enclosure. Linux: 31.5MB/s FreeBSD: 27.5MB/s There's still room for improvement but numbers don't seem that bad. Maybe you should try knoppix or so to verify it's not the drive's fault. Other than that I'd also guess it's an amd64 problem. Stefan From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 10:00:42 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6690216A401 for ; Fri, 26 Jan 2007 10:00:42 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id CEE4C13C4A8 for ; Fri, 26 Jan 2007 10:00:41 +0000 (UTC) (envelope-from karagodov@gmail.com) Received: by nf-out-0910.google.com with SMTP id m19so1070028nfc for ; Fri, 26 Jan 2007 02:00:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=K25SqMC+unyut9j+8oj6P1xEx0oRU+7tq6zP4MATNnomjOFGRIxh+Otyu5dhPeQjiJRFhm99loKSTH0rDN4+ElslvehPjekOlbntetvSEGZF0BcSMYbb/ral9N8wfI1CeukxyIyGGR5Qd2XIne5P4nfT4vS4HMunwiQMswFe0dE= Received: by 10.82.183.19 with SMTP id g19mr1717989buf.1169805640276; Fri, 26 Jan 2007 02:00:40 -0800 (PST) Received: by 10.82.106.13 with HTTP; Fri, 26 Jan 2007 02:00:40 -0800 (PST) Message-ID: Date: Fri, 26 Jan 2007 13:00:40 +0300 From: "Alexey Karagodov" To: freebsd-current@freebsd.org In-Reply-To: <200701261052.12435.shoesoft@gmx.net> MIME-Version: 1.0 References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261052.12435.shoesoft@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 10:00:42 -0000 what manufacturer says about usb speeds? that is the question 2007/1/26, Stefan Ehmann : > > On Friday 26 January 2007 03:24, M. Warner Losh wrote: > > On a lark, I just got a combo USB/Firewire external disk drive. I ran > > some crude benchmarks, and I was surprised by what I found. This is > > on a fairly stock -current kernel. > > > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > > This is with a simple dd command: > > On my i386 notebook with USB 2.0 enclosure. > Linux: 31.5MB/s > FreeBSD: 27.5MB/s > > There's still room for improvement but numbers don't seem that bad. > > Maybe you should try knoppix or so to verify it's not the drive's fault. > Other > than that I'd also guess it's an amd64 problem. > > Stefan > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 10:02:31 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3464116A485 for ; Fri, 26 Jan 2007 10:02:31 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id C406F13C481 for ; Fri, 26 Jan 2007 10:02:30 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so622844uge for ; Fri, 26 Jan 2007 02:02:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ghjqKdqBCKc7/bfAKpmJKVrEQyl/W7UjjIHUr+C+0HoerbTIyXgSTGEI8KVWh0OePNYzMG+pVruLAqvA5YUIIvKiyXTbWI9ZRbmK7ucw59ksMljdR3ZxBg5nKKTxG+L8Jvt4fAVl20DcTXt7IUuFDWoyQvlMX3lvcAXuTVrJbeg= Received: by 10.78.158.11 with SMTP id g11mr2115458hue.1169805749090; Fri, 26 Jan 2007 02:02:29 -0800 (PST) Received: by 10.78.164.20 with HTTP; Fri, 26 Jan 2007 02:02:29 -0800 (PST) Message-ID: Date: Fri, 26 Jan 2007 13:02:29 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "Stefan Ehmann" In-Reply-To: <200701261052.12435.shoesoft@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261052.12435.shoesoft@gmx.net> X-Google-Sender-Auth: 6a012c4dd5f6cc5a Cc: freebsd-current@freebsd.org, "M. Warner Losh" Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 10:02:31 -0000 On 1/26/07, Stefan Ehmann wrote: > On Friday 26 January 2007 03:24, M. Warner Losh wrote: > > On a lark, I just got a combo USB/Firewire external disk drive. I ran > > some crude benchmarks, and I was surprised by what I found. This is > > on a fairly stock -current kernel. > > > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > > This is with a simple dd command: > > On my i386 notebook with USB 2.0 enclosure. > Linux: 31.5MB/s > FreeBSD: 27.5MB/s > > There's still room for improvement but numbers don't seem that bad. > > Maybe you should try knoppix or so to verify it's not the drive's fault. Other > than that I'd also guess it's an amd64 problem. IIRC I got around 50Mb/s with most USB2.0 enclosures (and drives capable of sustaining the speed) under Windows. From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 10:04:08 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B31916A406 for ; Fri, 26 Jan 2007 10:04:08 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id A8F3B13C4AD for ; Fri, 26 Jan 2007 10:04:07 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id ACEA6EB7367 for ; Fri, 26 Jan 2007 18:04:05 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id 2aMHCCBWz21n for ; Fri, 26 Jan 2007 18:03:54 +0800 (CST) Received: from [10.217.12.122] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 7576EEB7325 for ; Fri, 26 Jan 2007 18:03:54 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to: subject:x-enigmail-version:content-type; b=Vmojh+Iq/Vdm9u8pSv6R+QwRvw5+Lb0arnhRBLzsHkGP5ZxURNB3e5pOfxsSyDgTt p7MmSkNDw5WO6ZvkbOzGg== Message-ID: <45B9D204.9030503@delphij.net> Date: Fri, 26 Jan 2007 18:03:48 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: FreeBSD Current X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig92C3591130A09322CD10F44F" Subject: HEADSUP: Replacing GNU gzip(1) implementation with a BSD licensed version X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 10:04:08 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig92C3591130A09322CD10F44F Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Dear folks, A BSD licensed gzip version has been ported from NetBSD, in order to replace the current GNU GPL'ed gzip version found in our base system. The new gzip would be added to src/usr.bin. It is expected to hit the tree soon. Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig92C3591130A09322CD10F44F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFudIEOfuToMruuMARA20MAJ40QxBckMM5Mpevt52t/vzHhrzbPACdGYoV +65o7FbZx4/uqb+uOAcjphI= =3gWs -----END PGP SIGNATURE----- --------------enig92C3591130A09322CD10F44F-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 10:33:20 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 929AF16A403 for ; Fri, 26 Jan 2007 10:33:20 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 4F4BC13C481 for ; Fri, 26 Jan 2007 10:33:18 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A5FB52.dip.t-dialin.net [84.165.251.82]) by redbull.bpaserver.net (Postfix) with ESMTP id 281E82E149; Fri, 26 Jan 2007 11:43:14 +0100 (CET) Received: from webmail.leidinger.net (webmail.Leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id D85FF5B4873; Fri, 26 Jan 2007 11:33:11 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.13.8/8.13.8/Submit) id l0QAXB8N020709; Fri, 26 Jan 2007 11:33:11 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from psbru.cec.eu.int (psbru.cec.eu.int [158.169.131.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Fri, 26 Jan 2007 11:33:11 +0100 Message-ID: <20070126113311.tuvrh2azr48ckoc8@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Fri, 26 Jan 2007 11:33:11 +0100 From: Alexander Leidinger To: "M. Warner Losh" References: <20070125.192448.-432840241.imp@bsdimp.com> In-Reply-To: <20070125.192448.-432840241.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.3) / FreeBSD-7.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.864, required 6, autolearn=not spam, BAYES_00 -15.00, DK_POLICY_SIGNSOME 0.00, FORGED_RCVD_HELO 0.14) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No Cc: current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 10:33:20 -0000 Quoting "M. Warner Losh" (from Thu, 25 Jan 2007 19:24:48 -0700 (MST)): > Summary: > > firewire 40.5 MB/s > usb 11.5 MB/s > ata 32.6 MB/s Instead of comparing it with a different drive on ata, you could give atausb a try (and maybe do all of the tests on i386 to check for differences to amd64). Bye, Alexander. -- Corruption is not the No. 1 priority of the Police Commissioner. His job is to enforce the law and fight crime. -- P.B.A. President E. J. Kiernan http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 10:58:35 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D64E416A400 for ; Fri, 26 Jan 2007 10:58:35 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mx1.freebsd.org (Postfix) with ESMTP id 576ED13C48D for ; Fri, 26 Jan 2007 10:58:35 +0000 (UTC) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.8/8.13.7) with ESMTP id l0QAwMV8073034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Jan 2007 11:58:22 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.8/8.13.3/Submit) id l0QAwMct073033; Fri, 26 Jan 2007 11:58:22 +0100 (CET) Date: Fri, 26 Jan 2007 11:58:22 +0100 From: Divacky Roman To: LI Xin Message-ID: <20070126105822.GA72945@stud.fit.vutbr.cz> References: <45B9D204.9030503@delphij.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45B9D204.9030503@delphij.net> User-Agent: Mutt/1.4.2.2i X-Scanned-By: MIMEDefang 2.57 on 147.229.176.14 Cc: FreeBSD Current Subject: Re: HEADSUP: Replacing GNU gzip(1) implementation with a BSD licensed version X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 10:58:35 -0000 On Fri, Jan 26, 2007 at 06:03:48PM +0800, LI Xin wrote: > Dear folks, > > A BSD licensed gzip version has been ported from NetBSD, in order to > replace the current GNU GPL'ed gzip version found in our base system. > > The new gzip would be added to src/usr.bin. It is expected to hit the > tree soon. how does performance compare between the bsdzip and gzip? From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 11:08:33 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4635316A402 for ; Fri, 26 Jan 2007 11:08:33 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id D625C13C4A3 for ; Fri, 26 Jan 2007 11:08:32 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so633964uge for ; Fri, 26 Jan 2007 03:08:31 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=fXXzT0yzMKso4YnsJc0WjY7wv22F4745r7bZx59Ez+TzPXbFumqsPsTqg5xfe528SWisFT29HTNwVosuZ44W5pnNiNCRQExmkwuJALgqjXqbXk6q4Nods4amMMuDWn51/D1h2RHLSyvtJoits9wJBdPySk7tQ9GNNy1rqNiZM4Y= Received: by 10.78.146.11 with SMTP id t11mr816621hud.1169809709482; Fri, 26 Jan 2007 03:08:29 -0800 (PST) Received: by 10.78.164.20 with HTTP; Fri, 26 Jan 2007 03:08:29 -0800 (PST) Message-ID: Date: Fri, 26 Jan 2007 14:08:29 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "Alexander Leidinger" In-Reply-To: <20070126113311.tuvrh2azr48ckoc8@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070125.192448.-432840241.imp@bsdimp.com> <20070126113311.tuvrh2azr48ckoc8@webmail.leidinger.net> X-Google-Sender-Auth: 8fdce469cfa1f576 Cc: current@freebsd.org, "M. Warner Losh" Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 11:08:33 -0000 On 1/26/07, Alexander Leidinger wrote: > Quoting "M. Warner Losh" (from Thu, 25 Jan 2007 > 19:24:48 -0700 (MST)): > > > Summary: > > > > firewire 40.5 MB/s > > usb 11.5 MB/s > > ata 32.6 MB/s > > Instead of comparing it with a different drive on ata, you could give > atausb a try (and maybe do all of the tests on i386 to check for > differences to amd64). I gave atausb a try with no perceptible changes both on i386 and amd64. From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 12:32:57 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4327F16A403 for ; Fri, 26 Jan 2007 12:32:57 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 93B2B13C484 for ; Fri, 26 Jan 2007 12:32:56 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 26 Jan 2007 12:32:55 -0000 Received: from h081217095052.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.95.52] by mail.gmx.net (mp050) with SMTP; 26 Jan 2007 13:32:55 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 13:32:53 +0100 User-Agent: KMail/1.9.5 References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261052.12435.shoesoft@gmx.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701261332.54375.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: Alexey Karagodov Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 12:32:57 -0000 On Friday 26 January 2007 11:00, Alexey Karagodov wrote: > what manufacturer says about usb speeds? > that is the question Well, "up to 56MB/s" which is pretty much full USB2 speed. But writing it on the box doesn't mean the speed can actually be reached. Benchmarking on windows might be interesting, but I don't know how to measure raw disk io on windows. Stefan From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 12:35:18 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ECD4016A401 for ; Fri, 26 Jan 2007 12:35:18 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.224]) by mx1.freebsd.org (Postfix) with ESMTP id B1F8C13C4BB for ; Fri, 26 Jan 2007 12:35:14 +0000 (UTC) (envelope-from infofarmer@gmail.com) Received: by wr-out-0506.google.com with SMTP id 68so609454wri for ; Fri, 26 Jan 2007 04:35:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=hDk6GtC5FPWiSbE+D5U5so/7YSMoIJU4SXf7A2zOgF8ue8sRHLL9x4YcRwIj01lRwLBOXwbXIX+J4BJzkcQYBDV+cwb9iLA1unZJmc9zRS6PETtY+qQaUwQEF5eG/QV2modEso4fkl9724YwHX9exISCbC+Xx7ABn2LXQELxJjQ= Received: by 10.78.170.6 with SMTP id s6mr2164015hue.1169814913240; Fri, 26 Jan 2007 04:35:13 -0800 (PST) Received: by 10.78.164.20 with HTTP; Fri, 26 Jan 2007 04:35:13 -0800 (PST) Message-ID: Date: Fri, 26 Jan 2007 15:35:13 +0300 From: "Andrew Pantyukhin" Sender: infofarmer@gmail.com To: "Stefan Ehmann" In-Reply-To: <200701261332.54375.shoesoft@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261052.12435.shoesoft@gmx.net> <200701261332.54375.shoesoft@gmx.net> X-Google-Sender-Auth: ae76e6480cfe5780 Cc: freebsd-current@freebsd.org, Alexey Karagodov Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 12:35:19 -0000 On 1/26/07, Stefan Ehmann wrote: > On Friday 26 January 2007 11:00, Alexey Karagodov wrote: > > what manufacturer says about usb speeds? > > that is the question > > Well, "up to 56MB/s" which is pretty much full USB2 speed. > > But writing it on the box doesn't mean the speed can actually be reached. > > Benchmarking on windows might be interesting, but I don't know how to measure > raw disk io on windows. Format the disk, copy a large file to/from it, divide its size by time spent, add the word "approximately" :-) From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 12:41:06 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A07516A402 for ; Fri, 26 Jan 2007 12:41:06 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id CF44213C4A8 for ; Fri, 26 Jan 2007 12:41:05 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 26 Jan 2007 12:41:04 -0000 Received: from h081217095052.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.95.52] by mail.gmx.net (mp028) with SMTP; 26 Jan 2007 13:41:04 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: "Andrew Pantyukhin" Date: Fri, 26 Jan 2007 13:41:03 +0100 User-Agent: KMail/1.9.5 References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261332.54375.shoesoft@gmx.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701261341.03742.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org, Alexey Karagodov Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 12:41:06 -0000 On Friday 26 January 2007 13:35, Andrew Pantyukhin wrote: > On 1/26/07, Stefan Ehmann wrote: > > On Friday 26 January 2007 11:00, Alexey Karagodov wrote: > > > what manufacturer says about usb speeds? > > > that is the question > > > > Well, "up to 56MB/s" which is pretty much full USB2 speed. > > > > But writing it on the box doesn't mean the speed can actually be reached. > > > > Benchmarking on windows might be interesting, but I don't know how to > > measure raw disk io on windows. > > Format the disk, copy a large file to/from it, divide > its size by time spent, add the word "approximately" :-) I'd rather not format a drive with my backups and other stuff on it :-) From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 14:06:56 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 176E016A402 for ; Fri, 26 Jan 2007 14:06:56 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from mail08b.verio.de (mail08b.verio.de [213.198.55.74]) by mx1.freebsd.org (Postfix) with SMTP id 6162613C483 for ; Fri, 26 Jan 2007 14:06:55 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from mx29.stngva01.us.mxservers.net (204.202.242.73) by mail08b.verio.de (RS ver 1.0.95vs) with SMTP id 2-083040412; Fri, 26 Jan 2007 15:06:53 +0100 (CET) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx29.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id cfa0ab54.20584.103.mx29.stngva01.us.mxservers.net; Fri, 26 Jan 2007 09:06:52 -0500 (EST) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.8/8.11.6) with ESMTP id l0QE6np5010845; Fri, 26 Jan 2007 15:06:49 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200701261406.l0QE6np5010845@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: Stefan Ehmann In-Reply-To: Message from Stefan Ehmann of "Fri, 26 Jan 2007 13:41:03 +0100." <200701261341.03742.shoesoft@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Jan 2007 15:06:49 +0100 From: Gary Jennejohn X-Spam: [F=0.2083701118; heur=0.500(-19800); stat=0.195; spamtraq-heur=0.519(2007010918)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: freebsd-current@freebsd.org, Alexey Karagodov Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 14:06:56 -0000 Stefan Ehmann writes: > On Friday 26 January 2007 13:35, Andrew Pantyukhin wrote: > > On 1/26/07, Stefan Ehmann wrote: > > > On Friday 26 January 2007 11:00, Alexey Karagodov wrote: > > > > what manufacturer says about usb speeds? > > > > that is the question > > > > > > Well, "up to 56MB/s" which is pretty much full USB2 speed. > > > > > > But writing it on the box doesn't mean the speed can actually be reached. > > > > > > Benchmarking on windows might be interesting, but I don't know how to > > > measure raw disk io on windows. > > > > Format the disk, copy a large file to/from it, divide > > its size by time spent, add the word "approximately" :-) > > I'd rather not format a drive with my backups and other stuff on it :-) > If you want to test under windows then you could use hdbench from c't magazine. I think it has a non-destructive mode. It's what they use to do all their disk tests. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 15:27:25 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02F7B16A407 for ; Fri, 26 Jan 2007 15:27:25 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 50D3213C48E for ; Fri, 26 Jan 2007 15:27:23 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 26 Jan 2007 15:27:22 -0000 Received: from h081217095052.dyn.cm.kabsi.at (EHLO taxman.pepperland) [81.217.95.52] by mail.gmx.net (mp047) with SMTP; 26 Jan 2007 16:27:22 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Gary Jennejohn Date: Fri, 26 Jan 2007 16:27:20 +0100 User-Agent: KMail/1.9.5 References: <200701261406.l0QE6np5010845@peedub.jennejohn.org> In-Reply-To: <200701261406.l0QE6np5010845@peedub.jennejohn.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200701261627.20976.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org, Alexey Karagodov Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 15:27:25 -0000 On Friday 26 January 2007 15:06, Gary Jennejohn wrote: > Stefan Ehmann writes: > > On Friday 26 January 2007 13:35, Andrew Pantyukhin wrote: > > > On 1/26/07, Stefan Ehmann wrote: > > > > On Friday 26 January 2007 11:00, Alexey Karagodov wrote: > > > > > what manufacturer says about usb speeds? > > > > > that is the question > > > > > > > > Well, "up to 56MB/s" which is pretty much full USB2 speed. > > > > > > > > But writing it on the box doesn't mean the speed can actually be > > > > reached. > > > > > > > > Benchmarking on windows might be interesting, but I don't know how to > > > > measure raw disk io on windows. > > > > > > Format the disk, copy a large file to/from it, divide > > > its size by time spent, add the word "approximately" :-) > > > > I'd rather not format a drive with my backups and other stuff on it :-) > > If you want to test under windows then you could use hdbench from c't > magazine. I think it has a non-destructive mode. It's what they use to > do all their disk tests. Thanks for the tip. Using h2benchw, I get 30.5MB/s - so no magic speed increase on windows. The limiting factor is not the hd, using ata I get more than 65MB/s. According to [1] "The maximum rate currently (2006) attained with real devices is about [...] 30 MB/s". [1] http://en.wikipedia.org/wiki/Usb From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 15:37:14 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E0CED16A404; Fri, 26 Jan 2007 15:37:14 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id 2DB8A13C483; Fri, 26 Jan 2007 15:37:13 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe09.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 225692775; Fri, 26 Jan 2007 15:37:11 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 15:36:48 +0100 User-Agent: KMail/1.9.5 References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261341.03742.shoesoft@gmx.net> In-Reply-To: <200701261341.03742.shoesoft@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701261536.48893.hselasky@c2i.net> Cc: Alexey Karagodov , Stefan Ehmann Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 15:37:15 -0000 On Friday 26 January 2007 13:41, Stefan Ehmann wrote: > On Friday 26 January 2007 13:35, Andrew Pantyukhin wrote: > > On 1/26/07, Stefan Ehmann wrote: > > > On Friday 26 January 2007 11:00, Alexey Karagodov wrote: > > > > what manufacturer says about usb speeds? > > > > that is the question > > > > > > Well, "up to 56MB/s" which is pretty much full USB2 speed. It is called high speed USB, and it can go up 53 MB/s with a payload of 512 bytes per packet according to "Table 5-10. High-speed Bulk Transaction Limits" in the USB 2.0 specification. The table does not say anything about whether this include bit-stuffing or not. If bit stuffing is not included, then you have to divide this value by 1.20 approximately for the worst case, all 1's. 53 MB/s div 1.20 = 44 MB/s. > > > > > > But writing it on the box doesn't mean the speed can actually be > > > reached. > > > > > > Benchmarking on windows might be interesting, but I don't know how to > > > measure raw disk io on windows. > > > > Format the disk, copy a large file to/from it, divide > > its size by time spent, add the word "approximately" :-) > > I'd rather not format a drive with my backups and other stuff on it :-) Results with the new USB stack*: Changing the interrupt delay from 2 microframes to 1 microframe gave me 2MBytes more per second on the EHCI controller. I connected two high speed "umass" capable devices to the same EHCI controller on my computer, and did a "dd" on both devices at the same time, with a block size of 131072 bytes. The one device transferred 22 MB/s. The other device transferred 16 MB/s. Summed up this yields 38 MB/s. Used alone these devices can transfer 27 MB/s and 20 MB/s. It seems clear that the EHCI controller is saturated at 38 MB/s. %dmesg |grep ehci ehci0: mem 0xe0100000-0xe01003ff irq 10 at device 29.7 on pci0 usb3: on ehci0 % --HPS * http://www.turbocat.net/~hselasky/usb4bsd or see the FreeBSD-perforce USB project. From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 15:52:43 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8E0616A403 for ; Fri, 26 Jan 2007 15:52:43 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by mx1.freebsd.org (Postfix) with ESMTP id 85FC813C4A8 for ; Fri, 26 Jan 2007 15:52:43 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from [192.168.0.13] (dsl-63-249-90-35.cruzio.com [63.249.90.35]) by dommail.onthenet.com.au (MOS 3.5.7-GR) with ESMTP id CMF78113 (AUTH peterg@ptree32.com.au); Sat, 27 Jan 2007 01:39:20 +1000 (EST) Message-ID: <45BA2002.1080405@freebsd.org> Date: Fri, 26 Jan 2007 07:36:34 -0800 From: Peter Grehan User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: LI Xin Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: grehan@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 15:52:44 -0000 Known issue with binutils when x-building on 64-bit hosts, see amd64/102996. later, Peter. From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 15:58:37 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C15316A400 for ; Fri, 26 Jan 2007 15:58:37 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id C68C913C48C for ; Fri, 26 Jan 2007 15:58:36 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id BAC73EB3A1D; Fri, 26 Jan 2007 23:58:35 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id dMEw4jQwJcjN; Fri, 26 Jan 2007 23:58:28 +0800 (CST) Received: from [192.168.1.32] (unknown [221.221.168.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 47C67EB3988; Fri, 26 Jan 2007 23:58:28 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:organization:user-agent:mime-version:to:cc: subject:references:in-reply-to:x-enigmail-version:content-type; b=k/e+50rvKfpkKOAjrBjo1Lj0q2uAYYpvbyDDvHaIwdV6rIfLCNPDrd5ra24H+PI/f UVoIgU0OZDlBPaAaktPAg== Message-ID: <45BA2521.9020106@delphij.net> Date: Fri, 26 Jan 2007 23:58:25 +0800 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207) MIME-Version: 1.0 To: Divacky Roman References: <45B9D204.9030503@delphij.net> <20070126105822.GA72945@stud.fit.vutbr.cz> In-Reply-To: <20070126105822.GA72945@stud.fit.vutbr.cz> X-Enigmail-Version: 0.94.1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig263FFC408EEF191AE73001A0" Cc: FreeBSD Current Subject: Re: HEADSUP: Replacing GNU gzip(1) implementation with a BSD licensed version X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 15:58:37 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig263FFC408EEF191AE73001A0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Divacky Roman wrote: > On Fri, Jan 26, 2007 at 06:03:48PM +0800, LI Xin wrote: >> Dear folks, >> >> A BSD licensed gzip version has been ported from NetBSD, in order to >> replace the current GNU GPL'ed gzip version found in our base system. >> >> The new gzip would be added to src/usr.bin. It is expected to hit the= >> tree soon. >=20 > how does performance compare between the bsdzip and gzip? If you mean speed, I have only tested this roughly on an Xeon based i386 box, and the result was that difference are within epsilon. Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig263FFC408EEF191AE73001A0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFuiUhOfuToMruuMARA5BtAJ4wY84a7P8PR5YQheXzB189Yb8gxACbBYyI Djo8sZigKMnY4kEQBsKdQLQ= =Y1r9 -----END PGP SIGNATURE----- --------------enig263FFC408EEF191AE73001A0-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 16:31:41 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5E0C16A402; Fri, 26 Jan 2007 16:31:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 595C213C494; Fri, 26 Jan 2007 16:31:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0QGSF0I046531; Fri, 26 Jan 2007 09:28:16 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 26 Jan 2007 09:28:42 -0700 (MST) Message-Id: <20070126.092842.1973603551.imp@bsdimp.com> To: cperciva@freebsd.org From: "M. Warner Losh" In-Reply-To: <45B99A59.6070902@freebsd.org> References: <45B9895B.9020709@freebsd.org> <20070125.224642.353412237.imp@bsdimp.com> <45B99A59.6070902@freebsd.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 26 Jan 2007 09:28:16 -0700 (MST) Cc: current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 16:31:41 -0000 In message: <45B99A59.6070902@freebsd.org> Colin Percival writes: : M. Warner Losh wrote: : > In message: <45B9895B.9020709@freebsd.org> : > Colin Percival writes: : > : M. Warner Losh wrote: : > : > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. : > : : > : I get 25MB/s from my Vantec Nexstar3 : > : USB 2.0 enclosure: : > : : > : http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html : > : > Still, 25MB/s is no 40MB/s... : : Sure, but it means that the performance issues aren't simply a global "USB 2.0 : is bad". What does `diskinfo -c` say about your firewire and USB interfaces? Actually, I think it does mean exactly that. At least with our code base and the hardware I have access to. I tested another enclosures on my amd64 laptop running current and my i386 laptop running 6.2R (+ current cardbus) and found similar results. 6.2R on i386 was even slower, despite the laptop being a 3GHz pentium. I got similar results with a cardbus usb2.0 card as I did with the built-in usb 2.0 ports. diskinfo -c tells me that usb is 3 times slower per block, and has a 6 times higher command overhead. Firewire is faster than local ata, but has a 20% higher command overhead. usb: I/O command overhead: time to read 10MB block 0.971377 sec = 0.047 msec/sector time to read 20480 sectors 15.577325 sec = 0.761 msec/sector calculated command overhead = 0.713 msec/sector firewire: I/O command overhead: time to read 10MB block 0.299125 sec = 0.015 msec/sector time to read 20480 sectors 2.804367 sec = 0.137 msec/sector calculated command overhead = 0.122 msec/sector ata: (this is a different disk) ad0 I/O command overhead: time to read 10MB block 0.346256 sec = 0.017 msec/sector time to read 20480 sectors 2.249805 sec = 0.110 msec/sector calculated command overhead = 0.093 msec/sector usb 2.0 shouldn't be this slow, and I think it points to our usb code being poor at something that's introducing a huge overhead into commands, as well as creating greater overhead on long transfers. It has been suggested that the limited scatter gather in the usb code might be causing some of the problems. I haven't tested the Hans Petter Selasky usb stack to see if it is any better. It appears there's no scatter gather there, so that might make the numbers even worse. But if the command queueing is better, then it might make up for it. Warner From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 16:42:03 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9602416A402 for ; Fri, 26 Jan 2007 16:42:03 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.freebsd.org (Postfix) with ESMTP id 48DDE13C4A8 for ; Fri, 26 Jan 2007 16:42:03 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.47] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.8/8.13.6) with ESMTP id l0QGfuOQ044549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Jan 2007 08:41:58 -0800 (PST) (envelope-from sobomax@FreeBSD.org) Message-ID: <45BA2F32.1050806@FreeBSD.org> Date: Fri, 26 Jan 2007 08:41:22 -0800 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Andrew Pantyukhin References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261052.12435.shoesoft@gmx.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, "M. Warner Losh" , Stefan Ehmann Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 16:42:03 -0000 Andrew Pantyukhin wrote: > On 1/26/07, Stefan Ehmann wrote: >> On Friday 26 January 2007 03:24, M. Warner Losh wrote: >> > On a lark, I just got a combo USB/Firewire external disk drive. I ran >> > some crude benchmarks, and I was surprised by what I found. This is >> > on a fairly stock -current kernel. >> > >> > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. >> > This is with a simple dd command: >> >> On my i386 notebook with USB 2.0 enclosure. >> Linux: 31.5MB/s >> FreeBSD: 27.5MB/s >> >> There's still room for improvement but numbers don't seem that bad. >> >> Maybe you should try knoppix or so to verify it's not the drive's >> fault. Other >> than that I'd also guess it's an amd64 problem. > > IIRC I got around 50Mb/s with most USB2.0 enclosures (and > drives capable of sustaining the speed) under Windows. As long as I know, FreeBSD USB stack doesn't support bulk transfers that are necessary to get a good speed of an USB drive. -Maxim From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 16:55:56 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B00716A401 for ; Fri, 26 Jan 2007 16:55:56 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id B9E0D13C4A8 for ; Fri, 26 Jan 2007 16:55:55 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 26 Jan 2007 11:27:14 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id MVG01775; Fri, 26 Jan 2007 11:27:08 -0500 (EST) Received: from 209-6-203-219.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.203.219]) by smtp01.lnh.mail.rcn.net with ESMTP; 26 Jan 2007 11:27:02 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17850.11127.944124.276290@jerusalem.litteratus.org> Date: Fri, 26 Jan 2007 11:25:27 -0500 To: current@freebsd.org In-Reply-To: <20070125.192448.-432840241.imp@bsdimp.com> References: <20070125.192448.-432840241.imp@bsdimp.com> X-Mailer: VM 7.17 under 21.5 (beta27) "fiddleheads" XEmacs Lucid X-Junkmail-Status: score=10/50, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090203.45BA2BE0.00A9,ss=1,fgs=0, ip=207.172.4.11, so=2006-05-09 23:27:51, dmn=5.2.125/2006-10-10 Cc: Subject: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 16:55:56 -0000 M. Warner Losh writes: > On a lark, I just got a combo USB/Firewire external disk drive. > I ran some crude benchmarks, and I was surprised by what I found. > This is on a fairly stock -current kernel. > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. As long as we're on the subject: I'm testing a USB-connected external hard drive (PATA-133) as a replacement for SCSI-I/DLT in a dump-driven backup arrangement for a P4/2.25 ghz+80 mbyte/sec SCSI box. Hardware specs as reported by the boot probe are appended. "diskinfo -tc" returns: 512 # sectorsize 100256284672 # mediasize in bytes (93G) 195813056 # mediasize in sectors 12188 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. I/O command overhead: time to read 10MB block 0.590932 sec = 0.029 msec/sector time to read 20480 sectors 16.156980 sec = 0.789 msec/sector calculated command overhead = 0.760 msec/sector Seek times: Full stroke: 250 iter in 5.276618 sec = 21.106 msec Half stroke: 250 iter in 4.144696 sec = 16.579 msec Quarter stroke: 500 iter in 6.929293 sec = 13.859 msec Short forward: 400 iter in 2.341049 sec = 5.853 msec Short backward: 400 iter in 3.632142 sec = 9.080 msec Seq outer: 2048 iter in 1.645352 sec = 0.803 msec Seq inner: 2048 iter in 1.598203 sec = 0.780 msec Transfer rates: outside: 102400 kbytes in 5.938111 sec = 17245 kbytes/sec middle: 102400 kbytes in 6.076508 sec = 16852 kbytes/sec inside: 102400 kbytes in 5.807954 sec = 17631 kbytes/sec Performance, so far, has been better than the old set-up but far less than thrilling and I'd like to understand why. Dump, using these options: $DUMP_LEVEL -D $DUMPDATES_FILE -Lau -f gets me 2 +/- 0.2 mbytes/sec. Is this a reasonable value? (I.e. is dump the limiting factor?) Do I need to reconfigure something, or is my hardware just lame? I'm not expecting to get the full 40 mbyte/sec of USB 2.0 spec; 20 or even 10 would be fine. But 2? Ouch. Respectfully, Robert Huff jerusalem kernel: ehci0: mem 0xf0000000-0xf0000 0ff irq 15 at device 10.3 on pci0 jerusalem kernel: ehci0: [GIANT-LOCKED] jerusalem kernel: usb3: on ehci0 huff@jerusalem>> jerusalem kernel: usb3: EHCI version 1.0 jerusalem kernel: usb3: companion controller, 2 ports each: usb2 jerusalem kernel: usb3: on ehci0 jerusalem kernel: usb3: USB revision 2.0 jerusalem kernel: uhub3: on usb3 jerusalem kernel: uhub3: 6 ports with 6 removable, self powered jerusalem kernel: umass0: on uhub3 jerusalem kernel: (probe15:umass-sim0:0:0:0): Uninitialized Transport 5:0? jerusalem kernel: da2 at umass-sim0 bus 0 target 0 lun 0 jerusalem kernel: da2: Fixed Direct Acces s SCSI-0 device jerusalem kernel: da2: 40.000MB/s transfers jerusalem kernel: da2: 95611MB (195813072 512 byte sectors: 255H 63S/T 12188C) From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 16:59:12 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8DF7E16A400 for ; Fri, 26 Jan 2007 16:59:12 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.freebsd.org (Postfix) with ESMTP id 5EAE013C489 for ; Fri, 26 Jan 2007 16:59:12 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.13.6/8.13.6) with ESMTP id l0QGxBXa014532 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 26 Jan 2007 11:59:11 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id l0QGx6HD015009; Fri, 26 Jan 2007 11:59:06 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin Message-ID: <17850.13146.266196.499166@grasshopper.cs.duke.edu> Date: Fri, 26 Jan 2007 11:59:06 -0500 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@freebsd.org X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Subject: excessive TCP duplicate acks? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 16:59:12 -0000 When running some benchmarks, I noticed tons of duplicate acks showing up in systat -tcp (thousands, or tens of thousands per second). Taking a trace, I see that -current seems to send "lots" of duplicate acks. At first I thought this was a driver bug, but I've seen it with 3 different drivers (mxge, nve, xl) and at various network speeds. It seems to happen when the -current machine is the "sender" in a netperf, and seems to happen with both a linux a FreeBSD receiver, and is easy to reproduce using -current from yesterday (running on amd64 if it matters). >From my very naive tcpdump reading skills, it looks like the FreeBSD machine sends a full window with a partial payload and a push flag in the last segment. It ignores (or does not yet see the receiver's acks). It then spews tons of duplicate acks at the reciever until it notices the acks, and starts sending data again. This happens over and over again.. Is this normal, or is there something wrong? In the appended tcpdump snippet taken at the receiver, 172.31.193.16 was sending a netperf (netperf -H172.31.193.15 -- -s65535 -S32767) to 172.31.193.15. I can make a raw dump file available if anybody is interested. Thanks, Drew 11:14:13.524661 IP 172.31.193.16.65344 > 172.31.193.15.32809: S 1455368652:1455368652(0) win 65535 11:14:13.524668 IP 172.31.193.15.32809 > 172.31.193.16.65344: S 3829892109:3829892109(0) ack 1455368653 win 5792 11:14:13.524727 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.525051 IP 172.31.193.16.65344 > 172.31.193.15.32809: . 1:1449(1448) ack 1 win 65535 11:14:13.525061 IP 172.31.193.15.32809 > 172.31.193.16.65344: . ack 1449 win 17 11:14:13.525174 IP 172.31.193.16.65344 > 172.31.193.15.32809: . 1449:2897(1448) ack 1 win 65535 <..many packets omitted..> 11:14:13.530344 IP 172.31.193.16.65344 > 172.31.193.15.32809: . 62265:63713(1448) ack 1 win 65535 11:14:13.530467 IP 172.31.193.16.65344 > 172.31.193.15.32809: . 63713:65161(1448) ack 1 win 65535 11:14:13.530474 IP 172.31.193.15.32809 > 172.31.193.16.65344: . ack 65161 win 94 11:14:13.530504 IP 172.31.193.16.65344 > 172.31.193.15.32809: P 65161:65536(375) ack 1 win 65535 11:14:13.530511 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530516 IP 172.31.193.15.32809 > 172.31.193.16.65344: . ack 65536 win 94 11:14:13.530518 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530525 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530533 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530540 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530547 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530554 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530561 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530569 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530576 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530584 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530591 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530597 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530604 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530612 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530619 IP 172.31.193.16.65344 > 172.31.193.15.32809: . ack 1 win 65535 11:14:13.530752 IP 172.31.193.16.65344 > 172.31.193.15.32809: . 65536:66865(1329) ack 1 win 65535 11:14:13.530760 IP 172.31.193.15.32809 > 172.31.193.16.65344: . ack 66865 win 94 11:14:13.530884 IP 172.31.193.16.65344 > 172.31.193.15.32809: . 66865:68313(1448) ack 1 win 65535 11:14:13.531007 IP 172.31.193.16.65344 > 172.31.193.15.32809: . 68313:69761(1448) ack 1 win 65535 From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 17:03:53 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F05E216A402; Fri, 26 Jan 2007 17:03:53 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id 1A47213C46B; Fri, 26 Jan 2007 17:03:52 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe09.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 225833407; Fri, 26 Jan 2007 18:03:50 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 18:03:27 +0100 User-Agent: KMail/1.9.5 References: <45B9895B.9020709@freebsd.org> <45B99A59.6070902@freebsd.org> <20070126.092842.1973603551.imp@bsdimp.com> In-Reply-To: <20070126.092842.1973603551.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701261803.28024.hselasky@c2i.net> Cc: cperciva@freebsd.org, "M. Warner Losh" , current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 17:03:54 -0000 On Friday 26 January 2007 17:28, M. Warner Losh wrote: > In message: <45B99A59.6070902@freebsd.org> > > Colin Percival writes: > : M. Warner Losh wrote: > : > In message: <45B9895B.9020709@freebsd.org> > : > > : > Colin Percival writes: > : > : M. Warner Losh wrote: > : > : > Firewire does around 40MB/s, while USB 2.0 maxes out at about > : > : > 12MB/s. > : > : > : > : I get 25MB/s from my Vantec Nexstar3 > : > : USB 2.0 enclosure: > : > : > : > : http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html > : > > : > Still, 25MB/s is no 40MB/s... > : > : Sure, but it means that the performance issues aren't simply a global > : "USB 2.0 is bad". What does `diskinfo -c` say about your firewire and > : USB interfaces? > > > I haven't tested the Hans Petter Selasky usb stack to see if it is any > better. It appears there's no scatter gather there, so that might > make the numbers even worse. But if the command queueing is better, > then it might make up for it. Yes, it has scatter and gather since August last year :-) But all USB drivers currently use copy-in/copy-out to/from the DMA buffer. With regard to "umass" there is one copy-out/copy-in per transfer. Currently all transfers are done in bulks of 131072 bytes, so there is not too much overhead. I am considering direct buffer loading. --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 17:33:47 2007 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 37D7E16A400 for ; Fri, 26 Jan 2007 17:33:47 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 9BB6313C487 for ; Fri, 26 Jan 2007 17:33:46 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (dybkve@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l0QHXdrG078260; Fri, 26 Jan 2007 18:33:45 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l0QHXdY1078259; Fri, 26 Jan 2007 18:33:39 +0100 (CET) (envelope-from olli) Date: Fri, 26 Jan 2007 18:33:39 +0100 (CET) Message-Id: <200701261733.l0QHXdY1078259@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, roberthuff@rcn.com In-Reply-To: <17850.11127.944124.276290@jerusalem.litteratus.org> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 26 Jan 2007 18:33:45 +0100 (CET) Cc: Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, roberthuff@rcn.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 17:33:47 -0000 Robert Huff wrote: > As long as we're on the subject: > I'm testing a USB-connected external hard drive (PATA-133) as a > replacement for SCSI-I/DLT in a dump-driven backup arrangement for a > P4/2.25 ghz+80 mbyte/sec SCSI box. > [...] > Performance, so far, has been better than the old set-up but far > less than thrilling and I'd like to understand why. Dump, using > these options: > > $DUMP_LEVEL -D $DUMPDATES_FILE -Lau -f > > gets me 2 +/- 0.2 mbytes/sec. > Is this a reasonable value? (I.e. is dump the limiting > factor?) Do I need to reconfigure something, or is my hardware just > lame? > I'm not expecting to get the full 40 mbyte/sec of USB 2.0 spec; > 20 or even 10 would be fine. But 2? Ouch. Historically the performance of dump(8) has always been quite bad. It didn't matter in ancient times because tape drives were slow back then, so dump(8) was not the limiting factor. ;-) For that reason I try to avoid dump(8) when possible. Maybe you should try to use tar, cpio or pax instead and check if the performance is better. I'm not sure if dump(8) has been improved recently (I confess that I haven't tried). Maybe it is better now. If you continue to use dump(8), make sure that you specify a reasonable cache size (-C option). Refer to the manual page for details. Without that option, performance will be _really_ bad. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd It's trivial to make fun of Microsoft products, but it takes a real man to make them work, and a God to make them do anything useful. From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 18:03:59 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3CF9E16A401 for ; Fri, 26 Jan 2007 18:03:59 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id B7A0413C491 for ; Fri, 26 Jan 2007 18:03:58 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [193.217.102.48] (account mc467741@c2i.net HELO [10.0.0.249]) by mailfe09.swip.net (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 225833407; Fri, 26 Jan 2007 18:03:50 +0100 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Fri, 26 Jan 2007 18:03:27 +0100 User-Agent: KMail/1.9.5 References: <45B9895B.9020709@freebsd.org> <45B99A59.6070902@freebsd.org> <20070126.092842.1973603551.imp@bsdimp.com> In-Reply-To: <20070126.092842.1973603551.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701261803.28024.hselasky@c2i.net> Cc: cperciva@freebsd.org, "M. Warner Losh" , current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 18:03:59 -0000 On Friday 26 January 2007 17:28, M. Warner Losh wrote: > In message: <45B99A59.6070902@freebsd.org> > > Colin Percival writes: > : M. Warner Losh wrote: > : > In message: <45B9895B.9020709@freebsd.org> > : > > : > Colin Percival writes: > : > : M. Warner Losh wrote: > : > : > Firewire does around 40MB/s, while USB 2.0 maxes out at about > : > : > 12MB/s. > : > : > : > : I get 25MB/s from my Vantec Nexstar3 > : > : USB 2.0 enclosure: > : > : > : > : http://www.daemonology.net/blog/2006-01-28-vantex-nexstar3.html > : > > : > Still, 25MB/s is no 40MB/s... > : > : Sure, but it means that the performance issues aren't simply a global > : "USB 2.0 is bad". What does `diskinfo -c` say about your firewire and > : USB interfaces? > > > I haven't tested the Hans Petter Selasky usb stack to see if it is any > better. It appears there's no scatter gather there, so that might > make the numbers even worse. But if the command queueing is better, > then it might make up for it. Yes, it has scatter and gather since August last year :-) But all USB drivers currently use copy-in/copy-out to/from the DMA buffer. With regard to "umass" there is one copy-out/copy-in per transfer. Currently all transfers are done in bulks of 131072 bytes, so there is not too much overhead. I am considering direct buffer loading. --HPS From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 18:40:38 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9EA3A16A402 for ; Fri, 26 Jan 2007 18:40:38 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 5D74613C48D for ; Fri, 26 Jan 2007 18:40:38 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mr02.lnh.mail.rcn.net ([207.172.157.22]) by smtp02.lnh.mail.rcn.net with ESMTP; 26 Jan 2007 13:12:09 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr02.lnh.mail.rcn.net (MOS 3.7.5a-GA) with ESMTP id MVG35828; Fri, 26 Jan 2007 13:11:57 -0500 (EST) Received: from 209-6-203-219.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.203.219]) by smtp01.lnh.mail.rcn.net with ESMTP; 26 Jan 2007 13:11:50 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17850.17413.363571.54932@jerusalem.litteratus.org> Date: Fri, 26 Jan 2007 13:10:13 -0500 To: freebsd-current@freebsd.org In-Reply-To: <200701261733.l0QHXdY1078259@lurza.secnetix.de> References: <17850.11127.944124.276290@jerusalem.litteratus.org> <200701261733.l0QHXdY1078259@lurza.secnetix.de> X-Mailer: VM 7.17 under 21.5 (beta27) "fiddleheads" XEmacs Lucid X-Junkmail-Status: score=10/50, host=mr02.lnh.mail.rcn.net X-Junkmail-SD-Raw: score=unknown, refid=str=0001.0A090205.45BA4478.009F,ss=1,fgs=0, ip=207.172.4.11, so=2006-05-09 23:27:51, dmn=5.2.125/2006-10-10 Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 18:40:38 -0000 Oliver Fromme writes: > I'm not sure if dump(8) has been improved recently (I > confess that I haven't tried). Maybe it is better now. > If you continue to use dump(8), make sure that you > specify a reasonable cache size (-C option). Refer to > the manual page for details. Without that option, > performance will be _really_ bad. I've made the adjustment and will see what happens. Thanks. Robert Huff From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 18:51:52 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 507C216A401 for ; Fri, 26 Jan 2007 18:51:52 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id EBFD613C487 for ; Fri, 26 Jan 2007 18:51:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0QIo4Ff047832; Fri, 26 Jan 2007 11:50:04 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 26 Jan 2007 11:50:03 -0700 (MST) Message-Id: <20070126.115003.78754521.imp@bsdimp.com> To: delphij@delphij.net From: Warner Losh In-Reply-To: <45B9D204.9030503@delphij.net> References: <45B9D204.9030503@delphij.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 26 Jan 2007 11:50:04 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: Replacing GNU gzip(1) implementation with a BSD licensed version X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 18:51:52 -0000 > A BSD licensed gzip version has been ported from NetBSD, in order to > replace the current GNU GPL'ed gzip version found in our base system. > > The new gzip would be added to src/usr.bin. It is expected to hit the > tree soon. Thanks! Warner From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 18:51:52 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D3DD516A402 for ; Fri, 26 Jan 2007 18:51:52 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 92DB113C48A for ; Fri, 26 Jan 2007 18:51:52 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0QIniun047824; Fri, 26 Jan 2007 11:49:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 26 Jan 2007 11:49:44 -0700 (MST) Message-Id: <20070126.114944.104080809.imp@bsdimp.com> To: shoesoft@gmx.net From: Warner Losh In-Reply-To: <200701261052.12435.shoesoft@gmx.net> References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261052.12435.shoesoft@gmx.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 26 Jan 2007 11:49:44 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 18:51:52 -0000 From: Stefan Ehmann Subject: Re: Interesting speed benchmarks Date: Fri, 26 Jan 2007 10:52:11 +0100 > On Friday 26 January 2007 03:24, M. Warner Losh wrote: > > On a lark, I just got a combo USB/Firewire external disk drive. I ran > > some crude benchmarks, and I was surprised by what I found. This is > > on a fairly stock -current kernel. > > > > Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. > > This is with a simple dd command: > > On my i386 notebook with USB 2.0 enclosure. > Linux: 31.5MB/s > FreeBSD: 27.5MB/s > > There's still room for improvement but numbers don't seem that bad. > > Maybe you should try knoppix or so to verify it's not the drive's fault. Other > than that I'd also guess it's an amd64 problem. It is not an AMD64 problem. I get the same numbers on my i386 latpop as I get on my amd64 laptop. Actually, I get WORSE numbers on the i386 laptop by about 20%. It isn't the drive's fault. Otherwise, firewire wouldn't get 40MB/s. The same drive, the same enclusure are used for both the USB and firewire tests. It is about as apples to apples as you can get. There's some serious performance issues in the usb stack. Warner From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 19:48:08 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8694F16A400 for ; Fri, 26 Jan 2007 19:48:08 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id 44B2113C481 for ; Fri, 26 Jan 2007 19:48:08 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 8FE3F2D4AB0; Fri, 26 Jan 2007 19:19:21 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 9C17C11434; Fri, 26 Jan 2007 20:19:52 +0100 (CET) Date: Fri, 26 Jan 2007 20:19:52 +0100 From: "Simon L. Nielsen" To: LI Xin Message-ID: <20070126191951.GA973@zaphod.nitro.dk> References: <45B9D204.9030503@delphij.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45B9D204.9030503@delphij.net> User-Agent: Mutt/1.5.11 Cc: FreeBSD Current Subject: Re: HEADSUP: Replacing GNU gzip(1) implementation with a BSD licensed version X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 19:48:08 -0000 On 2007.01.26 18:03:48 +0800, LI Xin wrote: > A BSD licensed gzip version has been ported from NetBSD, in order to > replace the current GNU GPL'ed gzip version found in our base system. > > The new gzip would be added to src/usr.bin. It is expected to hit the > tree soon. Great, thanks for working on this! So, in perhaps 3 years we don't have to support gzip wrt. security anymore :-). -- Simon L. Nielsen From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 19:48:16 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1C1216A4C7 for ; Fri, 26 Jan 2007 19:48:16 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id A068E13C458 for ; Fri, 26 Jan 2007 19:48:16 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [192.168.42.21] (andersonbox1.centtech.com [192.168.42.21]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l0QJ9T15056585; Fri, 26 Jan 2007 13:09:29 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <45BA51EA.3070901@freebsd.org> Date: Fri, 26 Jan 2007 13:09:30 -0600 From: Eric Anderson User-Agent: Thunderbird 1.5.0.9 (X11/20070121) MIME-Version: 1.0 To: Warner Losh References: <20070125.192448.-432840241.imp@bsdimp.com> <200701261052.12435.shoesoft@gmx.net> <20070126.114944.104080809.imp@bsdimp.com> In-Reply-To: <20070126.114944.104080809.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/2493/Fri Jan 26 06:00:46 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-current@freebsd.org, shoesoft@gmx.net Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 19:48:17 -0000 On 01/26/07 12:49, Warner Losh wrote: > From: Stefan Ehmann > Subject: Re: Interesting speed benchmarks > Date: Fri, 26 Jan 2007 10:52:11 +0100 > >> On Friday 26 January 2007 03:24, M. Warner Losh wrote: >>> On a lark, I just got a combo USB/Firewire external disk drive. I ran >>> some crude benchmarks, and I was surprised by what I found. This is >>> on a fairly stock -current kernel. >>> >>> Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. >>> This is with a simple dd command: >> On my i386 notebook with USB 2.0 enclosure. >> Linux: 31.5MB/s >> FreeBSD: 27.5MB/s >> >> There's still room for improvement but numbers don't seem that bad. >> >> Maybe you should try knoppix or so to verify it's not the drive's fault. Other >> than that I'd also guess it's an amd64 problem. > > It is not an AMD64 problem. I get the same numbers on my i386 latpop > as I get on my amd64 laptop. Actually, I get WORSE numbers on the > i386 laptop by about 20%. > > It isn't the drive's fault. Otherwise, firewire wouldn't get 40MB/s. > The same drive, the same enclusure are used for both the USB and > firewire tests. It is about as apples to apples as you can get. > > There's some serious performance issues in the usb stack. > > Warner A few tidbits of information (may be useful, maybe not): - I've seen the firewire part of the enclosure be faster than the USB part. The chips that run it are possibly different, so that shouldn't be forgotten. I've had a few USB->flash adapters that got lousy performance, but when I switched to a USB->SATA flash card reader, the performance doubled. - For those testing using a file system - STOP! It's not a good test of the throughput of the device, and depends on a lot of variables. dd or diskinfo are decent generic tools, but in Windows you just can't use a file system benchmark to compare. - If you read/write less than the drive cache, it should remove the latency of the drive from the equation, right? Eric From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 21:09:49 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4CD016A401; Fri, 26 Jan 2007 21:09:49 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 5531713C49D; Fri, 26 Jan 2007 21:09:49 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l0QL7U5C049201; Fri, 26 Jan 2007 14:07:30 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 26 Jan 2007 14:07:56 -0700 (MST) Message-Id: <20070126.140756.-311940260.imp@bsdimp.com> To: anderson@freebsd.org From: "M. Warner Losh" In-Reply-To: <45BA51EA.3070901@freebsd.org> References: <200701261052.12435.shoesoft@gmx.net> <20070126.114944.104080809.imp@bsdimp.com> <45BA51EA.3070901@freebsd.org> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Fri, 26 Jan 2007 14:07:31 -0700 (MST) Cc: freebsd-current@freebsd.org, shoesoft@gmx.net Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 21:09:49 -0000 In message: <45BA51EA.3070901@freebsd.org> Eric Anderson writes: : On 01/26/07 12:49, Warner Losh wrote: : > From: Stefan Ehmann : > Subject: Re: Interesting speed benchmarks : > Date: Fri, 26 Jan 2007 10:52:11 +0100 : > : >> On Friday 26 January 2007 03:24, M. Warner Losh wrote: : >>> On a lark, I just got a combo USB/Firewire external disk drive. I ran : >>> some crude benchmarks, and I was surprised by what I found. This is : >>> on a fairly stock -current kernel. : >>> : >>> Firewire does around 40MB/s, while USB 2.0 maxes out at about 12MB/s. : >>> This is with a simple dd command: : >> On my i386 notebook with USB 2.0 enclosure. : >> Linux: 31.5MB/s : >> FreeBSD: 27.5MB/s : >> : >> There's still room for improvement but numbers don't seem that bad. : >> : >> Maybe you should try knoppix or so to verify it's not the drive's fault. Other : >> than that I'd also guess it's an amd64 problem. : > : > It is not an AMD64 problem. I get the same numbers on my i386 latpop : > as I get on my amd64 laptop. Actually, I get WORSE numbers on the : > i386 laptop by about 20%. : > : > It isn't the drive's fault. Otherwise, firewire wouldn't get 40MB/s. : > The same drive, the same enclusure are used for both the USB and : > firewire tests. It is about as apples to apples as you can get. : > : > There's some serious performance issues in the usb stack. : > : > Warner : : : A few tidbits of information (may be useful, maybe not): : : - I've seen the firewire part of the enclosure be faster than the USB : part. The chips that run it are possibly different, so that shouldn't : be forgotten. I've had a few USB->flash adapters that got lousy : performance, but when I switched to a USB->SATA flash card reader, the : performance doubled. I'm now seeing on my FreeBSD desktop at work numbers that are in the 28MB/s range. I'll have to investigate things more closely... I can't imagine why FreeBSD/amd64 would be so much slower. : - For those testing using a file system - STOP! It's not a good test of : the throughput of the device, and depends on a lot of variables. dd or : diskinfo are decent generic tools, but in Windows you just can't use a : file system benchmark to compare. yes. : - If you read/write less than the drive cache, it should remove the : latency of the drive from the equation, right? True, but not relevant, I don't think. the speed of the disk is in excess of what either firewire or usb can do. Warner From owner-freebsd-current@FreeBSD.ORG Fri Jan 26 22:43:55 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 575A316A401 for ; Fri, 26 Jan 2007 22:43:55 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id B455B13C487 for ; Fri, 26 Jan 2007 22:43:54 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l0QMhqvY012618 for ; Sat, 27 Jan 2007 09:43:52 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l0QMhqow012617 for freebsd-current@freebsd.org; Sat, 27 Jan 2007 09:43:52 +1100 (EST) (envelope-from peter) Date: Sat, 27 Jan 2007 09:43:52 +1100 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20070126224352.GD927@turion.vk2pj.dyndns.org> References: <17850.11127.944124.276290@jerusalem.litteratus.org> <200701261733.l0QHXdY1078259@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: <200701261733.l0QHXdY1078259@lurza.secnetix.de> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jan 2007 22:43:55 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, 2007-Jan-26 18:33:39 +0100, Oliver Fromme wrote: >Robert Huff wrote: > > $DUMP_LEVEL -D $DUMPDATES_FILE -Lau -f=20 > >=20 > > gets me 2 +/- 0.2 mbytes/sec. > > Is this a reasonable value? (I.e. is dump the limiting > > factor?) Do I need to reconfigure something, or is my hardware just > > lame? I presume you are dumping an internal SCSI disk onto a USB disk. Dump is slow but shouldn't be that slow. Doing a dump of root, I get 10MB/s on one system and 15MB/s on another. Even my P-120 firewall gets 2.7MB/s and it is actually CPU limited, not disk limited. What do you get if you do the dump to /dev/null? >Historically the performance of dump(8) has always been >quite bad. It didn't matter in ancient times because >tape drives were slow back then, so dump(8) was not the >limiting factor. ;-) Tapes ceased to be the limiting factor long ago. There was a thread bemoaning the "Glacial speed of dump backups" on FreeBSD 4.6 in mid- 2002. I thought there was an earlier thread but I don't have my old mail archives to hand. There are two factors that make dump's performance abyssmal: 1) It physically re-reads the block containing the inode being dumped multiple times (to ensure that the file hasn't changed size) 2) It never reads more than the FS blocksize (8K or 16K). The first is not relevant for dumping snapshots and could probably be disabled. Caching (-C option) was introduced to attempt to alleviate the second but may or may not improve the overall throughput (it depends on the actual file layouts). Probably the overall design of dump needs a major re-think to try and improve performance - the introduction of snapshots removes the need to handle dynamic file- systems. >For that reason I try to avoid dump(8) when possible. >Maybe you should try to use tar, cpio or pax instead and >check if the performance is better. Note that dump/restore is the only tool that can correctly reproduce sparse files. tar, cpio and pax also have filename and file size restrictions. I don't think that cpio or pax support ACLs or file flags. --=20 Peter Jeremy --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFuoQo/opHv/APuIcRAngkAKC1AtPu8x/cKS0cbe9VL5NM4ssMPgCbBOC2 T+H7b/eoIRyQs4KdaqmET98= =FPuW -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 27 04:37:57 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C88416A400 for ; Sat, 27 Jan 2007 04:37:57 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.178]) by mx1.freebsd.org (Postfix) with ESMTP id 062CF13C4AC for ; Sat, 27 Jan 2007 04:37:56 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/8.12.11/smtpout08/MantshX 4.0) with ESMTP id l0R4bnmt025349; Fri, 26 Jan 2007 20:37:49 -0800 (PST) Received: from [192.168.1.2] (c-67-164-11-148.hsd1.ca.comcast.net [67.164.11.148]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id l0R4bloP019349 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 26 Jan 2007 20:37:48 -0800 (PST) In-Reply-To: <45B9AA00.3030906@delphij.net> References: <45B97535.5070900@delphij.net> <45B997ED.7000605@delphij.net> <45B99C6E.2030803@delphij.net> <1C63ACE4-DD1E-4FDB-A36B-F3D9650773EF@mac.com> <45B9AA00.3030906@delphij.net> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <989F100F-CE92-480C-8799-8EBD22997284@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Fri, 26 Jan 2007 20:36:27 -0800 To: LI Xin X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: FreeBSD Current Subject: Re: PowerPC port broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 04:37:57 -0000 On Jan 25, 2007, at 11:13 PM, LI Xin wrote: > Still same problem... Do we have a public reference PowerPC box for > committers to test changes? This is the only platform I have not > tested > my gzip related changes :-) No, not yet. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Sat Jan 27 17:21:22 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 58D8116A401 for ; Sat, 27 Jan 2007 17:21:22 +0000 (UTC) (envelope-from reichert@numachi.com) Received: from meisai.numachi.com (meisai.numachi.com [198.175.254.6]) by mx1.freebsd.org (Postfix) with SMTP id D92AA13C4AC for ; Sat, 27 Jan 2007 17:21:21 +0000 (UTC) (envelope-from reichert@numachi.com) Received: (qmail 80107 invoked from network); 27 Jan 2007 16:54:38 -0000 Received: from natto.numachi.com (198.175.254.216) by meisai.numachi.com with SMTP; 27 Jan 2007 16:54:38 -0000 Received: (qmail 91369 invoked by uid 1001); 27 Jan 2007 16:54:37 -0000 Date: Sat, 27 Jan 2007 11:54:37 -0500 From: Brian Reichert To: Peter Jeremy Message-ID: <20070127165437.GB41546@numachi.com> References: <17850.11127.944124.276290@jerusalem.litteratus.org> <200701261733.l0QHXdY1078259@lurza.secnetix.de> <20070126224352.GD927@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070126224352.GD927@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.5.10i Cc: freebsd-current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 17:21:22 -0000 On Sat, Jan 27, 2007 at 09:43:52AM +1100, Peter Jeremy wrote: > Note that dump/restore is the only tool that can correctly reproduce > sparse files. tar, cpio and pax also have filename and file size > restrictions. I don't think that cpio or pax support ACLs or file > flags. I thought 'star' handled sparse files and all the extra magic? Not that this is germaine to the topic at hand... > -- > Peter Jeremy -- Brian Reichert 55 Crystal Ave. #286 Daytime number: (603) 434-6842 Derry NH 03038-1725 USA BSD admin/developer at large From owner-freebsd-current@FreeBSD.ORG Sat Jan 27 21:42:39 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4134416A402 for ; Sat, 27 Jan 2007 21:42:39 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id C4C3513C48E for ; Sat, 27 Jan 2007 21:42:36 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l0RLgZ93016758; Sun, 28 Jan 2007 08:42:35 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l0RLgYtU016757; Sun, 28 Jan 2007 08:42:34 +1100 (EST) (envelope-from peter) Date: Sun, 28 Jan 2007 08:42:34 +1100 From: Peter Jeremy To: Brian Reichert Message-ID: <20070127214234.GO927@turion.vk2pj.dyndns.org> References: <17850.11127.944124.276290@jerusalem.litteratus.org> <200701261733.l0QHXdY1078259@lurza.secnetix.de> <20070126224352.GD927@turion.vk2pj.dyndns.org> <20070127165437.GB41546@numachi.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ULyIDA2m8JTe+TiX" Content-Disposition: inline In-Reply-To: <20070127165437.GB41546@numachi.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 21:42:39 -0000 --ULyIDA2m8JTe+TiX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, 2007-Jan-27 11:54:37 -0500, Brian Reichert wrote: >On Sat, Jan 27, 2007 at 09:43:52AM +1100, Peter Jeremy wrote: >> Note that dump/restore is the only tool that can correctly reproduce >> sparse files. tar, cpio and pax also have filename and file size >> restrictions. I don't think that cpio or pax support ACLs or file >> flags. > >I thought 'star' handled sparse files and all the extra magic? Not >that this is germaine to the topic at hand... You can detect a sparse file by comparing the length of the file with the number of allocated blocks. You can't determine whether a specific block is all NULLs or not allocated without either bypassing the filesystem (which dump does) or using a syscall to retrieve a bitmap of allocated blocks (which FreeBSD doesn't have). =20 --=20 Peter Jeremy --ULyIDA2m8JTe+TiX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFu8dK/opHv/APuIcRApE1AJ9BnKXriCb87SVQ+1x7AL/pcyAo1ACfXI/f FTMOLQaDVdbdfZQU2xKNMFo= =pUnu -----END PGP SIGNATURE----- --ULyIDA2m8JTe+TiX-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 27 23:03:44 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 966A016A400 for ; Sat, 27 Jan 2007 23:03:44 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from mail.bitblocks.com (mail.bitblocks.com [64.142.15.60]) by mx1.freebsd.org (Postfix) with ESMTP id 787F613C48C for ; Sat, 27 Jan 2007 23:03:44 +0000 (UTC) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost.bitblocks.com [127.0.0.1]) by mail.bitblocks.com (Postfix) with ESMTP id 6CFCE5B32; Sat, 27 Jan 2007 14:41:20 -0800 (PST) To: Peter Jeremy In-reply-to: Your message of "Sun, 28 Jan 2007 08:42:34 +1100." <20070127214234.GO927@turion.vk2pj.dyndns.org> Date: Sat, 27 Jan 2007 14:41:20 -0800 From: Bakul Shah Message-Id: <20070127224120.6CFCE5B32@mail.bitblocks.com> Cc: freebsd-current@freebsd.org Subject: Re: Interesting speed benchmarks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 23:03:44 -0000 Peter Jeremy wrote: > On Sat, 2007-Jan-27 11:54:37 -0500, Brian Reichert wrote: > >On Sat, Jan 27, 2007 at 09:43:52AM +1100, Peter Jeremy wrote: > >> Note that dump/restore is the only tool that can correctly reproduce > >> sparse files. tar, cpio and pax also have filename and file size > >> restrictions. I don't think that cpio or pax support ACLs or file > >> flags. > > > >I thought 'star' handled sparse files and all the extra magic? Not > >that this is germaine to the topic at hand... > > You can detect a sparse file by comparing the length of the file > with the number of allocated blocks. You can't determine whether a > specific block is all NULLs or not allocated without either bypassing > the filesystem (which dump does) or using a syscall to retrieve a > bitmap of allocated blocks (which FreeBSD doesn't have). =20 Both rsync and gtar create a sparse file by not writing blocks of zeroes given -S option. You are correct that there is no special help for reading sparse files. I recall pjd@freebsd.org saying he plans to implement solaris specific extensions to lseek() in zfs (lseek's whence arg can take SEEK_HOLE/SEEK_DATA values, to seek to next null/nonnull block). It would be nice if this was done for all filesystems. Returning a bitmap is far more work than adding SEEK_{HOLE,DATA}. For backups I use vbackup & venti from plan9ports. Like dump vbackup knows ufs1 & ufs2 structure to walk the filesytem and write only live data to venti (a SHA1-addressed block storage server) so it correctly handles sparse files. A full backup is faster than dump. All subseqeuent backups are incremental and generally run very fast (for example I can backup a UFS2 system at about 10MB/s to a USB2 ATA disk. dd shows write speed of 23MB/s). You can get at backed up data in a number of different ways: 1) vcat (makes an identical disk image given a snapshot's `score') 2) vftp (you can browse/copy files individually) 3) vnfs + vmount (make one or more snapshots accessible in filesystem namespace) AFAIK flags, attributes & ACLs are maintained but are only available if you use vcat. See http://swtch.com/plan9ports From owner-freebsd-current@FreeBSD.ORG Sat Jan 27 23:49:24 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D7C5916A537 for ; Sat, 27 Jan 2007 23:49:24 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2B1C913C4C3 for ; Sat, 27 Jan 2007 23:49:20 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l0RNA824004223; Sat, 27 Jan 2007 15:10:08 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <45BBDBCF.3090901@freebsd.org> Date: Sat, 27 Jan 2007 15:10:07 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Reichert References: <17850.11127.944124.276290@jerusalem.litteratus.org> <200701261733.l0QHXdY1078259@lurza.secnetix.de> <20070126224352.GD927@turion.vk2pj.dyndns.org> <20070127165437.GB41546@numachi.com> In-Reply-To: <20070127165437.GB41546@numachi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , freebsd-current@freebsd.org Subject: dump/tar/star/etc (was Re: Interesting speed benchmarks) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jan 2007 23:49:25 -0000 Brian Reichert wrote: >On Sat, Jan 27, 2007 at 09:43:52AM +1100, Peter Jeremy wrote: > > >> ... dump/restore is the only tool ... tar, cpio and pax also have ... restrictions. >> >> > >I thought 'star' handled sparse files and all the extra magic? Not >that this is germaine to the topic at hand... > > The full picture is a little complicated. No one tool gets everything exactly right: For sparse file support: * dump fully handles them. * gnutar and star use some guesswork to archive them into "gnutar format" archives; neither can guarantee that the final block layout matches the original * gnutar, star, and bsdtar can all restore sparse files from "gnutar format" archives For ACLs and file flags: * I'm not sure about dump; I believe it handles file flags but not ACLs * star and bsdtar fully support both using "pax extended" tar archives * gtar, cpio, and pax do not support them For long filenames and large files: * dump should fully support both up to the limits of the filesystem * star, bsdtar, and gnutar all support large files (64-bit lengths) using extended tar archives * star and gnutar support filenames up to 1k (longest name supported by kernel system calls) * bsdtar supports filenames up to 1meg, though with some limits (restoring dirs with names over 1k gets the permissions wrong sometimes) * cpio and pax are more limited I eventually want to replace cpio and pax with versions built on top of libarchive (as bsdtar is), which will alleviate some of these issues. (Though some are particular to the archive formats; there is no standard cpio extension for long filenames or large files.) Tim Kientzle