From: chetan loke <loke.chetan@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 af-packet 1/2] Enhance af-packet to provide (near zero)lossless packet capture functionality.
Date: Mon, 18 Jul 2011 08:49:30 -0400 [thread overview]
Message-ID: <CAAsGZS5b9X5HW=_JjfahbXpi9f4H5iYGeY9-+wBjP+=c-MDj4w@mail.gmail.com> (raw)
In-Reply-To: <1310971114.2509.25.camel@edumazet-laptop>
On Mon, Jul 18, 2011 at 2:38 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Le dimanche 17 juillet 2011 à 23:26 -0400, Chetan Loke a écrit :
>> Signed-off-by: Chetan Loke <loke.chetan@gmail.com>
>> ---
>> include/linux/if_packet.h | 125 +++++++++++++++++++++++++++++++++++++++++++++
>> 1 files changed, 125 insertions(+), 0 deletions(-)
>
>>
>> +struct tpacket3_hdr {
>> + __u32 tp_status;
>> + __u32 tp_next_offset;
>> + __u32 tp_len;
>> + __u32 tp_snaplen;
>> + __u16 tp_mac;
>> + __u16 tp_net;
>> + __u32 tp_sec;
>> + __u32 tp_nsec;
>> + __u32 tp_rxhash;
>> + __u16 tp_vlan_tci;
>> + __u16 tp_padding;
>> + __u32 tp_next_offset;
>> +};
>
> Srange, I see tp_next_offset twice in tpacket3_hdr ?
Sorry, I was trying some last minute fancy prefetch changes. So I
bubbled up the field on my test box but somehow missed the cleanup on
the dev-box.
Will wait for a day to gather some more comments and then re-send the patch.
Chetan Loke
next prev parent reply other threads:[~2011-07-18 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 3:26 [PATCH net-next v3 af-packet 0/2] Enhance af-packet to provide (near zero)lossless packet capture functionality Chetan Loke
2011-07-18 3:26 ` [PATCH net-next v3 af-packet 1/2] " Chetan Loke
2011-07-18 6:38 ` Eric Dumazet
2011-07-18 12:49 ` chetan loke [this message]
2011-07-18 16:56 ` David Miller
2011-07-18 3:26 ` [PATCH net-next v3 af-packet 2/2] " Chetan Loke
2011-07-18 3:46 ` Joe Perches
2011-07-18 14:55 ` chetan loke
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='CAAsGZS5b9X5HW=_JjfahbXpi9f4H5iYGeY9-+wBjP+=c-MDj4w@mail.gmail.com' \
--to=loke.chetan@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).