From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Donald Becker <becker@scyld.com>
Cc: Matti Aarnio <matti.aarnio@zmailer.org>,
Robert PipCA <robertpipca@yahoo.com>,
vortex@scyld.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [vortex] Re: MTU discovery
Date: Tue, 11 Jun 2002 20:57:13 -0400 [thread overview]
Message-ID: <3D069C69.1090003@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206111523050.1688-100000@presario>
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
> <rishis at CLEMSON.EDU> 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
prev parent reply other threads:[~2002-06-12 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 7:45 MTU discovery Robert PipCA
2002-06-10 8:05 ` Matti Aarnio
2002-06-10 8:23 ` Robert PipCA
2002-06-10 9:50 ` Olivier Galibert
2002-06-10 21:45 ` Bill Davidsen
2002-06-10 22:02 ` Joel Jaeggli
2002-06-11 3:31 ` BALBIR SINGH
2002-06-11 3:46 ` Joel Jaeggli
2002-06-11 19:27 ` [vortex] " Donald Becker
2002-06-12 0:57 ` Jeff Garzik [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D069C69.1090003@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=becker@scyld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=robertpipca@yahoo.com \
--cc=vortex@scyld.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox