> -----Original Message----- > From: Jun Yang <jun.y...@nxp.com> > Sent: Friday, February 14, 2020 3:19 PM > To: Dumitrescu, Cristian <cristian.dumitre...@intel.com>; Hemant Agrawal > <hemant.agra...@nxp.com>; dev@dpdk.org > Cc: sta...@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
