All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Maayan Kashani <mkashani@nvidia.com>
Cc: dev@dpdk.org, dsosnowski@nvidia.com, rasland@nvidia.com,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: Re: [PATCH v2] net/mlx5: support NUMA node fallback
Date: Thu, 26 Jun 2025 14:11:28 +0200	[thread overview]
Message-ID: <4495972.n97fhnxGW3@thomas> (raw)
In-Reply-To: <20250625150022.183054-1-mkashani@nvidia.com>

25/06/2025 17:00, Maayan Kashani:
> Cross NUMA support means that when there is no
> memory on the local NUMA, use other available
> NUMA memory for port initialization and start.
> 
> If mlx5 malloc with specified socket failed,
> malloc function would return an error.
> To support cross NUMA,
> NUMA tolerant wrapper will be used on supported toolchains,
> and it will log the exact place where fallback allocation happened.
> NUMA tolerant flags in mlx5_malloc were added to support cases
> where the toolchain does not support statement expressions.
> 
> Add a NUMA tolerant wrapper to mlx5 malloc calls in
> ipool and devx/memory region initializations
> to support cross NUMA in device probing and port start stage.
> 
> For Tx/Rx initializations, use socket-num given by the user
>  and when SOCKET_ID_ANY is passed, default to device NUMA
> node with fallback to SOCKET_ID_ANY.
> 
> Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>

Applied, thanks.




      reply	other threads:[~2025-06-26 12:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-19  7:01 [PATCH] net/mlx5: mlx5 malloc NUMA fallback Maayan Kashani
2025-06-25 15:00 ` [PATCH v2] net/mlx5: support NUMA node fallback Maayan Kashani
2025-06-26 12:11   ` Thomas Monjalon [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=4495972.n97fhnxGW3@thomas \
    --to=thomas@monjalon.net \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@nvidia.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 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.