public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Alexei Starovoitov <ast@fb•com>
To: "Björn Töpel" <bjorn.topel@gmail•com>, "William Tu" <u9012063@gmail•com>
Cc: "Karlsson, Magnus" <magnus.karlsson@intel•com>,
	"Alexander Duyck" <alexander.h.duyck@intel•com>,
	"Alexander Duyck" <alexander.duyck@gmail•com>,
	"John Fastabend" <john.fastabend@gmail•com>,
	"Jesper Dangaard Brouer" <brouer@redhat•com>,
	"Willem de Bruijn" <willemdebruijn.kernel@gmail•com>,
	"Daniel Borkmann" <daniel@iogearbox•net>,
	"Linux Kernel Network Developers" <netdev@vger•kernel.org>,
	"Björn Töpel" <bjorn.topel@intel•com>,
	michael.lundkvist@ericsson•com, "Brandeburg,
	Jesse" <jesse.brandeburg@intel•com>,
	"Anjali Singhai Jain" <anjali.singhai@intel•com>,
	"Zhang, Qi Z" <qi.z.zhang@intel•com>,
	ravineet.singh@ericsson•com
Subject: Re: [RFC PATCH v2 00/14] Introducing AF_XDP support
Date: Wed, 11 Apr 2018 11:43:35 -0700	[thread overview]
Message-ID: <bcfd90dd-4977-4f97-daec-c7128bcdb67e@fb.com> (raw)
In-Reply-To: <CAJ+HfNiJ+tS6cG4_cCj1syQC8m8OZWM44-NX-hbdRYWQj=98TA@mail.gmail.com>

On 4/11/18 5:17 AM, Björn Töpel wrote:
>
> In the current RFC you are required to create both an Rx and Tx queue
> to bind the socket, which is just weird for your "Rx on one device, Tx
> to another" scenario. I'll fix that in the next RFC.

I would defer on adding new features until the key functionality lands.
imo it's in good shape and I would submit it without RFC tag as soon as
net-next reopens.

  reply	other threads:[~2018-04-11 18:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-27 16:59 [RFC PATCH v2 00/14] Introducing AF_XDP support Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 01/14] net: initial AF_XDP skeleton Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 02/14] xsk: add user memory registration support sockopt Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 03/14] xsk: add umem fill queue support and mmap Björn Töpel
2018-04-12  2:15   ` Michael S. Tsirkin
2018-04-12  7:38     ` Karlsson, Magnus
2018-04-12  8:54       ` Jesper Dangaard Brouer
2018-04-12 14:04       ` Michael S. Tsirkin
2018-04-12 15:19         ` Karlsson, Magnus
2018-04-23 10:26           ` Karlsson, Magnus
2018-03-27 16:59 ` [RFC PATCH v2 04/14] xsk: add Rx queue setup and mmap support Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 05/14] xsk: add support for bind for Rx Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 06/14] xsk: add Rx receive functions and poll support Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 07/14] bpf: introduce new bpf AF_XDP map type BPF_MAP_TYPE_XSKMAP Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 08/14] xsk: wire up XDP_DRV side of AF_XDP Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 09/14] xsk: wire up XDP_SKB " Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 10/14] xsk: add umem completion queue support and mmap Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 11/14] xsk: add Tx queue setup and mmap support Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 12/14] xsk: support for Tx Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 13/14] xsk: statistics support Björn Töpel
2018-03-27 16:59 ` [RFC PATCH v2 14/14] samples/bpf: sample application for AF_XDP sockets Björn Töpel
2018-04-12 11:05   ` Jesper Dangaard Brouer
2018-04-12 11:08     ` Karlsson, Magnus
2018-03-28 21:18 ` [RFC PATCH v2 00/14] Introducing AF_XDP support Eric Leblond
2018-03-29  6:16   ` Björn Töpel
2018-03-29 15:36     ` Jesper Dangaard Brouer
2018-04-09 21:51 ` William Tu
2018-04-10  6:47   ` Björn Töpel
2018-04-10 14:14     ` William Tu
2018-04-11 12:17       ` Björn Töpel
2018-04-11 18:43         ` Alexei Starovoitov [this message]
2018-04-12 14:14           ` Björn Töpel

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=bcfd90dd-4977-4f97-daec-c7128bcdb67e@fb.com \
    --to=ast@fb$(echo .)com \
    --cc=alexander.duyck@gmail$(echo .)com \
    --cc=alexander.h.duyck@intel$(echo .)com \
    --cc=anjali.singhai@intel$(echo .)com \
    --cc=bjorn.topel@gmail$(echo .)com \
    --cc=bjorn.topel@intel$(echo .)com \
    --cc=brouer@redhat$(echo .)com \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=jesse.brandeburg@intel$(echo .)com \
    --cc=john.fastabend@gmail$(echo .)com \
    --cc=magnus.karlsson@intel$(echo .)com \
    --cc=michael.lundkvist@ericsson$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=qi.z.zhang@intel$(echo .)com \
    --cc=ravineet.singh@ericsson$(echo .)com \
    --cc=u9012063@gmail$(echo .)com \
    --cc=willemdebruijn.kernel@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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