Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 11 Jun 2002 21:00:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 11 Jun 2002 21:00:48 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:1547 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id ; Tue, 11 Jun 2002 21:00:48 -0400 Message-ID: <3D069C69.1090003@mandrakesoft.com> Date: Tue, 11 Jun 2002 20:57:13 -0400 From: Jeff Garzik Organization: MandrakeSoft User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/00200205 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Donald Becker CC: Matti Aarnio , Robert PipCA , vortex@scyld.com, Linux Kernel Mailing List Subject: Re: [vortex] Re: MTU discovery In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Donald Becker wrote: > A 16 bit register.. 64KB packets. There are various issues with using > large packet sizes. There is no driver that has been verified with > jumbo frames. I have been throwing driver versions at Rishi Srivatsavai > trying to sort out the issues. You might notice > the changes in 0.99W, although they don't handle the FIFO limit issues. With the VLAN stuff that suddenly appeared, I did some large packet testing... I would typically cap the MTU limit at just under the FIFO size, since it often requires special handling doing frames > FIFO size. I do not look forward to re-verifying the 2.4 tulip driver across all those chipsets, to make sure my large packet code [which is not yet in the kernel] works. :) Jeff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/