netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: sameehj@amazon.com, davem@davemloft.net, netdev@vger.kernel.org,
	dwmw@amazon.com, zorik@amazon.com, matua@amazon.com,
	saeedb@amazon.com, msw@amazon.com, aliguori@amazon.com,
	nafea@amazon.com, gtzalik@amazon.com, netanel@amazon.com,
	alisaidi@amazon.com, benh@amazon.com, akiyano@amazon.com,
	ndagan@amazon.com, ast@kernel.org, daniel@iogearbox.net,
	kafai@fb.com, songliubraving@fb.com, yhs@fb.com, andriin@fb.com,
	john.fastabend@gmail.com, kpsingh@chromium.org, kuba@kernel.org,
	hawk@kernel.org, shayagr@amazon.com, lorenzo@kernel.org
Subject: Re: [PATCH RFC net-next 0/2] XDP multi buffer helpers
Date: Tue, 28 Jul 2020 14:54:33 +0200	[thread overview]
Message-ID: <20200728125433.GB286429@lore-desk> (raw)
In-Reply-To: <20200728123327.GB25823@ranger.igk.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2303 bytes --]

> On Mon, Jul 27, 2020 at 12:56:51PM +0000, sameehj@amazon.com wrote:
> > From: Sameeh Jubran <sameehj@amazon.com>
> > 
> > This series is based on the series that Lorenzo sent [0].
> 
> What is your final design for multi buffer support in XDP?
> Why don't you provide a single RFC that is fully functional but instead
> you're sending a bunch of separate RFCs?

Hi Maciej,

IMO the buffer layout is defined now (we will use the trailing part of the
"linear" area of the xdp_buff to store references for subsequent buffers like
we already do for skb).
What is not defined yet are the metadata (e.g. number of frames, total length, ..)
we want to pass to the bpf layer. This is the main reason why I sent this series
[1] as RFC, I want to collect feedbacks about this approach. For the moment (at
least in my series) mb in xdp_buff is just used to indicate if this is a
multi-buff xdp_buff.

> 
> IMHO it's a weird strategy. Not sure what others think about.
> 

we did not coordinate, sorry for the noise.

Regards,
Lorenzo

[1] https://patchwork.ozlabs.org/project/netdev/cover/cover.1595503780.git.lorenzo@kernel.org/

> > 
> > This series simply adds new bpf helpers for xdp mb support as well as
> > introduces a sample program that uses them.
> > 
> > [0] - [RFC net-next 00/22] Introduce mb bit in xdp_buff/xdp_frame
> 
> Direct link wouldn't hurt I guess :) Please also include all the previous
> discussions that took place on mailing list around this topic. This will
> make reviewers life easier I suppose. As I asked above, I'm not sure
> what's your final design for this feature.
> 
> > 
> > Sameeh Jubran (2):
> >   xdp: helpers: add multibuffer support
> >   samples/bpf: add bpf program that uses xdp mb helpers
> > 
> >  include/uapi/linux/bpf.h       |  13 +++
> >  net/core/filter.c              |  60 ++++++++++++++
> >  samples/bpf/Makefile           |   3 +
> >  samples/bpf/xdp_mb_kern.c      |  66 ++++++++++++++++
> >  samples/bpf/xdp_mb_user.c      | 174 +++++++++++++++++++++++++++++++++++++++++
> >  tools/include/uapi/linux/bpf.h |  13 +++
> >  6 files changed, 329 insertions(+)
> >  create mode 100644 samples/bpf/xdp_mb_kern.c
> >  create mode 100644 samples/bpf/xdp_mb_user.c
> > 
> > -- 
> > 2.16.6
> > 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2020-07-28 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 12:56 [PATCH RFC net-next 0/2] XDP multi buffer helpers sameehj
2020-07-27 12:56 ` [PATCH RFC net-next 1/2] xdp: helpers: add multibuffer support sameehj
2020-07-27 19:35   ` David Miller
2020-07-27 12:56 ` [PATCH RFC net-next 2/2] samples/bpf: add bpf program that uses xdp mb helpers sameehj
2020-07-28 12:33 ` [PATCH RFC net-next 0/2] XDP multi buffer helpers Maciej Fijalkowski
2020-07-28 12:54   ` Lorenzo Bianconi [this message]
2020-07-28 18:48   ` Jakub Kicinski

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=20200728125433.GB286429@lore-desk \
    --to=lorenzo.bianconi@redhat.com \
    --cc=akiyano@amazon.com \
    --cc=aliguori@amazon.com \
    --cc=alisaidi@amazon.com \
    --cc=andriin@fb.com \
    --cc=ast@kernel.org \
    --cc=benh@amazon.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dwmw@amazon.com \
    --cc=gtzalik@amazon.com \
    --cc=hawk@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@chromium.org \
    --cc=kuba@kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=matua@amazon.com \
    --cc=msw@amazon.com \
    --cc=nafea@amazon.com \
    --cc=ndagan@amazon.com \
    --cc=netanel@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedb@amazon.com \
    --cc=sameehj@amazon.com \
    --cc=shayagr@amazon.com \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    --cc=zorik@amazon.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).