[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

Another comment is, comment out lcore_socket_id check will influence other architectures. If possible, I would like to make this change to Power specific. -Original Message- From: gowrishankar muthukrishnan [mailto:gowrishanka...@linux.vnet.ibm.com] Sent: 2016?8?12? 17:00 To: Chao Zhu

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

Hi Chao, I have simplified the approach for this patch in v5. * Including ppc64le specific changes * App panic in creating core map only in SMT=off case, so that would be addressed separately. Hoping with new patch set v5, your review would be easier. Regards, Gowrishankar On Friday 12

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

Gowrishankar, I suggest to set the following value: n_max_cores_per_socket = 8 n_max_ht_per_core = 8 This will cover most of the Power8 servers. Any comments? -Original Message- From: gowrishankar muthukrishnan [mailto:gowrishanka...@linux.vnet.ibm.com] Sent: 2016?8?11? 20:02 To:

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

On Friday 12 August 2016 03:45 PM, Chao Zhu wrote: > Another comment is, comment out lcore_socket_id check will influence other > architectures. If possible, I would like to make this change to Power > specific. Hi Chao, I am revisiting cpu_core_map_init() fn. I realize, all we handle is max

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

On Friday 12 August 2016 02:14 PM, Chao Zhu wrote: > Gowrishankar, > > I suggest to set the following value: > > n_max_cores_per_socket = 8 > n_max_ht_per_core = 8 > > This will cover most of the Power8 servers. > Any comments? Sure Chao. I will include this change in v5. If there are no other

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

Gowrishankar, Thanks for the detail. If my understanding is correct, Power8 has different chips. Some of the OpenPOWER chips have 8 cores per socket. And the max threads per core is 8. Should we support this in cpu_core_map_init()? Here's a dump from the OpenPOWER system.

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

On Thursday 11 August 2016 03:59 PM, Chao Zhu wrote: > Gowrishankar, > > Thanks for the detail. > If my understanding is correct, Power8 has different chips. Some of the > OpenPOWER chips have 8 cores per socket. And the max threads per core is 8. > Should we support this in cpu_core_map_init()?

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

Gowrishankar, Can you give more description about this patch? Thank you! -Original Message- From: Gowrishankar Muthukrishnan [mailto:gowrishanka...@linux.vnet.ibm.com] Sent: 2016?8?6? 20:33 To: dev at dpdk.org Cc: Chao Zhu ; Bruce Richardson ; Konstantin Ananyev ; Thomas Monjalon ;

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

Hi Chao, Sure. Please find below one. This patch fixes ip_pipeline panic in app_init_core_map while preparing cpu core map in powerpc with SMT off. cpu_core_map_compute_linux currently prepares core mapping based on file existence in sysfs ie.

[dpdk-dev] [PATCH v4 3/6] ip_pipeline: fix lcore mapping for varying SMT threads as in ppc64

From: gowrishankar offline lcore would still refer to original core id and this has to be considered while creating cpu core mask. Signed-off-by: Gowrishankar --- config/defconfig_ppc_64-power8-linuxapp-gcc | 3 --- examples/ip_pipeline/cpu_core_map.c