All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Chuang Wang <nashuiliang@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, corbet@lwn.net,
	skhan@linuxfoundation.org, sdf.kernel@gmail.com,
	daniel@iogearbox.net, kuniyu@google.com, netdev@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v13] net: reduce ARFS flow updates by checking LLC affinity
Date: Wed, 18 Nov 2026 02:10:09 +0000	[thread overview]
Message-ID: <179496780902.1408948.5643474909251504479.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113125643.2255-1-nashuiliang@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Fri, 13 Nov 2026 20:56:34 +0800 you wrote:
> When an application migrates to a different CPU, RFS records the new
> CPU in the global rps_sock_flow_table via rps_record_sock_flow().  On
> the next packet of a flow, get_rps_cpu() notices the change and calls
> set_rps_cpu() to update the per-queue flow entry.  With Accelerated
> RFS (ARFS), set_rps_cpu() also invokes the driver's ndo_rx_flow_steer()
> callback so that the NIC steers the flow to a queue close to the new
> CPU.
> 
> [...]

Here is the summary with links:
  - [net-next,v13] net: reduce ARFS flow updates by checking LLC affinity
    https://git.kernel.org/netdev/net-next/c/1a0dd3c7c4ac

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-18  2:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 12:56 [PATCH net-next v13] net: reduce ARFS flow updates by checking LLC affinity Chuang Wang
2026-11-17 13:24 ` netdev-bot+sashiko
2026-11-18  2:10 ` patchwork-bot+netdevbpf [this message]

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=179496780902.1408948.5643474909251504479.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=corbet@lwn.net \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nashuiliang@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf.kernel@gmail.com \
    --cc=skhan@linuxfoundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.