From owner-freebsd-current@FreeBSD.ORG Thu Oct 30 11:50:39 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55BF716A4CE for ; Thu, 30 Oct 2003 11:50:39 -0800 (PST) Received: from www.ambrisko.com (adsl-64-174-51-42.dsl.snfc21.pacbell.net [64.174.51.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B50F43F93 for ; Thu, 30 Oct 2003 11:50:38 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.8p2/8.12.8) with ESMTP id h9UJoUDl005912; Thu, 30 Oct 2003 11:50:30 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.8p2/8.12.8/Submit) id h9UJoTuR005911; Thu, 30 Oct 2003 11:50:29 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200310301950.h9UJoTuR005911@ambrisko.com> In-Reply-To: <20031030174122.F8510@prg.traveller.cz> To: Michal Mertl Date: Thu, 30 Oct 2003 11:50:29 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: Sam Leffler cc: current@freebsd.org Subject: Re: jumbograms (& em) & nfs a no go X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 30 Oct 2003 19:50:39 -0000 Michal Mertl writes: | On Thu, 30 Oct 2003, Sam Leffler wrote: | | > On Thursday 30 October 2003 04:46 am, Michal Mertl wrote: | > > I wanted to test gigabit network performance and found out that current | > > (from 5.0 to up to date -current) doesn't fully work with jumbograms (MTU | > > set to 6000), Intel adapters and nfs (both UDP and TCP). | > > | > > I checked that the same thing works with 4.9. | > > | > > I then left one computer at 4.9 and upgraded the other to 5.0. When I | > > mount a partition from 5.0 machine I found out, that copying reliably | > > works only from 5.0 to 4.9. The other way around I see messages 'em0: | > > discard oversize frame (ether type 800 flags 3 len 67582 > max 6014)' on | > > 5.0 and the copying stalls. On 4.9 machine I later see 'nfs server | > > 10.0.0.2:/usr: not responding'. The interface is stuck for some time - can | > > be revived by changing mtu back to 1500 and down/up sequence. | > | > I've ran many jumbogram tests of machines connected with a cross-over cable | > and em devices at each end. If you've got a swtch in the middle make sure it | > does the right thing. | | I also used exclusively crossover cable. The same configuration worked | with 4.9. The problem appears only with NFS. You might want to try this patch: Index: if_em.c =================================================================== RCS file: /cvs/src/sys/dev/em/if_em.c,v retrieving revision 1.32 diff -c -r1.32 if_em.c *** if_em.c 15 Oct 2003 05:34:41 -0000 1.32 --- if_em.c 30 Oct 2003 19:39:49 -0000 *************** *** 2454,2460 **** BUS_SPACE_MAXADDR, /* highaddr */ NULL, NULL, /* filter, filterarg */ MCLBYTES, /* maxsize */ ! 1, /* nsegments */ MCLBYTES, /* maxsegsize */ BUS_DMA_ALLOCNOW, /* flags */ NULL, /* lockfunc */ --- 2454,2460 ---- BUS_SPACE_MAXADDR, /* highaddr */ NULL, NULL, /* filter, filterarg */ MCLBYTES, /* maxsize */ ! 2, /* nsegments */ MCLBYTES, /* maxsegsize */ BUS_DMA_ALLOCNOW, /* flags */ NULL, /* lockfunc */ There was a few bugs in the system before in that there was insufficient error check in the bus_dma stuff. The issue was that HW was writing more then was the allocated due to (nsegments=1). This isn't the right fix but might help point to the issue. I don't have access to the HW to test it out anymore. Doug A.