Messages in this thread |  | | Date | Wed, 13 Apr 2011 17:07:57 -0400 | From | Mathieu Desnoyers <> | Subject | Re: [PATCH -v3 3/4] lib, Make gen_pool memory allocator lockless |
| |
* Huang Ying (ying.huang@intel.com) wrote: [...] > + * rcu_read_lock and rcu_read_unlock is not used int gen_pool_alloc, > + * gen_pool_free, gen_pool_avail and gen_pool_size etc, because chunks > + * are only added into pool, not deleted from pool unless the pool > + * itself is destroyed. If chunk will be deleted from pool, > + * rcu_read_lock and rcu_read_unlock should be uses in these > + * functions.
So how do you protect between pool destruction and adding chunks into the pool ?
Thanks,
Mathieu
-- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com
|  |