[dpdk-dev] [PATCH v5 19/19] timer: add support to non-EAL thread

Olivier MATZ olivier.matz at 6wind.com
Fri Feb 13 10:57:40 CET 2015


Hi,

On 02/13/2015 01:55 AM, Liang, Cunming wrote:
>> About ' lcore_id != LCORE_ID_ANY' vs ' lcore_id < RTE_MAX_LCORE'.
>> I think both ways are valid right now.
>> Though using ' lcore_id != LCORE_ID_ANY' means, that if user will setup
>> PER_LCORE(_lcore_id) for dynamically created thread to some value >=
>> RTE_MAX_LCORE,
>> then our code will not work properly.
>> Konstantin
> [LCM] Ok, now we get the agreement as below.
> 1. only using '< RTE_MAX_LCORE' to check the EAL thread with valid lcore_id.
> 2. LCORE_ID_ANY is used as lcore_id default value or used for any  unspecified lcore_id assignment.

Doing like this is fine for me, although I don't really agree with
the initial argument: it's should not be allowed for an application
to modify an eal variable (_lcore_id).

Regards,
Olivier


More information about the dev mailing list