public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: "Li,Rongqing(ACG CCN)" <lirongqing@baidu.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: 答复: [PATCH][rdma-next] RDMA/mlx5: Use NUMA-aware allocation for memory region descriptors
Date: Sun, 8 Mar 2026 14:46:04 +0200	[thread overview]
Message-ID: <20260308124604.GP12611@unreal> (raw)
In-Reply-To: <ccaf962222eb41a6a909ec434ccb80c6@baidu.com>

On Fri, Mar 06, 2026 at 05:23:07AM +0000, Li,Rongqing(ACG CCN) wrote:
> 
> > The mlx5_alloc_priv_descs() function currently uses kzalloc(), which allocates
> > memory on the NUMA node of the calling CPU. On multi-socket systems, this
> > can lead to cross-node memory access if the HCA is attached to a different
> > NUMA node than the process allocating the Memory Region (MR).
> > 
> > Switch to kzalloc_node() and specify the node associated with the HCA's DMA
> > device. This ensures that the MR descriptors are resident on the local NUMA
> > node, reducing latency for hardware access.
> > 
> > Signed-off-by: Li RongQing <lirongqing@baidu.com>
> 
> ping
> 
> [Li,Rongqing] 

I have no plans to merge these patches in RDMA subsystem. It is unlikely
can give any benefit to the performance.

Thanks

      reply	other threads:[~2026-03-08 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24  9:07 [PATCH][rdma-next] RDMA/mlx5: Use NUMA-aware allocation for memory region descriptors lirongqing
2026-03-06  5:23 ` 答复: " Li,Rongqing(ACG CCN)
2026-03-08 12:46   ` Leon Romanovsky [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=20260308124604.GP12611@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lirongqing@baidu.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