mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Chuang Wang <nashuiliang@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	Stanislav Fomichev <sdf.kernel@gmail.com>,
	Hangbin Liu <liuhangbin@gmail.com>,
	Samiullah Khawaja <skhawaja@google.com>,
	Neal Cardwell <ncardwell@google.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v11] net: reduce ARFS flow updates by checking LLC affinity
Date: Mon, 19 Oct 2026 18:42:18 -0700	[thread overview]
Message-ID: <20261019184218.14d6b8ad@kernel.org> (raw)
In-Reply-To: <20261012060152.2930-1-nashuiliang@gmail.com>

On Mon, 12 Oct 2026 14:01:08 +0800 Chuang Wang wrote:
> +		/*

nit: empty line not needed in networking, start with the "title":

	/* ARFS LLC Affinity Feature:

> +		 * ARFS LLC Affinity Feature:
> +		 * Reduce ARFS flow updates by checking LLC affinity.
> +		 *
> +		 * Frequent flow table updates can trigger constant hardware steering
> +		 * reconfigurations (e.g., ndo_rx_flow_steer), leading to significant
> +		 * contention on driver internal locks (like mlx5's arfs_lock).
> +		 *
> +		 * Skip the expensive hardware steering update if the flow's previous
> +		 * target CPU and the new one share the last level cache: cache locality
> +		 * for the application is preserved either way.
> +		 */

Honestly, I don't think this comment is needed at all. The check 
is pretty understandable to anyone with any system config experience.

> +		if (static_branch_unlikely(&arfs_llc_affinity) &&
> +		    old_cpu < nr_cpu_ids && cpu_online(old_cpu) &&
> +			cpus_share_cache(old_cpu, next_cpu))
> +			goto out;

The last line of the condition is mis-aligned 

> +	{
> +		.procname	= "arfs_llc_affinity",
> +		.data		= &arfs_llc_affinity.key,
> +		.maxlen		= sizeof(arfs_llc_affinity.key),
> +		.mode		= 0644,
> +		.proc_handler	= proc_do_static_key
> +	},

You're adding a uAPI / profcs knob. It needs to be documented
appropriately under Documentation/

Please note that net next is closed:
https://netdev.bots.linux.dev/net-next.html
-- 
pw-bot: cr

      parent reply	other threads:[~2026-10-20  1:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12  6:01 Chuang Wang
2026-10-13  7:00 ` netdev-bot+sashiko
2026-10-13  7:07   ` Kuniyuki Iwashima
2026-10-14  5:47     ` chuang
2026-10-14  3:51   ` chuang
2026-10-20  1:42 ` Jakub Kicinski [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=20261019184218.14d6b8ad@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuniyu@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=nashuiliang@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roman.gushchin@linux.dev \
    --cc=sdf.kernel@gmail.com \
    --cc=skhawaja@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

all inboxes | Powered by JetHome®