From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Jun Yang <jun.yang@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Stable@dpdk.org" <Stable@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] RE: [PATCH 2/2] examples/ip_pipeline: fix to use sock id instead of cpuid
Date: Tue, 18 Feb 2020 10:47:54 +0000 [thread overview]
Message-ID: <DM6PR11MB2714D9BDB434DA43A79D9503EB110@DM6PR11MB2714.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DB6PR04MB312830BB960A5EAE127BBABD9D150@DB6PR04MB3128.eurprd04.prod.outlook.com>
> -----Original Message-----
> From: Jun Yang <jun.yang@nxp.com>
> Sent: Friday, February 14, 2020 3:19 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>; dev@dpdk.org
> Cc: Stable@dpdk.org
> Subject: RE: [EXT] RE: [dpdk-dev] [PATCH 2/2] examples/ip_pipeline: fix to
> use sock id instead of cpuid
>
> Hi Cristian,
> Per my debug log, the CPU ID is actually DPDK current core ID on NXP ARM64
> platform whose socket ID is always 0.
>
Hi Jun,
The params->cpu_id is vendor independent, it is always the CPU socket ID and is consistently used as the NUMA node to allocate memory on. If your system has a single CPU socket, then this parameter should be equal to 0. As clearly documented and stated before, this parameter is never the CPU core ID, which is typically called core_id or lcore_id consistently in the code. Again, not sure where this confusion is coming from.
Regards,
Cristian
next prev parent reply other threads:[~2020-02-18 10:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 5:25 [dpdk-dev] [PATCH 1/2] examples/ip_pipeline: fix crypto queue config Hemant Agrawal
2019-12-11 5:25 ` [dpdk-dev] [PATCH 2/2] examples/ip_pipeline: fix to use sock id instead of cpuid Hemant Agrawal
2020-02-14 11:27 ` Dumitrescu, Cristian
2020-02-14 15:18 ` [dpdk-dev] [EXT] " Jun Yang
2020-02-18 10:47 ` Dumitrescu, Cristian [this message]
2020-02-19 14:17 ` Jun Yang
2020-02-14 10:52 ` [dpdk-dev] [PATCH 1/2] examples/ip_pipeline: fix crypto queue config Zhang, Roy Fan
2020-02-14 11:22 ` Dumitrescu, Cristian
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=DM6PR11MB2714D9BDB434DA43A79D9503EB110@DM6PR11MB2714.namprd11.prod.outlook.com \
--to=cristian.dumitrescu@intel.com \
--cc=Stable@dpdk.org \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jun.yang@nxp.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).