public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "Jubran, Samih" <sameehj@amazon.com>
Cc: "Luigi Rizzo" <rizzo@iet.unipi.it>,
	"Machulsky, Zorik" <zorik@amazon.com>,
	"Daniel Borkmann" <borkmann@iogearbox.net>,
	"David Miller" <davem@davemloft.net>,
	"Tzalik, Guy" <gtzalik@amazon.com>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Toke Høiland-Jørgensen" <toke@redhat.com>,
	"Kiyanovski, Arthur" <akiyano@amazon.com>,
	"Alexei Starovoitov" <ast@kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"David Ahern" <dsahern@gmail.com>,
	brouer@redhat.com
Subject: Re: XDP multi-buffer design discussion
Date: Wed, 22 Jan 2020 19:50:24 +0100	[thread overview]
Message-ID: <20200122195024.4bacf33a@carbon> (raw)
In-Reply-To: <9258f0767307489cb54428a8c1d91a0d@EX13D11EUB003.ant.amazon.com>

On Sun, 19 Jan 2020 07:34:00 +0000 "Jubran, Samih" <sameehj@amazon.com> wrote:

[...]
> 
> We have two proposed design solutions.  One (Jesper’s) seems easier
> to implement and gives the average XDP developer the framework to
> deal with multiple buffers.  The other (Luigi’s) seems more complete
> but raises a few questions:
>
> 1.	The netdev's callback might be too intrusive to the net
> drivers and requires the driver to somehow save context of the
> current processed packet
>
> 2.	The solution might be an overkill to the average XDP
> developer.  Does the average XDP developer really need full access to
> the packet?
> 
> Since Jesper's design is easier to implement as well as leaves a way
> for future extension to Luigi's design, I'm going to implement and
> share it with you.

Thanks for letting us know you are still working on this.

_WHEN_ you hit issue please feel free to reach out to me. (p.s. I'll be
in Brno at DevConf.cz the next couple of days. But will be back
Tuesday and back on IRC at Freenode channel #xdp nick:netoptimizer).

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer


      reply	other threads:[~2020-01-22 18:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BA8DC06A-C508-402D-8A18-B715FBA674A2@amazon.com>
     [not found] ` <b28504a3-4a55-d302-91fe-63915e4568d3@iogearbox.net>
     [not found]   ` <5FA3F980-29E6-4B91-8150-9F28C0E09C45@amazon.com>
     [not found]     ` <20190823084704.075aeebd@carbon>
     [not found]       ` <67C7F66A-A3F7-408F-9C9E-C53982BCCD40@amazon.com>
     [not found]         ` <20191204155509.6b517f75@carbon>
     [not found]           ` <ec2fd7f6da44410fbaeb021cf984f2f6@EX13D11EUC003.ant.amazon.com>
2019-12-16 14:07             ` XDP multi-buffer design discussion Jesper Dangaard Brouer
2019-12-17  4:15               ` Luigi Rizzo
2019-12-17  8:46                 ` Jesper Dangaard Brouer
2019-12-17  9:00                   ` Toke Høiland-Jørgensen
2019-12-17 15:44                     ` Jubran, Samih
2019-12-17 22:30                   ` Luigi Rizzo
2019-12-18 16:03                     ` Jubran, Samih
2019-12-19 10:44                       ` Jesper Dangaard Brouer
2019-12-19 17:29                         ` Luigi Rizzo
2020-01-19  7:34                           ` Jubran, Samih
2020-01-22 18:50                             ` Jesper Dangaard Brouer [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=20200122195024.4bacf33a@carbon \
    --to=brouer@redhat.com \
    --cc=akiyano@amazon.com \
    --cc=ast@kernel.org \
    --cc=borkmann@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=gtzalik@amazon.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=rizzo@iet.unipi.it \
    --cc=sameehj@amazon.com \
    --cc=toke@redhat.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