From: Krishna Kumar <krikku@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, tom@herbertland.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
sdf@fomichev.me, kuniyu@google.com, ahmed.zaki@intel.com,
aleksander.lobakin@intel.com, atenart@kernel.org,
jdamato@fastly.com, krishna.ku@flipkart.com, krikku@gmail.com
Subject: [PATCH v5 net-next 0/2] net: RPS table overwrite prevention and flow_id caching
Date: Mon, 21 Jul 2025 08:46:07 +0530 [thread overview]
Message-ID: <20250721031609.132217-1-krikku@gmail.com> (raw)
This series splits the previous RPS patch [1] into two patches for
net-next following reviewer feedback. It also addresses a kernel test
robot warning by ensuring rps_flow_is_active() is defined only when
aRFS is enabled. I tested v3 with four builds and reboots: two for
[PATCH 1/2] with aRFS enabled/disabled, and two for [PATCH 2/2].
There are no code changes in v4 and v5, only documentation, etc.
The first patch prevents RPS table overwrite for active flows thereby
improving aRFS stability.
The second patch caches hash & flow_id in get_rps_cpu() to avoid
recalculating it in set_rps_cpu() (this patch depends on the first).
[1] https://lore.kernel.org/netdev/20250708081516.53048-1-krikku@gmail.com/
[2] https://lore.kernel.org/netdev/20250717064554.3e4d9993@kernel.org/
Signed-off-by: Krishna Kumar <krikku@gmail.com>
---
v5: Same v4 patch sent with a change in documentation style for "return".
v4: Same v3 patch sent as a new thread instead of a continuation.
v3: Wrapped rps_flow_is_active() in #ifdef CONFIG_RFS_ACCEL to fix
unused function warning reported by kernel test robot.
v2: Split original patch into two: RPS table overwrite prevention and hash/
flow_id caching.
Krishna Kumar (2):
net: Prevent RPS table overwrite for active flows
net: Cache hash and flow_id to avoid recalculation
include/net/rps.h | 5 ++-
net/core/dev.c | 89 ++++++++++++++++++++++++++++++++++++++------
net/core/net-sysfs.c | 4 +-
3 files changed, 84 insertions(+), 14 deletions(-)
--
2.43.0
next reply other threads:[~2025-07-21 3:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 3:16 Krishna Kumar [this message]
2025-07-21 3:16 ` [PATCH v5 net-next 1/2] net: Prevent RPS table overwrite for active flows Krishna Kumar
2025-07-21 8:14 ` Eric Dumazet
2025-07-21 11:12 ` Krishna Kumar
2025-07-23 4:33 ` Krishna Kumar
2025-07-21 8:21 ` Eric Dumazet
2025-07-21 11:33 ` Krishna Kumar
2025-07-21 3:16 ` [PATCH v5 net-next 2/2] net: Cache hash and flow_id to avoid recalculation Krishna Kumar
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=20250721031609.132217-1-krikku@gmail.com \
--to=krikku@gmail.com \
--cc=ahmed.zaki@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jdamato@fastly.com \
--cc=krishna.ku@flipkart.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=tom@herbertland.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).