[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250103185954.1236510-1-kuba@kernel.org>
Date: Fri, 3 Jan 2025 10:59:45 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: davem@...emloft.net
Cc: netdev@...r.kernel.org,
edumazet@...gle.com,
pabeni@...hat.com,
dw@...idwei.uk,
almasrymina@...gle.com,
jdamato@...tly.com,
Jakub Kicinski <kuba@...nel.org>
Subject: [PATCH net-next 0/8] net: make sure we retain NAPI ordering on netdev->napi_list
I promised Eric to remove the rtnl protection of the NAPI list,
when I sat down to implement it over the break I realized that
the recently added NAPI ID retention will break the list ordering
assumption we have in netlink dump. The ordering used to happen
"naturally", because we'd always add NAPIs that the head of the
list, and assign a new monotonically increasing ID.
Before the first patch of this series we'd still only add at
the head of the list but now the newly added NAPI may inherit
from its config an ID lower than something else already on the list.
The fix is in the first patch, the rest is netdevsim churn to test it.
I'm posting this for net-next, because AFAICT the problem can't
be triggered in net, given the very limited queue API adoption.
Jakub Kicinski (8):
net: make sure we retain NAPI ordering on netdev->napi_list
netdev: define NETDEV_INTERNAL
netdevsim: support NAPI config
netdevsim: allocate rqs individually
netdevsim: add queue alloc/free helpers
netdevsim: add queue management API support
netdevsim: add debugfs-triggered queue reset
selftests: net: test listing NAPI vs queue resets
Documentation/networking/netdevices.rst | 10 +
drivers/net/netdevsim/netdev.c | 254 ++++++++++++++++++++---
drivers/net/netdevsim/netdevsim.h | 5 +-
net/core/dev.c | 42 +++-
net/core/netdev_rx_queue.c | 1 +
tools/testing/selftests/net/nl_netdev.py | 19 +-
6 files changed, 292 insertions(+), 39 deletions(-)
--
2.47.1
Powered by blists - more mailing lists