From: Shan Wei <shanwei@cn.fujitsu.com>
To: 单卫 <shanwei@cn.fujitsu.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Ben Hutchings" <bhutchings@solarflare.com>,
netdev <netdev@vger.kernel.org>
Subject: question about UFO behavior for bridge device
Date: Fri, 13 May 2011 17:21:07 +0800 [thread overview]
Message-ID: <4DCCF803.5020805@cn.fujitsu.com> (raw)
UDP protocol creates a big packet(skb) in which the data length is greater than MTU.
If device(eth0, lo) does not supports UFO, This big skb will be fragmented to
many fragments in IP protocol, and fragments are sent one by one by device.
But, if device(eth0, lo) supports UFO, IP protocol don't fragment it, and
device directly sends it out.
For bridge device which enable UFO, and Ethernet device(eth0) which not
support UFO, IP protocol also doesn't fragment it, and bridge forwards original
skb to eth0. For this UFO disabled eth0, kernel needs to perform segmentation
on so big skb in dev_gso_segment(), and link segmented skbs to next field
of original skb. Then device sends segmented skbs out, but not original skb.
But, actually, i saw original big skb in eth0's tcpdump file, but not segmented skbs.
The behavior is right or what we want?
Is there anything missed about my analysis?
--
Best Regards
-----
Shan Wei
next reply other threads:[~2011-05-13 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 9:21 Shan Wei [this message]
2011-05-13 13:06 ` question about UFO behavior for bridge device Ben Hutchings
2011-05-13 14:36 ` Herbert Xu
2011-05-14 9:54 ` Shan Wei
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=4DCCF803.5020805@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=bhutchings@solarflare.com \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@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).