[dpdk-dev] [PATCH v4 00/17] support multi-pthread per core

Olivier MATZ olivier.matz at 6wind.com
Fri Feb 6 16:47:43 CET 2015


Hi,

On 02/02/2015 03:02 AM, Cunming Liang wrote:
> v4 changes:
>   new patch fixing strnlen() invalid return in 32bit icc [03/17]
>   update and add more comments on sched_yield() [16/17]
> 
> v3 changes:
>   new patch adding sched_yield() in rte_ring to avoid long spin [16/17]
> 
> v2 changes:
>   add '<number>-<number>' support for EAL option '--lcores' [02/17]
> 
> The patch series contain the enhancements of EAL and fixes for libraries
> to run multi-pthreads(either EAL or non-EAL thread) per physical core.
> Two major changes list as below:
> - Extend the core affinity of each EAL thread to 1:n.
>   Each lcore stands for a EAL thread rather than a logical core.
>   The change adds new EAL option to allow static lcore to cpuset assginment.
>   Then a lcore(EAL thread) affinity to a cpuset, original 1:1 mapping is the special case.
> - Fix the libraries to allow running on any non-EAL thread.
>   It fix the gaps running libraries in non-EAL thread(dynamic created by user).
>   Each fix libraries take care the case of rte_lcore_id() >= RTE_MAX_LCORE.

Sorry if I missed something, but after reading the mailing list threads
about this subject, I cannot find an explanation about what problem
this series try to solve.

Can you give some details about which use-case require to have multiple
pthreads per cpu? What are the advantage of doing so?

Regards,
Olivier


More information about the dev mailing list