From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Vitaly Zuevsky <vitaly.zuevsky@gcore.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Richard Henderson <richard.henderson@linaro.org>,
Matt Turner <mattst88@gmail.com>,
Magnus Lindholm <linmag7@gmail.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Helge Deller <deller@gmx.de>,
Andreas Larsson <andreas@gaisler.com>,
Kuniyuki Iwashima <kuniyu@google.com>,
Willem de Bruijn <willemb@google.com>,
Arnd Bergmann <arnd@arndb.de>,
Christian Brauner <brauner@kernel.org>,
Andrew Halaney <andrew@amutable.com>,
Jori Koolstra <jkoolstra@xs4all.nl>,
Alexander Mikhalitsyn <alexander@mihalicyn.com>,
Tariq Toukan <tariqt@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Chuang Wang <nashuiliang@gmail.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-alpha@vger.kernel.org, linux-mips@vger.kernel.org,
linux-parisc@vger.kernel.org, sparclinux@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: [RFC PATCH net-next v1 1/2] net: add SO_NO_RFS to exclude a socket from RFS and aRFS
Date: Sat, 31 Oct 2026 11:15:03 -0400 [thread overview]
Message-ID: <willemdebruijn.kernel.e08dc63db124@gmail.com> (raw)
In-Reply-To: <20261031113330.45704-2-vitaly.zuevsky@gcore.com>
Vitaly Zuevsky wrote:
> RFS and accelerated RFS are enabled per host and per rx queue, but
> whether steering helps is a property of the flow. A host that carries
> a few long-lived flows which benefit from steering alongside a large
> churn of short-lived flows has no way to express that today.
>
> Add a boolean socket option, SO_NO_RFS. When set, sock_rps_record_flow()
> does not record the socket in rps_sock_flow_table, so get_rps_cpu()
> finds no match and neither software RFS nor ndo_rx_flow_steer() acts
> on the flow; it stays on the CPU chosen by RSS or RPS.
>
> The option is kept in sk_flags so that sk_clone_lock() copies it to
> accepted children: setting it on a listening socket excludes every
> connection accepted from it, while sockets the same process connects
> itself remain eligible.
>
> sock_rps_delete_flow() is skipped as well, because a socket that never
> recorded itself must not clear a table slot that may belong to another
> flow.
>
> The test sits after the TCP_ESTABLISHED check and inside the
> rfs_needed static branch, so hosts without RFS pay nothing and hosts
> with RFS pay one test_bit() on a cache line tcp_recvmsg() already
> touches.
>
> Signed-off-by: Vitaly Zuevsky <vitaly.zuevsky@gcore.com>
The Documentation change can/should be included in the main patch.
> ---
> arch/alpha/include/uapi/asm/socket.h | 2 ++
> arch/mips/include/uapi/asm/socket.h | 2 ++
> arch/parisc/include/uapi/asm/socket.h | 2 ++
> arch/sparc/include/uapi/asm/socket.h | 2 ++
> include/net/rps.h | 13 +++++++++++++
> include/net/sock.h | 1 +
> include/uapi/asm-generic/socket.h | 2 ++
> net/core/sock.c | 8 ++++++++
> 8 files changed, 32 insertions(+)
>
> diff --git a/include/net/rps.h b/include/net/rps.h
> index e33c6a2fa8bb..5afa48868236 100644
> --- a/include/net/rps.h
> +++ b/include/net/rps.h
> @@ -98,6 +98,13 @@ static inline void _sock_rps_record_flow(const struct sock *sk)
> * [1] : sk_state and sk_prot are in the same cache line.
> */
> if (sk->sk_state == TCP_ESTABLISHED) {
> + /* SO_NO_RFS: application asked us to never steer this flow.
> + * Tested after sk_state so the common case stays on one
> + * cache line.
> + */
Avoid verbose comments. Bots comment a lot more than kernel style.
Also arguably incorrect as TCP_ESTABLISHED is the common case.
> + if (unlikely(sock_flag(sk, SOCK_NO_RFS)))
> + return;
> +
> /* This READ_ONCE() is paired with the WRITE_ONCE()
> * from sock_rps_save_rxhash() and sock_rps_reset_rxhash().
> */
> @@ -111,6 +118,12 @@ static inline void _sock_rps_delete_flow(const struct sock *sk)
> rps_tag_ptr tag_ptr;
> u32 hash, index;
>
> + /* Never recorded, so never clear a slot that may belong to
> + * another flow.
Never is too strong here: can be set during socket lifetime.
Even if it had been correct, still another example of unnecessary
verbosity.
> + */
> + if (sock_flag(sk, SOCK_NO_RFS))
> + return;
> +
Both here and _sock_rfs_record_flow: probably should be in their
callers, like the other precondition check rfs_is_needed.
> hash = READ_ONCE(sk->sk_rxhash);
Optionally maybe also skip writing sk_rxhash if this is the only user.
> if (!hash)
> return;
next prev parent reply other threads:[~2026-10-31 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 11:33 [RFC PATCH net-next v1 0/2] net: per-socket opt-out from RFS/aRFS Vitaly Zuevsky
2026-10-31 11:33 ` [RFC PATCH net-next v1 1/2] net: add SO_NO_RFS to exclude a socket from RFS and aRFS Vitaly Zuevsky
2026-10-31 15:15 ` Willem de Bruijn [this message]
2026-10-31 11:33 ` [RFC PATCH net-next v1 2/2] Documentation: networking: document SO_NO_RFS Vitaly Zuevsky
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=willemdebruijn.kernel.e08dc63db124@gmail.com \
--to=willemdebruijn.kernel@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=alexander@mihalicyn.com \
--cc=andreas@gaisler.com \
--cc=andrew@amutable.com \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=deller@gmx.de \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jkoolstra@xs4all.nl \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linmag7@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=nashuiliang@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=richard.henderson@linaro.org \
--cc=saeedm@nvidia.com \
--cc=skhan@linuxfoundation.org \
--cc=sparclinux@vger.kernel.org \
--cc=tariqt@nvidia.com \
--cc=tsbogend@alpha.franken.de \
--cc=vitaly.zuevsky@gcore.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