diff options
author | Huang Ying | 2011-07-13 13:14:24 +0800 |
---|---|---|
committer | Len Brown | 2011-08-03 11:15:57 -0400 |
commit | 7f184275aa306046fe7edcbef3229754f0d97402 (patch) | |
tree | e2f82957072dd1ada3a4bc6c0281a6296123d8a0 /crypto/cast5.c | |
parent | f49f23abf3dd786ddcac1c1e7db3c2013b07413f (diff) |
lib, Make gen_pool memory allocator lockless
This version of the gen_pool memory allocator supports lockless
operation.
This makes it safe to use in NMI handlers and other special
unblockable contexts that could otherwise deadlock on locks. This is
implemented by using atomic operations and retries on any conflicts.
The disadvantage is that there may be livelocks in extreme cases. For
better scalability, one gen_pool allocator can be used for each CPU.
The lockless operation only works if there is enough memory available.
If new memory is added to the pool a lock has to be still taken. So
any user relying on locklessness has to ensure that sufficient memory
is preallocated.
The basic atomic operation of this allocator is cmpxchg on long. On
architectures that don't have NMI-safe cmpxchg implementation, the
allocator can NOT be used in NMI handler. So code uses the allocator
in NMI handler should depend on CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG.
Signed-off-by: Huang Ying <ying.huang@intel.com>
Reviewed-by: Andi Kleen <ak@linux.intel.com>
Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'crypto/cast5.c')
0 files changed, 0 insertions, 0 deletions