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

2015-02-13 Thread Olivier MATZ
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

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

2015-02-13 Thread Liang, Cunming
> -Original Message- > From: Ananyev, Konstantin > Sent: Thursday, February 12, 2015 9:54 PM > To: Liang, Cunming; dev at dpdk.org > Cc: olivier.matz at 6wind.com > Subject: RE: [PATCH v5 19/19] timer: add support to non-EAL thread > > Hi lads, > > > -Original Message- > > From:

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

2015-02-12 Thread Cunming Liang
Allow to setup timers only for EAL (lcore) threads (__lcore_id < MAX_LCORE_ID). E.g. ? dynamically created thread will be able to reset/stop timer for lcore thread, but it will be not allowed to setup timer for itself or another non-lcore thread. rte_timer_manage() for non-lcore thread would simp

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

2015-02-12 Thread Ananyev, Konstantin
Hi lads, > -Original Message- > From: Liang, Cunming > Sent: Thursday, February 12, 2015 8:17 AM > To: dev at dpdk.org > Cc: Ananyev, Konstantin; olivier.matz at 6wind.com; Liang, Cunming > Subject: [PATCH v5 19/19] timer: add support to non-EAL thread > > Allow to setup timers only for E