From: David Miller <davem@davemloft.net>
To: rgetz@blackfin.uclinux.org
Cc: netdev@vger.kernel.org
Subject: Re: Jumbo frame question...
Date: Fri, 24 Jul 2009 09:32:43 -0700 (PDT) [thread overview]
Message-ID: <20090724.093243.201296391.davem@davemloft.net> (raw)
In-Reply-To: <200907241141.55097.rgetz@blackfin.uclinux.org>
From: Robin Getz <rgetz@blackfin.uclinux.org>
Date: Fri, 24 Jul 2009 11:41:55 -0400
> Should a gigabit card, configured as 100, be sending jumbo UDP frames?
>
> My understanding, is no - this is a spec violation..
There is nothing wrong with supporting jumbo frames
when the speed is lower than 1GB.
If you configure the MTU to be jumbo size, it should
be no surprise to you that this is what gets used.
next prev parent reply other threads:[~2009-07-24 16:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 15:41 Jumbo frame question Robin Getz
2009-07-24 16:32 ` David Miller [this message]
2009-07-24 16:39 ` Rick Jones
2009-07-24 18:21 ` Robin Getz
2009-07-24 18:44 ` Rick Jones
2009-07-24 19:13 ` Eric Dumazet
2009-07-25 12:34 ` Robin Getz
2009-07-25 14:25 ` Eric Dumazet
2009-07-24 18:45 ` Lennart Sorensen
2009-07-25 3:28 ` Herbert Xu
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=20090724.093243.201296391.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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).