Re: [lng-odp] [API-NEXT PATCH 2/2] validation: timer: don't utilize pool enirely

2016-01-27 Thread Zoltan Kiss
On 26/01/16 16:17, Ola Liljedahl wrote: On 26 January 2016 at 14:32, Zoltan Kiss mailto:zoltan.k...@linaro.org>> wrote: Hi Ola, Would you mind taking a look at this? Zoli On 22/01/16 18:24, Zoltan Kiss wrote: As per-thread caches might retain some elements, no par

Re: [lng-odp] [API-NEXT PATCH 2/2] validation: timer: don't utilize pool enirely

2016-01-27 Thread Ola Liljedahl
Also the subject line misspells "entirely". As this will show up in the log of commits, it should be correctly spelled. A better title would perhaps be "validation:timer: handle early exhaustion of pool". On 26 January 2016 at 17:17, Ola Liljedahl wrote: > > > On 26 January 2016 at 14:32, Zoltan

Re: [lng-odp] [API-NEXT PATCH 2/2] validation: timer: don't utilize pool enirely

2016-01-26 Thread Ola Liljedahl
On 26 January 2016 at 14:32, Zoltan Kiss wrote: > Hi Ola, > > Would you mind taking a look at this? > > Zoli > > On 22/01/16 18:24, Zoltan Kiss wrote: > >> As per-thread caches might retain some elements, no particular thread >> should assume that a certain amount of elements are available at any

Re: [lng-odp] [API-NEXT PATCH 2/2] validation: timer: don't utilize pool enirely

2016-01-26 Thread Zoltan Kiss
Hi Ola, Would you mind taking a look at this? Zoli On 22/01/16 18:24, Zoltan Kiss wrote: As per-thread caches might retain some elements, no particular thread should assume that a certain amount of elements are available at any time. Also, we can't reliable check the high watermark anymore. S

[lng-odp] [API-NEXT PATCH 2/2] validation: timer: don't utilize pool enirely

2016-01-22 Thread Zoltan Kiss
As per-thread caches might retain some elements, no particular thread should assume that a certain amount of elements are available at any time. Also, we can't reliable check the high watermark anymore. Signed-off-by: Zoltan Kiss --- test/validation/timer/timer.c | 27 +--