From: Jean-Mickael Guerin <jmg@6wind.com>
To: Magnus Karlsson <magnus.karlsson@intel.com>
Cc: bjorn.topel@intel.com, ast@kernel.org, daniel@iogearbox.net,
netdev@vger.kernel.org, jakub.kicinski@netronome.com,
bjorn.topel@gmail.com, qi.z.zhang@intel.com, brouer@redhat.com,
xiaolong.ye@intel.com
Subject: Re: [PATCH bpf-next v4 0/2] libbpf: adding AF_XDP support
Date: Mon, 11 Feb 2019 07:33:33 +0100 [thread overview]
Message-ID: <CAP2kokD9aSryMBDjt+ip=1NFronXrMfY59b6DauTT59kWHLwcw@mail.gmail.com> (raw)
In-Reply-To: <1549631126-29067-1-git-send-email-magnus.karlsson@intel.com>
Hi Magnus,
> * In a future release, I am planning on adding a higher level data
> plane interface too. This will be based around recvmsg and sendmsg
> with the use of struct iovec for batching, without the user having
> to know anything about the underlying four rings of an AF_XDP
> socket. There will be one semantic difference though from the
> standard recvmsg and that is that the kernel will fill in the iovecs
> instead of the application. But the rest should be the same as the
> libc versions so that application writers feel at home.
You might consider recvmmsg() and sendmmsg() (bulk of multi segments packets?)
Jean-Mickael
next prev parent reply other threads:[~2019-02-11 6:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 13:05 [PATCH bpf-next v4 0/2] libbpf: adding AF_XDP support Magnus Karlsson
2019-02-08 13:05 ` [PATCH bpf-next v4 1/2] libbpf: add support for using AF_XDP sockets Magnus Karlsson
2019-02-15 16:37 ` Daniel Borkmann
2019-02-18 8:59 ` Magnus Karlsson
2019-02-18 11:21 ` Maciej Fijalkowski
2019-02-08 13:05 ` [PATCH bpf-next v4 2/2] samples/bpf: convert xdpsock to use libbpf for AF_XDP access Magnus Karlsson
2019-02-11 6:33 ` Jean-Mickael Guerin [this message]
2019-02-11 7:52 ` [PATCH bpf-next v4 0/2] libbpf: adding AF_XDP support Magnus Karlsson
2019-02-11 19:48 ` Jonathan Lemon
2019-02-13 11:32 ` Magnus Karlsson
2019-02-13 11:55 ` Jesper Dangaard Brouer
2019-02-15 16:20 ` Daniel Borkmann
2019-02-18 8:20 ` Magnus Karlsson
2019-02-18 9:38 ` Daniel Borkmann
2019-02-18 10:09 ` Magnus Karlsson
2019-02-13 20:49 ` Jonathan Lemon
2019-02-14 8:25 ` Magnus Karlsson
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='CAP2kokD9aSryMBDjt+ip=1NFronXrMfY59b6DauTT59kWHLwcw@mail.gmail.com' \
--to=jmg@6wind.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=qi.z.zhang@intel.com \
--cc=xiaolong.ye@intel.com \
/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).