[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180726214148.2087-1-jakub.kicinski@netronome.com>
Date: Thu, 26 Jul 2018 14:41:42 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: alexei.starovoitov@...il.com, daniel@...earbox.net,
brouer@...hat.com,
Björn Töpel <bjorn.topel@...el.com>,
Magnus Karlsson <magnus.karlsson@...el.com>
Cc: oss-drivers@...ronome.com, netdev@...r.kernel.org,
Jakub Kicinski <jakub.kicinski@...ronome.com>
Subject: [RFC bpf-next 0/6] net: xsk: minor improvements around queue handling
Hi!
This set tries to make the core take care of error checking for the
drivers. In particular making sure that the AF_XDP UMEM is not installed
on queues which don't exist (or are disabled) and that changing queue
(AKA ethtool channel) count cannot disable queues with active AF_XDF
zero-copy sockets.
I'm sending as an RFC because I'm not entirely sure what the desired
behaviour is here. Is it Okay to install AF_XDP on queues which don't
exist? I presume not? Are the AF_XDP queue_ids referring to TX queues
as well as RX queues in case of the driver? I presume not? Should
we try to prevent disabling queues which have non zero-copy sockets
installed as well? :S
Anyway, if any of those patches seem useful and reasonable, please let
me know I will repost as non-RFC.
Jakub Kicinski (6):
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
xsk: don't allow installing UMEM beyond the number of queues
ethtool: rename local variable max -> curr
ethtool: don't allow disabling queues with umem installed
include/linux/netdevice.h | 16 +++++++--
net/core/ethtool.c | 19 ++++++----
net/xdp/xdp_umem.c | 73 ++++++++++++++++++++++++---------------
3 files changed, 71 insertions(+), 37 deletions(-)
--
2.17.1
Powered by blists - more mailing lists