From: Michael Richardson <mcr@sandelman.ca>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Ani Sinha <ani@aristanetworks.com>,
Jiri Pirko <jpirko@redhat.com>,
netdev@vger.kernel.org, edumazet <edumazet@google.com>,
tcpdump-workers@lists.tcpdump.org, dborkman <dborkman@redhat.com>
Subject: Re: [tcpdump-workers] [PATCH net 1/2] net: dev_queue_xmit_nit: fix skb->vlan_tci field value
Date: Thu, 10 Jan 2013 20:47:49 -0500 [thread overview]
Message-ID: <32117.1357868869@sandelman.ca> (raw)
In-Reply-To: <1357761063.27446.60.camel@edumazet-glaptop>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
>>>>> "Eric" == Eric Dumazet <eric.dumazet@gmail.com> writes:
Eric> On Wed, 2013-01-09 at 11:27 -0800, Ani Sinha wrote:
>> This is wrong. Accelerated or not, the kernel code was organized to
>> have the tags in the packet aux data. So I think this is how user land
>> should be coded as well.
Eric> You have your opinion, thats good.
Eric> My opinion as a kernel developer is that the network tap is here to have
Eric> a copy of the exact frame given to the _device_.
Good: as someone who spends lots of time with tcpdump doing both network
and protocol diagnostics, it's really important to see exactly there.
If that means turning off some hardware offload in order to get the
intact 1p header, then that may be fine for many situations.
(At 10G, on a live router... well...)
The problem is that now we need to know, on a per device basis (based
upon the current configuration) if the VLAN tag was removed by the
hardware or not. It's not enough to try with vlan tag and not.
Eric> If you want other taps, and catch frames before/after various netfilter
Eric> hooks, segmentations, vlan accel, tunnels, or before GRO layer, thats a
Eric> totally different request.
Yes!!!! We need all of these tap points too...
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: Type: application/pgp-signature, Size: 307 bytes --]
next prev parent reply other threads:[~2013-01-11 1:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 5:15 [PATCH net 1/2] net: dev_queue_xmit_nit: fix skb->vlan_tci field value Paul Pearce
2013-01-09 6:06 ` Ani Sinha
2013-01-09 6:27 ` Eric Dumazet
2013-01-09 6:34 ` Ani Sinha
2013-01-09 19:27 ` Ani Sinha
2013-01-09 19:51 ` Eric Dumazet
2013-01-09 20:01 ` Ani Sinha
2013-01-09 20:06 ` Ani Sinha
2013-01-11 1:47 ` Michael Richardson [this message]
2013-01-11 2:37 ` [tcpdump-workers] " Paul Pearce
2013-01-11 8:46 ` Daniel Borkmann
2013-02-15 8:17 ` Eric W. Biederman
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=32117.1357868869@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=ani@aristanetworks.com \
--cc=dborkman@redhat.com \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=tcpdump-workers@lists.tcpdump.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).