From: Daniel Borkmann <daniel@iogearbox.net>
To: tom.barbette@ulg.ac.be
Cc: Joe Stringer <joe@ovn.org>,
xdp-newbies@vger.kernel.org, john.fastabend@gmail.com
Subject: Re: XDP for Kernel by-pass?
Date: Fri, 14 Jul 2017 11:44:27 +0200 [thread overview]
Message-ID: <5968927B.2010108@iogearbox.net> (raw)
In-Reply-To: <1702257840.29879018.1500021982749.JavaMail.zimbra@ulg.ac.be>
On 07/14/2017 10:46 AM, tom.barbette@ulg.ac.be wrote:
[...]
> Netmap hooks exactly where XDP does. We would just need a little shared-memory module that hooks in XDP and give all the raw packets to a userspace program.
There is work in progress for a faster AF_PACKET interface for RX/TX, which would
be a much better fit given AF_PACKET's purpose. Some RFC patches have been posted
here [1][2] some time ago.
[1] http://patchwork.ozlabs.org/patch/720937/
[2] http://patchwork.ozlabs.org/patch/720936/
> Tom
prev parent reply other threads:[~2017-07-14 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 19:34 XDP for Kernel by-pass? tom.barbette
2017-07-13 20:40 ` David Miller
2017-07-13 20:44 ` Daniel Borkmann
2017-07-13 21:07 ` Joe Stringer
2017-07-14 8:46 ` tom.barbette
2017-07-14 9:44 ` Daniel Borkmann [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=5968927B.2010108@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=joe@ovn.org \
--cc=john.fastabend@gmail.com \
--cc=tom.barbette@ulg.ac.be \
--cc=xdp-newbies@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 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.