Re: [lng-odp] odp_pool_param_t::num versus per-thread object caches

2016-01-20 Thread Zoltan Kiss
[mailto:bill.fischo...@linaro.org] *Sent:* Wednesday, January 13, 2016 1:55 PM *To:* Zoltan Kiss *Cc:* Savolainen, Petri (Nokia - FI/Espoo); lng-odp *Subject:* Re: [lng-odp] odp_pool_param_t::num versus per-thread object caches Linux-generic solves this problems with watermarks. As the shared pool depletes

Re: [lng-odp] odp_pool_param_t::num versus per-thread object caches

2016-01-14 Thread Savolainen, Petri (Nokia - FI/Espoo)
, January 13, 2016 1:55 PM To: Zoltan Kiss Cc: Savolainen, Petri (Nokia - FI/Espoo); lng-odp Subject: Re: [lng-odp] odp_pool_param_t::num versus per-thread object caches Linux-generic solves this problems with watermarks. As the shared pool depletes and hits its low watermark free() calls always

Re: [lng-odp] odp_pool_param_t::num versus per-thread object caches

2016-01-14 Thread Zoltan Kiss
to other pool types. -Petri *From:*EXT Bill Fischofer [mailto:bill.fischo...@linaro.org] *Sent:* Wednesday, January 13, 2016 1:55 PM *To:* Zoltan Kiss *Cc:* Savolainen, Petri (Nokia - FI/Espoo); lng-odp *Subject:* Re: [lng-odp] odp_pool_param_t::num versus per-thread object caches Linux-generic solves

Re: [lng-odp] odp_pool_param_t::num versus per-thread object caches

2016-01-13 Thread Bill Fischofer
Linux-generic solves this problems with watermarks. As the shared pool depletes and hits its low watermark free() calls always return elements back to the shared pool rather than the local cache until the shared pool reaches its high watermark. This ensures that elements cannot get "lost" in the