net: default_rps_mask follow-up
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 1 replyIn review
- v12 patches 3 repliesSuperseded
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | net: make default_rps_mask a per netns attributeinclude/ include/ net/ +1 more | +59 | 1 reply | |
| 2/2 | self-tests: more rps self teststools/ | +29 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 net-next 0/2] net: default_rps_mask follow-up
The first patch namespacify the setting. In the common case, once proper isolation is in place in the main namespace, forwarding to/from each child netns will allways happen on the desidered CPUs.
Any additional RPS stage inside the child namespace will not provide additional isolation and could hurt performance badly if picking a CPU on a remote node.
The 2nd patch adds more self-tests coverage.
Paolo Abeni (2):
net: make default_rps_mask a per netns attribute
self-tests: more rps self tests
include/linux/netdevice.h | 1 - include/net/netns/core.h | 5 ++ net/core/net-sysfs.c | 23 ++++++--- net/core/sysctl_net_core.c | 51 ++++++++++++++----- .../testing/selftests/net/rps_default_mask.sh | 41 ++++++++++----- 5 files changed, 88 insertions(+), 33 deletions(-)
Signature · 1 line
2.39.1