From owner-freebsd-current@FreeBSD.ORG Thu Oct 30 08:51:21 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 7210E16A4CF for ; Thu, 30 Oct 2003 08:51:21 -0800 (PST) Received: from prg.traveller.cz (prg.traveller.cz [193.85.2.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 902BB43FAF for ; Thu, 30 Oct 2003 08:51:17 -0800 (PST) (envelope-from mime@traveller.cz) Received: from prg.traveller.cz (localhost [127.0.0.1]) h9UGpBjZ073969; Thu, 30 Oct 2003 17:51:11 +0100 (CET) Received: from localhost (mime@localhost)h9UGpBHp073966; Thu, 30 Oct 2003 17:51:11 +0100 (CET) Date: Thu, 30 Oct 2003 17:51:11 +0100 (CET) From: Michal Mertl To: Sam Leffler In-Reply-To: <200310300804.58296.sam@errno.com> Message-ID: <20031030174122.F8510@prg.traveller.cz> References: <20031029183808.M99053@prg.traveller.cz> <200310300804.58296.sam@errno.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 16:51:21 -0000 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. I can repeat the whole test once again to make sure I didn't overlooked anything. It will take some time because I had to put one of the servers into production. -- Michal Mertl