All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: davem@davemloft.net, alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
	bjorn.topel@intel.com,
	Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH net-next 0/3] xsk: improvements to RX queue check and replace
Date: Mon, 30 Jul 2018 20:43:50 -0700	[thread overview]
Message-ID: <20180731034353.3774-1-jakub.kicinski@netronome.com> (raw)

Hi!

First 3 patches of my recent RFC.  The first one make the check against
real_num_rx_queues slightly more reliable, while the latter two redefine
XDP_QUERY_XSK_UMEM slightly to disallow replacing UMEM in the driver at
the stack level.

I'm not sure where this lays on the bpf vs net trees scale, but there
should be no conflicts with either tree.

Jakub Kicinski (3):
  net: update real_num_rx_queues even when !CONFIG_SYSFS
  xsk: refactor xdp_umem_assign_dev()
  xsk: don't allow umem replace at stack level

 include/linux/netdevice.h | 10 +++---
 net/xdp/xdp_umem.c        | 70 +++++++++++++++++++++++----------------
 2 files changed, 47 insertions(+), 33 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-07-31  5:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31  3:43 Jakub Kicinski [this message]
2018-07-31  3:43 ` [PATCH net-next 1/3] net: update real_num_rx_queues even when !CONFIG_SYSFS Jakub Kicinski
2018-07-31 13:02   ` Jesper Dangaard Brouer
2018-07-31  3:43 ` [PATCH net-next 2/3] xsk: refactor xdp_umem_assign_dev() Jakub Kicinski
2018-07-31  3:43 ` [PATCH net-next 3/3] xsk: don't allow umem replace at stack level Jakub Kicinski
2018-07-31  6:34 ` [PATCH net-next 0/3] xsk: improvements to RX queue check and replace Björn Töpel
2018-07-31  7:50 ` Daniel Borkmann
2018-07-31 16:48   ` David Miller

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=20180731034353.3774-1-jakub.kicinski@netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bjorn.topel@intel.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.