From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Maayan Kashani <mkashani@nvidia.com>, dev@dpdk.org
Cc: dsosnowski@nvidia.com, rasland@nvidia.com,
Aman Singh <aman.deep.singh@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@amd.com>,
Reshma Pattan <reshma.pattan@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v2] app/testpmd: cross NUMA support
Date: Sat, 26 Jul 2025 15:28:23 +0300 [thread overview]
Message-ID: <fd5f0f6a-cc34-4177-80b4-bccacf5e075c@oktetlabs.ru> (raw)
In-Reply-To: <20250626175856.1579-1-mkashani@nvidia.com>
On 6/26/25 20:58, Maayan Kashani wrote:
> Cross NUMA support means that
> if the current NUMA is out of memory,
> use another available NUMA memory.
>
> This patch is meant to support cross NUMA in testpmd,
> when disabling gro, gro fix for cross NUMA will come later.
>
> Replace pdump, metrics and dev shared data
> memory allocations to any socket
> instead of port socket id.
>
> Replace mbuf pools allocations to any socket
> when --no-numa flag is set.
I think that the patch should be split into few patches.
First of all it would allow to explain in the description
why SOCKET_ID_ANY is the right choice here since it is not
always the right choice. So, explanations are required case by case.
Second, it would allow to use correct prefix in the summary.
Summary should hint which problem is solved, what is the goal of
the patch, since "cross NUMA support" is not the goal.
As I understand the main idea behind that in general
rte_socket_id() should not be used if we don't want to strictly
bind memory allocation to the current socket. SOCKET_ID_ANY
does the same as a priority (as far as I can see), but allows
to fallback to memory which belongs to other NUMA nodes.
>
> Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> ---
> app/test-pmd/testpmd.c | 8 ++++----
> lib/ethdev/ethdev_private.c | 2 +-
> lib/pdump/rte_pdump.c | 2 +-
> 3 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/app/test-pmd/testpmd.c b/app/test-pmd/testpmd.c
> index 344c256c050..92a5d581bb9 100644
> --- a/app/test-pmd/testpmd.c
> +++ b/app/test-pmd/testpmd.c
> @@ -1729,8 +1729,7 @@ init_config(void)
> mempools[i] = mbuf_pool_create
> (mbuf_data_size[i],
> nb_mbuf_per_pool,
> - socket_num == UMA_NO_CONFIG ?
> - 0 : socket_num, i);
> + SOCKET_ID_ANY, i);
> }
>
> init_port_config();
> @@ -3057,7 +3056,8 @@ start_port(portid_t pid)
> } else {
> struct rte_mempool *mp =
> mbuf_pool_find
> - (port->socket_id, 0);
> + ((numa_support ? port->socket_id :
> + (unsigned int)SOCKET_ID_ANY), 0);
> if (mp == NULL) {
> fprintf(stderr,
> "Failed to setup RX queue: No mempool allocation on the socket %d\n",
> @@ -4476,7 +4476,7 @@ main(int argc, char** argv)
>
> #ifdef RTE_LIB_METRICS
> /* Init metrics library */
> - rte_metrics_init(rte_socket_id());
> + rte_metrics_init(SOCKET_ID_ANY);
> #endif
>
> #ifdef RTE_LIB_LATENCYSTATS
> diff --git a/lib/ethdev/ethdev_private.c b/lib/ethdev/ethdev_private.c
> index b96d992ea12..285d377d91f 100644
> --- a/lib/ethdev/ethdev_private.c
> +++ b/lib/ethdev/ethdev_private.c
> @@ -343,7 +343,7 @@ eth_dev_shared_data_prepare(void)
> /* Allocate port data and ownership shared memory. */
> mz = rte_memzone_reserve(MZ_RTE_ETH_DEV_DATA,
> sizeof(*eth_dev_shared_data),
> - rte_socket_id(), flags);
> + SOCKET_ID_ANY, flags);
> if (mz == NULL) {
> RTE_ETHDEV_LOG_LINE(ERR, "Cannot allocate ethdev shared data");
> goto out;
> diff --git a/lib/pdump/rte_pdump.c b/lib/pdump/rte_pdump.c
> index 79b20ce59b2..ba75b828f2e 100644
> --- a/lib/pdump/rte_pdump.c
> +++ b/lib/pdump/rte_pdump.c
> @@ -426,7 +426,7 @@ rte_pdump_init(void)
> int ret;
>
> mz = rte_memzone_reserve(MZ_RTE_PDUMP_STATS, sizeof(*pdump_stats),
> - rte_socket_id(), 0);
> + SOCKET_ID_ANY, 0);
> if (mz == NULL) {
> PDUMP_LOG_LINE(ERR, "cannot allocate pdump statistics");
> rte_errno = ENOMEM;
prev parent reply other threads:[~2025-07-26 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:53 [PATCH] " Maayan Kashani
2025-06-26 17:58 ` [PATCH v2] " Maayan Kashani
2025-07-26 12:28 ` Andrew Rybchenko [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=fd5f0f6a-cc34-4177-80b4-bccacf5e075c@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=ferruh.yigit@amd.com \
--cc=mkashani@nvidia.com \
--cc=rasland@nvidia.com \
--cc=reshma.pattan@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).