[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJ8uoz2J0HPfbzZQDsycRGZLnTF3Vh7cv=7iv+vA5DBa2qi9HA@mail.gmail.com>
Date: Mon, 11 Feb 2019 08:52:08 +0100
From: Magnus Karlsson <magnus.karlsson@...il.com>
To: Jean-Mickael Guerin <jmg@...nd.com>
Cc: Magnus Karlsson <magnus.karlsson@...el.com>,
Björn Töpel <bjorn.topel@...el.com>,
ast@...nel.org, Daniel Borkmann <daniel@...earbox.net>,
Network Development <netdev@...r.kernel.org>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
Björn Töpel <bjorn.topel@...il.com>,
"Zhang, Qi Z" <qi.z.zhang@...el.com>,
Jesper Dangaard Brouer <brouer@...hat.com>,
xiaolong.ye@...el.com
Subject: Re: [PATCH bpf-next v4 0/2] libbpf: adding AF_XDP support
On Mon, Feb 11, 2019 at 7:34 AM Jean-Mickael Guerin <jmg@...nd.com> wrote:
>
> 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?)
Exactly :-). Spot on.
/Magnus
> Jean-Mickael
Powered by blists - more mailing lists