Re: [lng-odp] [PATCH] linux-generic: schedule: set sched_local.pool correctly

Ping On Tue, Dec 1, 2015 at 7:14 AM, Bill Fischofer wrote: > This corrects bug https://bugs.linaro.org/show_bug.cgi?id=1921 > > Signed-off-by: Bill Fischofer > --- > platform/linux-generic/odp_schedule.c | 2 ++ > 1 file changed, 2

Re: [lng-odp] [PATCH] linux-generic: schedule: set sched_local.pool correctly

Merged, Maxim. On 12/10/2015 22:58, Bill Fischofer wrote: Ping On Tue, Dec 1, 2015 at 7:14 AM, Bill Fischofer > wrote: This corrects bug https://bugs.linaro.org/show_bug.cgi?id=1921 Signed-off-by: Bill Fischofer

[lng-odp] [PATCH] linux-generic: schedule: set sched_local.pool correctly

This corrects bug https://bugs.linaro.org/show_bug.cgi?id=1921 Signed-off-by: Bill Fischofer --- platform/linux-generic/odp_schedule.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/platform/linux-generic/odp_schedule.c b/platform/linux-generic/odp_schedule.c

Re: [lng-odp] [PATCH] linux-generic: schedule: set sched_local.pool correctly

I don't think there is any guarantee that all buffer returned by queue_deq_multi come from the same pool. So this should probably be updated when we copy an event out of the local cache at the beginning of schedule() Nicolas On 12/01/2015 02:14 PM, Bill Fischofer wrote: > This corrects bug

Re: [lng-odp] [PATCH] linux-generic: schedule: set sched_local.pool correctly

At least in the linux-generic implementation, we force max_deq to be 1 since we want consecutive events from an ordered queue to be dispatched to separate threads. There's no advantage to batching things as is done in parallel queues since if Thread A has events 1, 2,3, 4 while Thread B has