summaryrefslogtreecommitdiffstats
path: root/Documentation/input
diff options
context:
space:
mode:
authorTejun Heo <tj@kernel.org>2014-09-02 14:46:02 -0400
committerTejun Heo <tj@kernel.org>2014-09-02 14:46:02 -0400
commitb38d08f3181c5025a7ce84646494cc4748492a3b (patch)
tree3e20c06c7dfe6f8fb301e01c2a4a5dc0b55f911e /Documentation/input
parenta63d4ac4ab6094c051a5a240260d16117a7a2f86 (diff)
downloadblackbird-op-linux-b38d08f3181c5025a7ce84646494cc4748492a3b.tar.gz
blackbird-op-linux-b38d08f3181c5025a7ce84646494cc4748492a3b.zip
percpu: restructure locking
At first, the percpu allocator required a sleepable context for both alloc and free paths and used pcpu_alloc_mutex to protect everything. Later, pcpu_lock was introduced to protect the index data structure so that the free path can be invoked from atomic contexts. The conversion only updated what's necessary and left most of the allocation path under pcpu_alloc_mutex. The percpu allocator is planned to add support for atomic allocation and this patch restructures locking so that the coverage of pcpu_alloc_mutex is further reduced. * pcpu_alloc() now grab pcpu_alloc_mutex only while creating a new chunk and populating the allocated area. Everything else is now protected soley by pcpu_lock. After this change, multiple instances of pcpu_extend_area_map() may race but the function already implements sufficient synchronization using pcpu_lock. This also allows multiple allocators to arrive at new chunk creation. To avoid creating multiple empty chunks back-to-back, a new chunk is created iff there is no other empty chunk after grabbing pcpu_alloc_mutex. * pcpu_lock is now held while modifying chunk->populated bitmap. After this, all data structures are protected by pcpu_lock. Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'Documentation/input')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud