From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
Willem de Bruijn <willemb@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/4] rps: misc changes
Date: Mon, 7 Apr 2025 16:35:58 +0000 [thread overview]
Message-ID: <20250407163602.170356-1-edumazet@google.com> (raw)
Minor changes in rps:
skb_flow_limit() is probably unused these days,
and data-races are quite theoretical.
Eric Dumazet (4):
net: rps: change skb_flow_limit() hash function
net: rps: annotate data-races around (struct sd_flow_limit)->count
net: add data-race annotations in softnet_seq_show()
net: rps: remove kfree_rcu_mightsleep() use
include/net/rps.h | 5 +++--
net/core/dev.c | 11 +++++++----
net/core/dev.h | 5 +++--
net/core/net-procfs.c | 9 +++++----
net/core/sysctl_net_core.c | 6 +++---
5 files changed, 21 insertions(+), 15 deletions(-)
--
2.49.0.504.g3bcea36a83-goog
next reply other threads:[~2025-04-07 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 16:35 Eric Dumazet [this message]
2025-04-07 16:35 ` [PATCH net-next 1/4] net: rps: change skb_flow_limit() hash function Eric Dumazet
2025-04-07 18:53 ` Willem de Bruijn
2025-04-07 16:36 ` [PATCH net-next 2/4] net: rps: annotate data-races around (struct sd_flow_limit)->count Eric Dumazet
2025-04-07 18:55 ` Willem de Bruijn
2025-04-07 16:36 ` [PATCH net-next 3/4] net: add data-race annotations in softnet_seq_show() Eric Dumazet
2025-04-07 19:04 ` Willem de Bruijn
2025-04-07 16:36 ` [PATCH net-next 4/4] net: rps: remove kfree_rcu_mightsleep() use Eric Dumazet
2025-04-07 19:36 ` Willem de Bruijn
2025-04-08 20:08 ` [PATCH net-next 0/4] rps: misc changes patchwork-bot+netdevbpf
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=20250407163602.170356-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).