From: Eric Dumazet <eric.dumazet@gmail.com>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: Rick Jones <rick.jones2@hp.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: Jumbo frame question...
Date: Fri, 24 Jul 2009 21:13:41 +0200 [thread overview]
Message-ID: <4A6A07E5.9080705@gmail.com> (raw)
In-Reply-To: <200907241421.55986.rgetz@blackfin.uclinux.org>
Robin Getz a écrit :
> On Fri 24 Jul 2009 12:39, Rick Jones pondered:
>> 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 :).
>
> The spec I was talking about was the MTU...
>
> rgetz@pinky:~> /sbin/ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:11:11:B0:A5:D4
> inet addr:192.168.0.10 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::211:11ff:feb0:a5d4/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:45978 errors:5 dropped:0 overruns:0 frame:0
> TX packets:44536 errors:0 dropped:0 overruns:0 carrier:0
> collisions:3193 txqueuelen:1000
> RX bytes:11583575 (11.0 Mb) TX bytes:20025122 (19.0 Mb)
> Interrupt:16
>
>
> My MTU is 1500, but when tftp requests a block size of over that - the host
> does not fragment it (like I thought it should).
Which broken driver would do this me asking, and how can you be sure a jumbo frame was ever sent ?
I guess your tcpdump is fooled by gso settings... Did you tried
# ethtool -K eth0 gso off
next prev parent reply other threads:[~2009-07-24 19:15 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
2009-07-24 18:21 ` Robin Getz
2009-07-24 18:44 ` Rick Jones
2009-07-24 19:13 ` Eric Dumazet [this message]
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=4A6A07E5.9080705@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=rick.jones2@hp.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;
as well as URLs for NNTP newsgroup(s).