All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <dborkman@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: nvbolhuis@aimvalley.nl, netdev@vger.kernel.org,
	linux-net@vger.kernel.org
Subject: Re: i386 vs x86_64 struct tpacket_hdr layout
Date: Fri, 20 Dec 2013 19:45:12 +0100	[thread overview]
Message-ID: <52B49038.3070307@redhat.com> (raw)
In-Reply-To: <20131220.133854.672157982782686878.davem@davemloft.net>

On 12/20/2013 07:38 PM, David Miller wrote:
> From: Norbert van Bolhuis <nvbolhuis@aimvalley.nl>
> Date: Fri, 20 Dec 2013 14:30:06 +0100
>
>>
>> I'm compiling my 32bit application with -m32 on a x86_64
>> system/kernel.
>>
>> Things aren't working because for my application tp_len is at offset 4
>> but for the kernel it is at offset 8.
>>
>> struct tpacket_hdr {
>>          unsigned long   tp_status;
>>          unsigned int    tp_len;
>>          unsigned int    tp_snaplen;
>>          unsigned short  tp_mac;
>>          unsigned short  tp_net;
>>          unsigned int    tp_sec;
>>          unsigned int    tp_usec;
>> };
>>
>> How is this suppose to work ?
>
> This is why you should use tpacket layout v2 or v3, rather than v1,
> they fix these issues.

Norbert, please also read Documentation/networking/packet_mmap.txt

Thanks !

  reply	other threads:[~2013-12-20 18:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20 13:30 i386 vs x86_64 struct tpacket_hdr layout Norbert van Bolhuis
2013-12-20 18:38 ` David Miller
2013-12-20 18:45   ` Daniel Borkmann [this message]
2013-12-20 21:22     ` Norbert van Bolhuis
2014-01-06 22:58 ` single process receives own frames due to PACKET_MMAP Norbert van Bolhuis
2014-01-07  9:32   ` Daniel Borkmann
2014-01-07 10:06     ` Jesper Dangaard Brouer
2014-01-07 13:16       ` Norbert van Bolhuis
2014-01-07 13:47         ` Daniel Borkmann
2014-01-07 14:09         ` Jesper Dangaard Brouer
2014-01-07 15:16           ` Norbert van Bolhuis
2014-01-07 15:26             ` Daniel Borkmann
2014-01-07 15:46               ` Norbert van Bolhuis
2014-01-07 15:57                 ` Daniel Borkmann
2014-01-08 14:18                   ` Norbert van Bolhuis
2014-01-08 14:24                     ` Daniel Borkmann
2014-01-08 14:36                       ` Norbert van Bolhuis

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=52B49038.3070307@redhat.com \
    --to=dborkman@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nvbolhuis@aimvalley.nl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.