From: Norbert van Bolhuis <nvbolhuis@aimvalley•nl>
To: Daniel Borkmann <dborkman@redhat•com>
Cc: Jesper Dangaard Brouer <brouer@redhat•com>,
netdev@vger•kernel.org, David Miller <davem@davemloft•net>,
uaca@alumni•uv.es
Subject: Re: single process receives own frames due to PACKET_MMAP
Date: Wed, 08 Jan 2014 15:36:48 +0100 [thread overview]
Message-ID: <52CD6280.3080300@aimvalley.nl> (raw)
In-Reply-To: <52CD5FAB.60801@redhat.com>
On 01/08/14 15:24, Daniel Borkmann wrote:
> On 01/08/2014 03:18 PM, Norbert van Bolhuis wrote:
>
>>>> Is there a way to use one PF_PACKET socket for both TX and RX and use PACKET_MMAP ?
>>>
>>> Yep:
>>>
>>> http://thread.gmane.org/gmane.linux.network/269129/focus=269188
>>>
>>> Feel free to make a patch and add this to Documentation/networking/packet_mmap.txt
>>> I think could be useful for others as well.
>>
>>
>> Good, it all works fine now, though performance is still not as good as I'd hoped.
>
> Does your use case allow for TPACKET_V3 or for using fanout ?
>
no, unfortunately not.
Though currently our performance is limited by application/system stuff, so
at the moment it doesn't really matter.
--
Norbert
prev parent reply other threads:[~2014-01-08 14:38 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
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 [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=52CD6280.3080300@aimvalley.nl \
--to=nvbolhuis@aimvalley$(echo .)nl \
--cc=brouer@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dborkman@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=uaca@alumni$(echo .)uv.es \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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