From: David Newman <dnewman@networktest.com>
To: unlisted-recipients:; (no To-header on input)
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] drivers/net/tg3.c: Raise Jumbo Frame MTU to 9216?
Date: Wed, 15 Sep 2010 12:45:40 -0700 [thread overview]
Message-ID: <4C912264.5040203@networktest.com> (raw)
In-Reply-To: <1284578095.10223.27.camel@Joe-Laptop>
On 9/15/10 12:14 PM, Joe Perches wrote:
> On Wed, 2010-09-15 at 10:57 -0700, Michael Chan wrote:
>> On Wed, 2010-09-15 at 10:41 -0700, Joe Perches wrote:
>>> The TG3 apparently supports 9K frame sizes.
>>> http://www.broadcom.com/collateral/pb/5704C-PB05-R.pdf
>>> Is exactly 9000 a hardware limit?
>>> Should the jumbo frame MTU be raised to 9216 or 9216
>>> less the size of MAC, VLAN, IP and TCP headers?
>> 9000 has been the de facto standard, has it been changed recently?
>
> I know of a performance lab that's trying to use 9216 as a "standard"
> jumbo frame length.
>
> Unrelated to the performance lab:
> http://www.uoregon.edu/~joe/jumbo-clean-gear.html
> 9216 seems popular, especially with Cisco gear.
> Contrary to that link, the Cisco 3750 does work with 9216 length
> jumbo frames.
>
>> Anyway, we've never done any testing on 9216.
9216 is commonly used in Ethernet switch testing [1]. Most data center
switches support it, including some built around Broadcom silicon (e.g.,
Dell PowerConnect 8024, Extreme Summit X650).
There is no IEEE standard for jumbo lengths. The IETF's RFC 5180
recommends 9216 for switch performance testing.
Although 5180 specs this length as a SHOULD and not a MUST, its use does
represent widespread industry practice in switch performance benchmarking.
Regards,
David Newman
Network Test
[1] Length from first byte of DA to last byte of CRC absent any VLAN
header(s).
prev parent reply other threads:[~2010-09-15 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 17:41 [RFC PATCH] drivers/net/tg3.c: Raise Jumbo Frame MTU to 9216? Joe Perches
2010-09-15 17:57 ` Michael Chan
2010-09-15 19:14 ` Joe Perches
2010-09-15 19:31 ` Ben Hutchings
2010-09-15 19:45 ` David Newman [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=4C912264.5040203@networktest.com \
--to=dnewman@networktest.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).