From: Shan Wei <shanwei@cn.fujitsu.com>
To: Herbert Xu <herbert@gondor.hengli.com.au>,
Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: question about UFO behavior for bridge device
Date: Sat, 14 May 2011 17:54:06 +0800 [thread overview]
Message-ID: <4DCE513E.9040002@cn.fujitsu.com> (raw)
In-Reply-To: <20110513143627.GA29054@gondor.apana.org.au>
Herbert Xu wrote, at 05/13/2011 10:36 PM:
> On Fri, May 13, 2011 at 02:06:52PM +0100, Ben Hutchings wrote:
>>
>>> 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?
>>
>> I assume that packet capturing is handled earlier in the transmit path.
>
> Yes it is. It's the same with TSO.
Be cheated by tcpdump. :-(
dev_queue_xmit_nit(skb, dev) which dumps packet to user is called before handling GSO segments.
Thanks very much.
--
Best Regards
-----
Shan Wei
prev parent reply other threads:[~2011-05-14 9:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 9:21 question about UFO behavior for bridge device Shan Wei
2011-05-13 13:06 ` Ben Hutchings
2011-05-13 14:36 ` Herbert Xu
2011-05-14 9:54 ` Shan Wei [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=4DCE513E.9040002@cn.fujitsu.com \
--to=shanwei@cn.fujitsu.com \
--cc=bhutchings@solarflare.com \
--cc=herbert@gondor.hengli.com.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).