Netdev List
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Feng Tang <feng.tang@linux.alibaba.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
	Andi Kleen <ak@linux.intel.com>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v3] selftests: net: reuseport_bpf_numa: consider cpuless numa node
Date: Mon, 10 Aug 2026 14:29:29 +0100	[thread overview]
Message-ID: <20260810132929.GS51943@horms.kernel.org> (raw)
In-Reply-To: <20260807002436.43991-1-feng.tang@linux.alibaba.com>

On Fri, Aug 07, 2026 at 08:24:36AM +0800, Feng Tang wrote:
> reuseport_bpf_numa case failed when testing on a platform with CXL
> memory:
> 
>     #./reuseport_bpf_numa
>     ---- IPv4 UDP ----
>     send node 0, receive socket 0
>     ./reuseport_bpf_numa: failed to pin to node: Invalid argument
> 
> The root cause is that the platform has 2 numa nodes: node 0 has
> both cpu and memory, while node 1 is a CXL node which only has
> memory, and caused numa_run_on_node() to fail.
> 
> Add sanity check to skip cpuless numa node for the numa binding test.
> 
> Signed-off-by: Feng Tang <feng.tang@linux.alibaba.com>
> ---
> Changelog:
>   since v2:
>     * fix spelling issue (Jakub, Sashiko)
> 	* remove unnecessary 'inline' for is_cpuless_node() (Jakub)
> 
>   since v1:
>     * address comments from Sashiko bot
>       https://lore.kernel.org/all/20260730113738.41C901F000E9@smtp.kernel.org/
>     * lift the cpuless node check out of send_from_node() 

Reviewed-by: Simon Horman <horms@kernel.org>


      reply	other threads:[~2026-08-10 13:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07  0:24 [PATCH net-next v3] selftests: net: reuseport_bpf_numa: consider cpuless numa node Feng Tang
2026-08-10 13:29 ` Simon Horman [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=20260810132929.GS51943@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=feng.tang@linux.alibaba.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox