From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru,
keesang.song@amd.com, anatoly.burakov@intel.com,
david.marchand@redhat.com, bruce.richardson@intel.com,
David Christensen <drc@linux.vnet.ibm.com>
Subject: [dpdk-dev] NUMA node/socket
Date: Sun, 04 Jul 2021 03:38:36 +0200 [thread overview]
Message-ID: <2863796.yO5TXMfXnl@thomas> (raw)
There are some mix between NUMA node and socket IDs in DPDK.
Examples:
* rte_eth_dev_socket_id() returns the NUMA node.
* rte_malloc use sockets to allocate the memory
Is it critical?
next reply other threads:[~2021-07-04 1:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-04 1:38 Thomas Monjalon [this message]
2021-07-04 1:53 ` Thomas Monjalon
2021-07-04 8:27 ` Andrew Rybchenko
2021-07-04 9:28 ` Thomas Monjalon
2021-07-04 16:18 ` Stephen Hemminger
2021-07-04 16:27 ` Dmitry Kozlyuk
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=2863796.yO5TXMfXnl@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=ferruh.yigit@intel.com \
--cc=keesang.song@amd.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;
as well as URLs for NNTP newsgroup(s).