netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: rgetz@blackfin.uclinux.org, netdev@vger.kernel.org
Subject: Re: Jumbo frame question...
Date: Fri, 24 Jul 2009 09:39:43 -0700	[thread overview]
Message-ID: <4A69E3CF.1040805@hp.com> (raw)
In-Reply-To: <20090724.093243.201296391.davem@davemloft.net>

David Miller wrote:
> 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..

In so far as there is no de jure spec for Jumbo Frames, it is rather difficult 
to have 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.

Not a case of too much rope?  Given that (IIRC) Jumbo Frame was not introduced 
in Ethernet NICs until Gigabit came along (eg Alteon), the chances a (legacy) 
100 Mbit/s network would have JF-capable NICs is epsilon.

rick jones

> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2009-07-24 16:39 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
2009-07-24 16:39   ` Rick Jones [this message]
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=4A69E3CF.1040805@hp.com \
    --to=rick.jones2@hp.com \
    --cc=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).