> To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolainen@nokia-bell-
> labs.com>
> Cc: lng-odp@lists.linaro.org; bill.fischo...@linaro.org; Elo, Matias
> (Nokia - FI/Espoo) <matias....@nokia-bell-labs.com>
> Subject: Re: [lng-odp] [API-NEXT PATCH] linux-gen: scheduler: s
day, December 08, 2016 8:33 AM
> To: lng-odp@lists.linaro.org; bill.fischo...@linaro.org; Elo, Matias
> (Nokia - FI/Espoo) <matias....@nokia-bell-labs.com>
> Subject: [lng-odp] [API-NEXT PATCH] linux-gen: scheduler: solve ordered
> context inversion
>
> For ordered queue, a thre
rsday, December 08, 2016 8:33 AM
> > To: lng-odp@lists.linaro.org; bill.fischo...@linaro.org; Elo, Matias
> > (Nokia - FI/Espoo) <matias....@nokia-bell-labs.com>
> > Subject: [lng-odp] [API-NEXT PATCH] linux-gen: scheduler: solve ordered
> > context inversion
> >
> > Fo
08, 2016 8:33 AM
> To: lng-odp@lists.linaro.org; bill.fischo...@linaro.org; Elo, Matias
> (Nokia - FI/Espoo) <matias@nokia-bell-labs.com>
> Subject: [lng-odp] [API-NEXT PATCH] linux-gen: scheduler: solve ordered
> context inversion
>
> For ordered queue, a thread consume
For ordered queue, a thread consumes events (dequeue) and
acquires its unique sequential context in two steps, non
atomic and preemptable.
This leads to potential ordered context inversion in case
the thread consumes prior events acquired subsequent context,
while the thread consumes subsequent
