locking/rwsem: Rwsem rearchitecture part 2
Subsystems (3)
Waiman Long
reviewerv5 cover locking/rwsem: Rwsem rearchitecture part 2
v5:
- Drop v4 patch 1 as it is merged into tip's locking/core branch.
- Integrate the 2 followup patches into the series. The first follow-up patch is broken into 2 pieces. The first piece comes in before the "Enable readers spinning on writer" and the 2nd piece is merged into the "Enable time-based spinning on reader-owned rwsem" patch. The 2nd followup patch is added after that.
- Add a new patch to make all wake_up_q() calls after dropping wait_lock as suggested by PeterZ.
- Incorporate numerouos suggestions by PeterZ and Davidlohr.
v4:
- Fix the missing initialization bug with !CONFIG_RWSEM_SPIN_ON_OWNER in patch 2.
- Move the "Remove rwsem_wake() wakeup optimization" patch before the "Implement a new locking scheme" patch.
- Add two new patches to merge the relevant content of rwsem.h and rwsem-xadd.c into rwsem.c as suggested by PeterZ.
- Refactor the lock handoff patch to make all setting and clearing of the handoff bit serialized by wait_lock to ensure correctness.
- Adapt the rest of the patches to the new code base.
v3:
- Add 2 more patches in front to fix build and testing issues found. Patch 1 can actually be merged on top of the patch "locking/rwsem:
Enhance DEBUG_RWSEMS_WARN_ON() macro" in part 1.
- Change the handoff patch (now patch 4) to set handoff bit immediately after wakeup for RT writers. The timeout limit is also tightened to 4ms.
- There is no code changes in other patches other than resolving conflicts with patches 1, 2 and 4.
v2:
- Move the negative reader count checking patch (patch 12->10) forward to before the merge owner to count patch as suggested by Linus & expand the comment.
- Change the reader-owned rwsem spinning from count based to time based to have better control of the max time allowed.
This is part 2 of a 3-part (0/1/2) series to rearchitect the internal operation of rwsem. Both part 0 and part 1 are merged into tip.
This patchset revamps the current rwsem-xadd implementation to make it saner and easier to work with. It also implements the following 3 new features:
1) Waiter lock handoff
2) Reader optimistic spinning with adapative disabling
3) Store write-lock owner in the atomic count (x86-64 only for now)
Waiter lock handoff is similar to the mechanism currently in the mutex code. This ensures that lock starvation won't happen.
Reader optimistic spinning enables readers to acquire the lock more quickly. So workloads that use a mix of readers and writers should see an increase in performance as long as the reader critical sections are short. For those workloads that have long reader critical sections reader optimistic spinning may hurt performance, so an adaptive disabling mechanism is also implemented to disable it when reader-owned lock spinning timeouts happen.
Finally, storing the write-lock owner into the count will allow optimistic spinners to get to the lock holder's task structure more quickly and eliminating the timing gap where the write lock is acquired but the owner isn't known yet. This is important for RT tasks where spinning on a lock with an unknown owner is not allowed.
Because of the fact that multiple readers can share the same lock, there is a natural preference for readers when measuring in term of locking throughput as more readers are likely to get into the locking fast path than the writers. With waiter lock handoff, we are not going to starve the writers.
On a 1-socket 22-core 44-thread Skylake system with 22 reader and writer locking threads, the min/mean/max locking operations done in a 5-second testing window before the patchset were:
22 readers, Iterations Min/Mean/Max = 38,193/38,194/38,194 22 writers, Iterations Min/Mean/Max = 104,663/162,133/261,370
After the patchset, they became:
22 readers, Iterations Min/Mean/Max = 520,981/560,847/631,603 22 writers, Iterations Min/Mean/Max = 230,567/241,565/276,940
So it was much fairer to readers.
Patch 1 makes owner a permanent member of the rw_semaphore structure and set it irrespective of CONFIG_RWSEM_SPIN_ON_OWNER.
Patch 2 removes rwsem_wake() wakeup optimization as it doesn't work with lock handoff.
Patch 3 implements a new rwsem locking scheme similar to what qrwlock is current doing. Write lock is done by atomic_cmpxchg() while read lock is still being done by atomic_add().
Patch 4 merges the content of rwsem.h and rwsem-xadd.c into rwsem.c just like the mutex. The rwsem-xadd.c is removed and a bare-bone rwsem.h is left for internal function declaration needed by percpu-rwsem.c.
Patch 5 optimizes the merged rwsem.c file to generate smaller object file and performs other miscellaneous code cleanups.
Patch 6 makes rwsem_spin_on_owner() returns owner state.
Patch 7 implments lock handoff to prevent lock starvation. It is expected that throughput will be lower on workloads with highly contended rwsems for better fairness.
Patch 8 makes sure that all wake_up_q() calls happened after dropping the wait_lock.
Patch 9 makes RT task's handling of NULL owner more optimal.
Patch 10 makes reader wakeup to wake up almost all the readers in the wait queue instead of just those in the front.
Patch 11 renames the RWSEM_ANONYMOUSLY_OWNED bit to RWSEM_NONSPINNABLE.
Patch 12 enables reader to spin on a writer-owned rwsem.
Patch 13 enables a writer to spin on a reader-owned rwsem for at most 25us and extends the RWSEM_NONSPINNABLE bit to 2 separate ones - one for readers and one for writers.
Patch 14 implements the adaptive disabling of reader optimistic spinning when the reader-owned rwsem spinning timeouts happen.
Patch 15 adds some new rwsem owner access helper functions.
Patch 16 handles the case of too many readers by reserving the sign bit to designate that a reader lock attempt will fail and the locking reader will be put to sleep. This will ensure that we will not overflow the reader count.
Patch 17 merges the write-lock owner task pointer into the count. Only 64-bit count has enough space to provide a reasonable number of bits for reader count. This is for x86-64 only for the time being.
Patch 18 eliminates redundant computation of the merged owner-count.
With a locking microbenchmark running on 5.1 based kernel, the total locking rates (in kops/s) on a 1-socket Skylake system with equal numbers of readers and writers (mixed) before and after this patchset were:
# of Threads Before Patch After Patch
------------ ------------ -----------
2 1,566 4,750
4 1,191 3,972
8 825 3,871
16 744 3,405
32 691 3,243
44 672 3,217On workloads where the rwsem reader critical section is relatively long (longer than the spinning period), optimistic of writer on reader-owned rwsem may not be that helpful. In fact, the performance may regress in some cases like the will-it-sclae page_fault1 microbenchmark. This is likely due to the fact that larger reader groups where the readers acquire the lock together are broken into smaller ones. So more work will be needed to better tune the rwsem code to that kind of workload.
Waiman Long (18):
locking/rwsem: Make owner available even if
!CONFIG_RWSEM_SPIN_ON_OWNER
locking/rwsem: Remove rwsem_wake() wakeup optimization locking/rwsem: Implement a new locking scheme locking/rwsem: Merge rwsem.h and rwsem-xadd.c into rwsem.c locking/rwsem: Code cleanup after files merging locking/rwsem: Make rwsem_spin_on_owner() return owner state locking/rwsem: Implement lock handoff to prevent lock starvation locking/rwsem: Always release wait_lock before waking up tasks locking/rwsem: More optimal RT task handling of null owner locking/rwsem: Wake up almost all readers in wait queue locking/rwsem: Clarify usage of owner's nonspinaable bit locking/rwsem: Enable readers spinning on writer locking/rwsem: Enable time-based spinning on reader-owned rwsem locking/rwsem: Adaptive disabling of reader optimistic spinning locking/rwsem: Add more rwsem owner access helpers locking/rwsem: Guard against making count negative locking/rwsem: Merge owner into count on x86-64 locking/rwsem: Remove redundant computation of writer lock word
arch/x86/Kconfig | 6 + include/linux/rwsem.h | 11 +- include/linux/sched/wake_q.h | 5 + kernel/Kconfig.locks | 12 + kernel/locking/Makefile | 2 +- kernel/locking/lock_events_list.h | 11 +- kernel/locking/rwsem-xadd.c | 729 -------------- kernel/locking/rwsem.c | 1473 ++++++++++++++++++++++++++++- kernel/locking/rwsem.h | 306 +----- lib/Kconfig.debug | 8 +- 10 files changed, 1493 insertions(+), 1070 deletions(-) delete mode 100644 kernel/locking/rwsem-xadd.c
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 1/18 locking/rwsem: Make owner available even if !CONFIG_RWSEM_SPIN_ON_OWNER
The owner field in the rw_semaphore structure is used primarily for optimistic spinning. However, identifying the rwsem owner can also be helpful in debugging as well as tracing locking related issues when analyzing crash dump. The owner field may also store state information that can be important to the operation of the rwsem.
So the owner field is now made a permanent member of the rw_semaphore structure irrespective of CONFIG_RWSEM_SPIN_ON_OWNER.
--- include/linux/rwsem.h | 9 +++++---- kernel/locking/rwsem-xadd.c | 2 +- kernel/locking/rwsem.h | 23 ----------------------- lib/Kconfig.debug | 8 ++++---- 4 files changed, 10 insertions(+), 32 deletions(-)
include/linux/rwsem.h +5 -4
@@ -34,12 +34,12 @@*/ struct rw_semaphore {atomic_long_t count; -#ifdef CONFIG_RWSEM_SPIN_ON_OWNER /* -* Write owner. Used as a speculative check to see -* if the owner is running on the cpu. +* Write owner or one of the read owners. Can be used as a +* speculative check to see if the owner is running on the cpu. */ struct task_struct *owner; +#ifdef CONFIG_RWSEM_SPIN_ON_OWNER struct optimistic_spin_queue osq;/* spinner MCS lock */ #endif raw_spinlock_t wait_lock;
@@ -73,13 +73,14 @@ static inline int rwsem_is_locked(struct rw_semaphore *sem)#endif #ifdef CONFIG_RWSEM_SPIN_ON_OWNER -#define __RWSEM_OPT_INIT (lockname) , .osq = OSQ_LOCK_UNLOCKED, .owner = NULL +#define __RWSEM_OPT_INIT (lockname) , .osq = OSQ_LOCK_UNLOCKED#else #define __RWSEM_OPT_INIT (lockname)#endif #define __RWSEM_INITIALIZER (name) \ { __RWSEM_INIT_COUNT(name), \ + .owner = NULL, \ .wait_list = LIST_HEAD_INIT((name).wait_list), \ .wait_lock = __RAW_SPIN_LOCK_UNLOCKED(name.wait_lock) \ __RWSEM_OPT_INIT(name) \
kernel/locking/rwsem-xadd.c +1 -1
@@ -86,8 +86,8 @@ void __init_rwsem(struct rw_semaphore *sem, const char *name,atomic_long_set (&sem->count,RWSEM_UNLOCKED_VALUE );raw_spin_lock_init (&sem->wait_lock);INIT_LIST_HEAD (&sem->wait_list); -#ifdef CONFIG_RWSEM_SPIN_ON_OWNER sem->owner =NULL ; +#ifdef CONFIG_RWSEM_SPIN_ON_OWNER osq_lock_init (&sem->osq);#endif }
kernel/locking/rwsem.h +0 -23
@@ -61,7 +61,6 @@#define RWSEM_ACTIVE_READ_BIAS RWSEM_ACTIVE_BIAS#define RWSEM_ACTIVE_WRITE_BIAS (RWSEM_WAITING_BIAS + RWSEM_ACTIVE_BIAS) -#ifdef CONFIG_RWSEM_SPIN_ON_OWNER /* * All writes to owner are protected by WRITE_ONCE() to make sure that * store tearing can't happen as optimistic spinners may read and use
@@ -126,7 +125,6 @@ static inline bool rwsem_has_anonymous_owner(struct task_struct *owner)* real owner or one of the real owners. The only exception is when the * unlock is done by up_read_non_owner(). */ -#define rwsem_clear_reader_owned rwsem_clear_reader_ownedstatic inline void rwsem_clear_reader_owned (struct rw_semaphore *sem) {unsigned long val = (unsigned long )current |RWSEM_READER_OWNED
@@ -135,28 +133,7 @@ static inline void rwsem_clear_reader_owned(struct rw_semaphore *sem)cmpxchg_relaxed ((unsigned long *)&sem->owner, val, RWSEM_READER_OWNED | RWSEM_ANONYMOUSLY_OWNED); } -#endif -#else -static inline void rwsem_set_owner (struct rw_semaphore *sem) -{ -} - -static inline void rwsem_clear_owner (struct rw_semaphore *sem) -{ -} - -static inline void __rwsem_set_reader_owned (struct rw_semaphore *sem, -struct task_struct *owner) -{ -} - -static inline void rwsem_set_reader_owned (struct rw_semaphore *sem) -{ -} -#endif - -#ifndef rwsem_clear_reader_ownedstatic inline void rwsem_clear_reader_owned (struct rw_semaphore *sem) { }
lib/Kconfig.debug +4 -4
@@ -1067,7 +1067,7 @@ config PROVE_LOCKING select DEBUG_SPINLOCK select DEBUG_MUTEXES select DEBUG_RT_MUTEXES if RT_MUTEXES - select DEBUG_RWSEMS if RWSEM_SPIN_ON_OWNER + select DEBUG_RWSEMS select DEBUG_WW_MUTEX_SLOWPATH select DEBUG_LOCK_ALLOC select TRACE_IRQFLAGS
@@ -1171,10 +1171,10 @@ config DEBUG_WW_MUTEX_SLOWPATH config DEBUG_RWSEMS bool "RW Semaphore debugging: basic checks" - depends on DEBUG_KERNEL && RWSEM_SPIN_ON_OWNER + depends on DEBUG_KERNEL help - This debugging feature allows mismatched rw semaphore locks and unlocks - to be detected and reported. + This debugging feature allows mismatched rw semaphore locks + and unlocks to be detected and reported. config DEBUG_LOCK_ALLOC bool "Lock debugging: detect incorrect freeing of live locks"
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 2/18 locking/rwsem: Remove rwsem_wake() wakeup optimization
In reply to Waiman LongWith the commit 59aabfc7e959 ("locking/rwsem: Reduce spinlock contention in wakeup after up_read()/up_write()"), the rwsem_wake() forgoes doing a wakeup if the wait_lock cannot be directly acquired and an optimistic spinning locker is present. This can help performance by avoiding spinning on the wait_lock when it is contended.
With the later commit 133e89ef5ef3 ("locking/rwsem: Enable lockless waiter wakeup(s)"), the performance advantage of the above optimization diminishes as the average wait_lock hold time become much shorter.
With a later patch that supports rwsem lock handoff, we can no longer relies on the fact that the presence of an optimistic spinning locker will ensure that the lock will be acquired by a task soon and rwsem_wake() will be called later on to wake up waiters. This can lead to missed wakeup and application hang. So the commit 59aabfc7e959 ("locking/rwsem: Reduce spinlock contention in wakeup after up_read()/up_write()") will have to be reverted.
--- kernel/locking/rwsem-xadd.c | 72 ------------------------------------- 1 file changed, 72 deletions(-)
kernel/locking/rwsem-xadd.c +0 -72
@@ -395,25 +395,11 @@ static bool rwsem_optimistic_spin(struct rw_semaphore *sem)lockevent_cond_inc (rwsem_opt_fail, !taken); return taken; } - -/* -* Return true if the rwsem has active spinner -*/ -static inline bool rwsem_has_spinner (struct rw_semaphore *sem) -{ -return osq_is_locked (&sem->osq); -} -#else static bool rwsem_optimistic_spin (struct rw_semaphore *sem) {return false; } - -static inline bool rwsem_has_spinner (struct rw_semaphore *sem) -{ -return false; -}#endif /*
@@ -635,65 +621,7 @@ struct rw_semaphore *rwsem_wake(struct rw_semaphore *sem)unsigned long flags;DEFINE_WAKE_Q (wake_q); -/* -* __rwsem_down_write_failed_common(sem) -* rwsem_optimistic_spin(sem) -* osq_unlock(sem->osq) -* ... -* atomic_long_add_return(&sem->count) -* -* - VS - -* -* __up_write() -* if (atomic_long_sub_return_release(&sem->count) < 0) -* rwsem_wake(sem) -* osq_is_locked(&sem->osq) -* -* And __up_write() must observe !osq_is_locked() when it observes the -* atomic_long_add_return() in order to not miss a wakeup. -* -* This boils down to: -* -* [S.rel] X = 1 [RmW] r0 = (Y += 0) -* MB RMB -* [RmW] Y += 1 [L] r1 = X -* -* exists (r0=1 /\ r1=0) -*/ -smp_rmb (); - -/* -* If a spinner is present, it is not necessary to do the wakeup. -* Try to do wakeup only if the trylock succeeds to minimize -* spinlock contention which may introduce too much delay in the -* unlock operation. -* -* spinning writer up_write/up_read caller -* --------------- ----------------------- -* [S] osq_unlock() [L] osq -* MB RMB -* [RmW] rwsem_try_write_lock() [RmW] spin_trylock(wait_lock) -* -* Here, it is important to make sure that there won't be a missed -* wakeup while the rwsem is free and the only spinning writer goes -* to sleep without taking the rwsem. Even when the spinning writer -* is just going to break out of the waiting loop, it will still do -* a trylock in rwsem_down_write_failed() before sleeping. IOW, if -* rwsem_has_spinner() is true, it will guarantee at least one -* trylock attempt on the rwsem later on. -*/ -if (rwsem_has_spinner (sem)) { -/* -* The smp_rmb() here is to make sure that the spinner -* state is consulted before reading the wait_lock. -*/ -smp_rmb (); -if (!raw_spin_trylock_irqsave (&sem->wait_lock, flags)) -return sem; - goto locked; - }raw_spin_lock_irqsave (&sem->wait_lock, flags); -locked:if (!list_empty (&sem->wait_list))__rwsem_mark_wake (sem,RWSEM_WAKE_ANY , &wake_q);
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 3/18 locking/rwsem: Implement a new locking scheme
In reply to Waiman LongThe current way of using various reader, writer and waiting biases in the rwsem code are confusing and hard to understand. I have to reread the rwsem count guide in the rwsem-xadd.c file from time to time to remind myself how this whole thing works. It also makes the rwsem code harder to be optimized.
To make rwsem more sane, a new locking scheme similar to the one in qrwlock is now being used. The atomic long count has the following bit definitions:
Bit 0 - writer locked bit Bit 1 - waiters present bit
Bits 2-7 - reserved for future extension
Bits 8-X - reader count (24/56 bits)
The cmpxchg instruction is now used to acquire the write lock. The read lock is still acquired with xadd instruction, so there is no change here. This scheme will allow up to 16M/64P active readers which should be more than enough. We can always use some more reserved bits if necessary.
With that change, we can deterministically know if a rwsem has been write-locked. Looking at the count alone, however, one cannot determine for certain if a rwsem is owned by readers or not as the readers that set the reader count bits may be in the process of backing out. So we still need the reader-owned bit in the owner field to be sure.
With a locking microbenchmark running on 5.1 based kernel, the total locking rates (in kops/s) of the benchmark on a 8-socket 120-core IvyBridge-EX system before and after the patch were as follows:
Before Patch After Patch
# of Threads wlock rlock wlock rlock
------------ ----- ----- ----- -----
1 30,659 31,341 31,055 31,283
2 8,909 16,457 9,884 17,659
4 9,028 15,823 8,933 20,233
8 8,410 14,212 7,230 17,140
16 8,217 25,240 7,479 24,607The locking rates of the benchmark on a Power8 system were as follows:
Before Patch After Patch
# of Threads wlock rlock wlock rlock
------------ ----- ----- ----- -----
1 12,963 13,647 13,275 13,601
2 7,570 11,569 7,902 10,829
4 5,232 5,516 5,466 5,435
8 5,233 3,386 5,467 3,168The locking rates of the benchmark on a 2-socket ARM64 system were as follows:
Before Patch After Patch
# of Threads wlock rlock wlock rlock
------------ ----- ----- ----- -----
1 21,495 21,046 21,524 21,074
2 5,293 10,502 5,333 10,504
4 5,325 11,463 5,358 11,631
8 5,391 11,712 5,470 11,680The performance are roughly the same before and after the patch. There are run-to-run variations in performance. Runs with higher variances usually have higher throughput.
--- kernel/locking/rwsem-xadd.c | 147 ++++++++++++------------------------ kernel/locking/rwsem.h | 74 +++++++++--------- 2 files changed, 85 insertions(+), 136 deletions(-)
kernel/locking/rwsem-xadd.c +49 -98
@@ -9,6 +9,8 @@* * Optimistic spinning by Tim Chen <[email protected]> * and Davidlohr Bueso <[email protected]>. Based on mutexes. +* +* Rwsem count bit fields re-definition by Waiman Long <[email protected]>. */ #include <linux/rwsem.h> #include <linux/init.h>
@@ -22,52 +24,20 @@#include "rwsem.h" /* -* Guide to the rw_semaphore's count field for common values. -* (32-bit case illustrated, similar for 64-bit) -* -* 0x0000000X (1) X readers active or attempting lock, no writer waiting -* X = #active_readers + #readers attempting to lock -* (X*ACTIVE_BIAS) -* -* 0x00000000 rwsem is unlocked, and no one is waiting for the lock or -* attempting to read lock or write lock. -* -* 0xffff000X (1) X readers active or attempting lock, with waiters for lock -* X = #active readers + # readers attempting lock -* (X*ACTIVE_BIAS + WAITING_BIAS) -* (2) 1 writer attempting lock, no waiters for lock -* X-1 = #active readers + #readers attempting lock -* ((X-1)*ACTIVE_BIAS + ACTIVE_WRITE_BIAS) -* (3) 1 writer active, no waiters for lock -* X-1 = #active readers + #readers attempting lock -* ((X-1)*ACTIVE_BIAS + ACTIVE_WRITE_BIAS) -* -* 0xffff0001 (1) 1 reader active or attempting lock, waiters for lock -* (WAITING_BIAS + ACTIVE_BIAS) -* (2) 1 writer active or attempting lock, no waiters for lock -* (ACTIVE_WRITE_BIAS) +* Guide to the rw_semaphore's count field. * -* 0xffff0000 (1) There are writers or readers queued but none active -* or in the process of attempting lock. -* (WAITING_BIAS) -* Note: writer can attempt to steal lock for this count by adding -* ACTIVE_WRITE_BIAS in cmpxchg and checking the old count +* When the RWSEM_WRITER_LOCKED bit in count is set, the lock is owned +* by a writer. * -* 0xfffe0001 (1) 1 writer active, or attempting lock. Waiters on queue. -* (ACTIVE_WRITE_BIAS + WAITING_BIAS) -* -* Note: Readers attempt to lock by adding ACTIVE_BIAS in down_read and checking -* the count becomes more than 0 for successful lock acquisition, -* i.e. the case where there are only readers or nobody has lock. -* (1st and 2nd case above). -* -* Writers attempt to lock by adding ACTIVE_WRITE_BIAS in down_write and -* checking the count becomes ACTIVE_WRITE_BIAS for successful lock -* acquisition (i.e. nobody else has lock or attempts lock). If -* unsuccessful, in rwsem_down_write_failed, we'll check to see if there -* are only waiters but none active (5th case above), and attempt to -* steal the lock. +* The lock is owned by readers when +* (1) the RWSEM_WRITER_LOCKED isn't set in count, +* (2) some of the reader bits are set in count, and +* (3) the owner field has RWSEM_READ_OWNED bit set. * +* Having some reader bits set is not enough to guarantee a readers owned +* lock as the readers may be in the process of backing out from the count +* and a writer has just released the lock. So another writer may steal +* the lock immediately after that. */ /*
@@ -113,9 +83,8 @@ enum rwsem_wake_type {/* * handle the lock release when processes blocked on it that can now run -* - if we come here from up_xxxx(), then: -* - the 'active part' of count (&0x0000ffff) reached 0 (but may have changed) -* - the 'waiting part' of count (&0xffff0000) is -ve (and will still be so) +* - if we come here from up_xxxx(), then the RWSEM_FLAG_WAITERS bit must +* have been set. * - there must be someone on the queue * - the wait_lock must be held by the caller * - tasks are marked for wakeup, the caller must later invoke wake_up_q()
@@ -159,22 +128,11 @@ static void __rwsem_mark_wake(struct rw_semaphore *sem,* so we can bail out early if a writer stole the lock. */ if (wake_type !=RWSEM_WAKE_READ_OWNED ) { - adjustment =RWSEM_ACTIVE_READ_BIAS ; - try_reader_grant: + adjustment =RWSEM_READER_BIAS ; oldcount =atomic_long_fetch_add (adjustment, &sem->count); -if (unlikely (oldcount <RWSEM_WAITING_BIAS )) { -/* -* If the count is still less than RWSEM_WAITING_BIAS -* after removing the adjustment, it is assumed that -* a writer has stolen the lock. We have to undo our -* reader grant. -*/ -if (atomic_long_add_return (-adjustment, &sem->count) < -RWSEM_WAITING_BIAS ) -return ; - -/* Last active locker left. Retry waking readers. */ - goto try_reader_grant; +if (unlikely (oldcount &RWSEM_WRITER_MASK )) { +atomic_long_sub (adjustment, &sem->count); +return ; }/* * Set it to reader-owned to give spinners an early
@@ -214,11 +172,11 @@ static void __rwsem_mark_wake(struct rw_semaphore *sem,wake_q_add_safe (wake_q, tsk); } - adjustment = woken *RWSEM_ACTIVE_READ_BIAS - adjustment; + adjustment = woken *RWSEM_READER_BIAS - adjustment;lockevent_cond_inc (rwsem_wake_reader, woken);if (list_empty (&sem->wait_list)) {/* hit end of list above */ - adjustment -=RWSEM_WAITING_BIAS ; + adjustment -=RWSEM_FLAG_WAITERS ; }if (adjustment)
@@ -232,22 +190,15 @@ static void __rwsem_mark_wake(struct rw_semaphore *sem,*/ static inline bool rwsem_try_write_lock (long count,struct rw_semaphore *sem) { -/* -* Avoid trying to acquire write lock if count isn't RWSEM_WAITING_BIAS. -*/ -if (count !=RWSEM_WAITING_BIAS ) +long new; + +if (count &RWSEM_LOCK_MASK )return false; -/* -* Acquire the lock by trying to set it to ACTIVE_WRITE_BIAS. If there -* are other tasks on the wait list, we need to add on WAITING_BIAS. -*/ - count =list_is_singular (&sem->wait_list) ? -RWSEM_ACTIVE_WRITE_BIAS : -RWSEM_ACTIVE_WRITE_BIAS +RWSEM_WAITING_BIAS ; + new = count +RWSEM_WRITER_LOCKED - + (list_is_singular (&sem->wait_list) ?RWSEM_FLAG_WAITERS :0 ); -if (atomic_long_cmpxchg_acquire (&sem->count,RWSEM_WAITING_BIAS , count) - ==RWSEM_WAITING_BIAS ) { +if (atomic_long_try_cmpxchg_acquire (&sem->count, &count, new)) {rwsem_set_owner (sem);return true; }
@@ -263,9 +214,9 @@ static inline bool rwsem_try_write_lock_unqueued(struct rw_semaphore *sem) {long count =atomic_long_read (&sem->count); -while (!count || count ==RWSEM_WAITING_BIAS ) { +while (!(count &RWSEM_LOCK_MASK )) {if (atomic_long_try_cmpxchg_acquire (&sem->count, &count, - count +RWSEM_ACTIVE_WRITE_BIAS )) { + count +RWSEM_WRITER_LOCKED )) {rwsem_set_owner (sem);lockevent_inc (rwsem_opt_wlock);return true;
@@ -408,7 +359,7 @@ static bool rwsem_optimistic_spin(struct rw_semaphore *sem) static inline struct rw_semaphore __sched *__rwsem_down_read_failed_common (struct rw_semaphore *sem,int state) { -long count, adjustment = -RWSEM_ACTIVE_READ_BIAS ; +long count, adjustment = -RWSEM_READER_BIAS ;struct rwsem_waiter waiter;DEFINE_WAKE_Q (wake_q);
@@ -420,16 +371,16 @@ __rwsem_down_read_failed_common(struct rw_semaphore *sem, int state)/* * In case the wait queue is empty and the lock isn't owned * by a writer, this reader can exit the slowpath and return -* immediately as its RWSEM_ACTIVE_READ_BIAS has already -* been set in the count. +* immediately as its RWSEM_READER_BIAS has already been +* set in the count. */ -if (atomic_long_read (&sem->count) >=0 ) { +if (!(atomic_long_read (&sem->count) &RWSEM_WRITER_MASK )) {raw_spin_unlock_irq (&sem->wait_lock);rwsem_set_reader_owned (sem);lockevent_inc (rwsem_rlock_fast);return sem; } - adjustment +=RWSEM_WAITING_BIAS ; + adjustment +=RWSEM_FLAG_WAITERS ; }list_add_tail (&waiter.list, &sem->wait_list);
@@ -442,9 +393,8 @@ __rwsem_down_read_failed_common(struct rw_semaphore *sem, int state)* If there are no writers and we are first in the queue, * wake our own waiter to join the existing active readers ! */ -if (count ==RWSEM_WAITING_BIAS || - (count >RWSEM_WAITING_BIAS && - adjustment != -RWSEM_ACTIVE_READ_BIAS )) +if (!(count &RWSEM_LOCK_MASK ) || + (!(count &RWSEM_WRITER_MASK ) && (adjustment &RWSEM_FLAG_WAITERS )))__rwsem_mark_wake (sem,RWSEM_WAKE_ANY , &wake_q);raw_spin_unlock_irq (&sem->wait_lock);
@@ -472,7 +422,7 @@ __rwsem_down_read_failed_common(struct rw_semaphore *sem, int state) out_nolock:list_del (&waiter.list);if (list_empty (&sem->wait_list)) -atomic_long_add (-RWSEM_WAITING_BIAS , &sem->count); +atomic_long_andnot (RWSEM_FLAG_WAITERS , &sem->count);raw_spin_unlock_irq (&sem->wait_lock);__set_current_state (TASK_RUNNING );lockevent_inc (rwsem_rlock_fail);
@@ -505,9 +455,6 @@ __rwsem_down_write_failed_common(struct rw_semaphore *sem, int state)struct rw_semaphore *ret = sem;DEFINE_WAKE_Q (wake_q); -/* undo write bias from down_write operation, stop active locking */ - count =atomic_long_sub_return (RWSEM_ACTIVE_WRITE_BIAS , &sem->count); -/* do optimistic spinning and steal lock if possible */ if (rwsem_optimistic_spin (sem))return sem;
@@ -527,16 +474,18 @@ __rwsem_down_write_failed_common(struct rw_semaphore *sem, int state)list_add_tail (&waiter.list, &sem->wait_list); -/* we're now waiting on the lock, but no longer actively locking */ +/* we're now waiting on the lock */ if (waiting) { count =atomic_long_read (&sem->count);/* * If there were already threads queued before us and there are -* no active writers, the lock must be read owned; so we try to -* wake any read locks that were queued ahead of us. +* no active writers and some readers, the lock must be read +* owned; so we try to any read locks that were queued ahead +* of us. */ -if (count >RWSEM_WAITING_BIAS ) { +if (!(count &RWSEM_WRITER_MASK ) && + (count &RWSEM_READER_MASK )) {__rwsem_mark_wake (sem,RWSEM_WAKE_READERS , &wake_q);/* * The wakeup is normally called _after_ the wait_lock
@@ -553,8 +502,9 @@ __rwsem_down_write_failed_common(struct rw_semaphore *sem, int state)wake_q_init (&wake_q); } - }else - count =atomic_long_add_return (RWSEM_WAITING_BIAS , &sem->count); + }else { + count =atomic_long_add_return (RWSEM_FLAG_WAITERS , &sem->count); + }/* wait until we successfully acquire the lock */ set_current_state (state);
@@ -571,7 +521,8 @@ __rwsem_down_write_failed_common(struct rw_semaphore *sem, int state)schedule ();lockevent_inc (rwsem_sleep_writer);set_current_state (state); - }while ((count =atomic_long_read (&sem->count)) &RWSEM_ACTIVE_MASK ); + count =atomic_long_read (&sem->count); + }while (count &RWSEM_LOCK_MASK );raw_spin_lock_irq (&sem->wait_lock); }
@@ -587,7 +538,7 @@ __rwsem_down_write_failed_common(struct rw_semaphore *sem, int state)raw_spin_lock_irq (&sem->wait_lock);list_del (&waiter.list);if (list_empty (&sem->wait_list)) -atomic_long_add (-RWSEM_WAITING_BIAS , &sem->count); +atomic_long_andnot (RWSEM_FLAG_WAITERS , &sem->count);else __rwsem_mark_wake (sem,RWSEM_WAKE_ANY , &wake_q);raw_spin_unlock_irq (&sem->wait_lock);
kernel/locking/rwsem.h +36 -38
138 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 4/18 locking/rwsem: Merge rwsem.h and rwsem-xadd.c into rwsem.c
In reply to Waiman LongNow we only have one implementation of rwsem. Even though we still use xadd to handle reader locking, we use cmpxchg for writer instead. So the filename rwsem-xadd.c is not strictly correct. Also no one outside of the rwsem code need to know the internal implementation other than function prototypes for two internal functions that are called directly from percpu-rwsem.c.
So the rwsem-xadd.c and rwsem.h files are now merged into rwsem.c in the following order:
<upper part of rwsem.h>
<rwsem-xadd.c>
<lower part of rwsem.h>
<rwsem.c>
The rwsem.h file now contains only 2 function declarations for __up_read() and __down_read().
This is a code relocation patch with no code change at all except making __up_read() and __down_read() non-static functions so they can be used by percpu-rwsem.c.
--- kernel/locking/Makefile | 2 +- kernel/locking/rwsem-xadd.c | 608 ------------------------- kernel/locking/rwsem.c | 868 ++++++++++++++++++++++++++++++++++++ kernel/locking/rwsem.h | 281 +----------- 4 files changed, 875 insertions(+), 884 deletions(-) delete mode 100644 kernel/locking/rwsem-xadd.c
kernel/locking/Makefile +1 -1
@@ -3,7 +3,7 @@ # and is generally not a function of system call inputs. KCOV_INSTRUMENT := n -obj-y += mutex.o semaphore.o rwsem.o percpu-rwsem.o rwsem-xadd.o +obj-y += mutex.o semaphore.o rwsem.o percpu-rwsem.o ifdef CONFIG_FUNCTION_TRACER CFLAGS_REMOVE_lockdep.o = $(CC_FLAGS_FTRACE)
kernel/locking/rwsem-xadd.c deleted +0 -608
608 lines not on this page · raw message
kernel/locking/rwsem.c +868 -0
885 lines not on this page · raw message
kernel/locking/rwsem.h +6 -275
285 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 5/18 locking/rwsem: Code cleanup after files merging
In reply to Waiman LongAfter merging all the relevant rwsem code into one single file, there are a number of optimizations and cleanups that can be done:
1) Remove all the EXPORT_SYMBOL() calls for functions that are not accessed elsewhere.
2) Remove all the __visible tags as none of the functions will be called from assembly code anymore.
3) Make all the internal functions static.
4) Remove some unneeded blank lines.
5) Remove the intermediate rwsem_down_{read|write}_failed*() functions and rename __rwsem_down_{read|write}_failed_common() to rwsem_down_{read|write}_slowpath().
6) Use atomic_long_try_cmpxchg_acquire() as much as possible.
7) Remove the rwsem_rtrylock and rwsem_wtrylock lock events as they are not that useful.
That enables the compiler to do better optimization and reduce code size. The text+data size of rwsem.o on an x86-64 machine with gcc8 was reduced from 10237 bytes to 5030 bytes with this change.
--- kernel/locking/lock_events_list.h | 2 - kernel/locking/rwsem.c | 119 +++++++++--------------------- 2 files changed, 34 insertions(+), 87 deletions(-)
kernel/locking/lock_events_list.h +0 -2
@@ -61,7 +61,5 @@ LOCK_EVENT(rwsem_opt_fail) /* # of failed opt-spinnings */ LOCK_EVENT(rwsem_rlock) /* # of read locks acquired */ LOCK_EVENT(rwsem_rlock_fast) /* # of fast read locks acquired */ LOCK_EVENT(rwsem_rlock_fail) /* # of failed read lock acquisitions */ -LOCK_EVENT(rwsem_rtrylock) /* # of read trylock calls */ LOCK_EVENT(rwsem_wlock) /* # of write locks acquired */ LOCK_EVENT(rwsem_wlock_fail) /* # of failed write lock acquisitions */ -LOCK_EVENT(rwsem_wtrylock) /* # of write trylock calls */
kernel/locking/rwsem.c +34 -85
345 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 6/18 locking/rwsem: Make rwsem_spin_on_owner() return owner state
In reply to Waiman LongThis patch modifies rwsem_spin_on_owner() to return four possible values to better reflect the state of lock holder which enables us to make a better decision of what to do next.
--- kernel/locking/rwsem.c | 65 ++++++++++++++++++++++++++++++------------ 1 file changed, 47 insertions(+), 18 deletions(-)
kernel/locking/rwsem.c +47 -18
@@ -398,17 +398,54 @@ static inline bool rwsem_can_spin_on_owner(struct rw_semaphore *sem) }/* -* Return true only if we can still spin on the owner field of the rwsem. +* The rwsem_spin_on_owner() function returns the folowing 4 values +* depending on the lock owner state. +* OWNER_NULL : owner is currently NULL +* OWNER_WRITER: when owner changes and is a writer +* OWNER_READER: when owner changes and the new owner may be a reader. +* OWNER_NONSPINNABLE: +* when optimistic spinning has to stop because either the +* owner stops running, is unknown, or its timeslice has +* been used up. */ -static noinline bool rwsem_spin_on_owner(struct rw_semaphore *sem) +enum owner_state { +OWNER_NULL =1 <<0 , +OWNER_WRITER =1 <<1 , +OWNER_READER =1 <<2 , +OWNER_NONSPINNABLE =1 <<3 , +}; +#define OWNER_SPINNABLE (OWNER_NULL | OWNER_WRITER) + +static inline enum owner_state rwsem_owner_state (unsigned long owner) { -struct task_struct *owner =READ_ONCE (sem->owner); +if (!owner) +return OWNER_NULL ; -if (!is_rwsem_owner_spinnable (owner)) -return false; +if (owner &RWSEM_ANONYMOUSLY_OWNED ) +return OWNER_NONSPINNABLE ; + +if (owner &RWSEM_READER_OWNED ) +return OWNER_READER ; + +return OWNER_WRITER ; +} + +static noinline enum owner_state rwsem_spin_on_owner(struct rw_semaphore *sem) +{ +struct task_struct *tmp, *owner =READ_ONCE (sem->owner); +enum owner_state state =rwsem_owner_state ((unsigned long )owner); + +if (state !=OWNER_WRITER ) +return state;rcu_read_lock (); -while (owner && (READ_ONCE (sem->owner) == owner)) { +for (;;) { + tmp =READ_ONCE (sem->owner); +if (tmp != owner) { + state =rwsem_owner_state ((unsigned long )tmp); +break ; + } +/* * Ensure we emit the owner->on_cpu, dereference _after_ * checking sem->owner still matches owner, if that fails,
@@ -417,24 +454,16 @@ static noinline bool rwsem_spin_on_owner(struct rw_semaphore *sem)*/ barrier (); -/* -* abort spinning when need_resched or owner is not running or -* owner's cpu is preempted. -*/ if (need_resched () || !owner_on_cpu (owner)) { -rcu_read_unlock (); -return false; + state =OWNER_NONSPINNABLE ; +break ; }cpu_relax (); }rcu_read_unlock (); -/* -* If there is a new owner or the owner is not set, we continue -* spinning. -*/ -return is_rwsem_owner_spinnable (READ_ONCE (sem->owner)); +return state; }static bool rwsem_optimistic_spin (struct rw_semaphore *sem)
@@ -457,7 +486,7 @@ static bool rwsem_optimistic_spin(struct rw_semaphore *sem)* 2) readers own the lock as we can't determine if they are * actively running or not. */ -while (rwsem_spin_on_owner (sem)) { +while (rwsem_spin_on_owner (sem) &OWNER_SPINNABLE ) {/* * Try to acquire the lock */
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 7/18 locking/rwsem: Implement lock handoff to prevent lock starvation
In reply to Waiman LongBecause of writer lock stealing, it is possible that a constant stream of incoming writers will cause a waiting writer or reader to wait indefinitely leading to lock starvation.
This patch implements a lock handoff mechanism to disable lock stealing and force lock handoff to the first waiter or waiters (for readers) in the queue after at least a 4ms waiting period unless it is a RT writer task which doesn't need to wait. The waiting period is used to avoid discouraging lock stealing too much to affect performance.
The setting and clearing of the handoff bit is serialized by the wait_lock. So racing is not possible.
A rwsem microbenchmark was run for 5 seconds on a 2-socket 40-core 80-thread Skylake system with a v5.1 based kernel and 240 write_lock threads with 5us sleep critical section.
Before the patch, the min/mean/max numbers of locking operations for the locking threads were 1/7,792/173,696. After the patch, the figures became 5,842/6,542/7,458. It can be seen that the rwsem became much more fair, though there was a drop of about 16% in the mean locking operations done which was a tradeoff of having better fairness.
Making the waiter set the handoff bit right after the first wakeup can impact performance especially with a mixed reader/writer workload. With the same microbenchmark with short critical section and equal number of reader and writer threads (40/40), the reader/writer locking operation counts with the current patch were:
40 readers, Iterations Min/Mean/Max = 1,793/1,794/1,796 40 writers, Iterations Min/Mean/Max = 1,793/34,956/86,081
By making waiter set handoff bit immediately after wakeup:
40 readers, Iterations Min/Mean/Max = 43/44/46 40 writers, Iterations Min/Mean/Max = 43/1,263/3,191
--- kernel/locking/lock_events_list.h | 2 + kernel/locking/rwsem.c | 221 ++++++++++++++++++++++-------- 2 files changed, 169 insertions(+), 54 deletions(-)
kernel/locking/lock_events_list.h +2 -0
@@ -61,5 +61,7 @@ LOCK_EVENT(rwsem_opt_fail) /* # of failed opt-spinnings */ LOCK_EVENT(rwsem_rlock) /* # of read locks acquired */ LOCK_EVENT(rwsem_rlock_fast) /* # of fast read locks acquired */ LOCK_EVENT(rwsem_rlock_fail) /* # of failed read lock acquisitions */ +LOCK_EVENT(rwsem_rlock_handoff) /* # of read lock handoffs */ LOCK_EVENT(rwsem_wlock) /* # of write locks acquired */ LOCK_EVENT(rwsem_wlock_fail) /* # of failed write lock acquisitions */ +LOCK_EVENT(rwsem_wlock_handoff) /* # of write lock handoffs */
kernel/locking/rwsem.c +167 -54
394 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 8/18 locking/rwsem: Always release wait_lock before waking up tasks
In reply to Waiman LongWith the use of wake_q, we can do task wakeups without holding the wait_lock. There is one exception in the rwsem code, though. It is when the writer in the slowpath detects that there are waiters ahead but the rwsem is not held by a writer. This can lead to a long wait_lock hold time especially when a large number of readers are to be woken up.
Remediate this situation by releasing the wait_lock before waking up tasks and re-acquiring it afterward.
--- include/linux/sched/wake_q.h | 5 +++++ kernel/locking/rwsem.c | 27 ++++++++++++++++----------- 2 files changed, 21 insertions(+), 11 deletions(-)
include/linux/sched/wake_q.h +5 -0
@@ -51,6 +51,11 @@ static inline void wake_q_init(struct wake_q_head *head) head->lastp = &head->first; } +static inline bool wake_q_empty (struct wake_q_head *head) +{ +return head->first ==WAKE_Q_TAIL ; +} +extern void wake_q_add (struct wake_q_head *head,struct task_struct *task);extern void wake_q_add_safe (struct wake_q_head *head,struct task_struct *task);extern void wake_up_q (struct wake_q_head *head);
kernel/locking/rwsem.c +16 -11
@@ -731,17 +731,22 @@ rwsem_down_write_slowpath(struct rw_semaphore *sem, int state) ? RWSEM_WAKE_READERS : RWSEM_WAKE_ANY, &wake_q); -/* -* The wakeup is normally called _after_ the wait_lock -* is released, but given that we are proactively waking -* readers we can deal with the wake_q overhead as it is -* similar to releasing and taking the wait_lock again -* for attempting rwsem_try_write_lock(). -*/ -wake_up_q (&wake_q); - -/* We need wake_q again below, reinitialize */ -wake_q_init (&wake_q); +if (!wake_q_empty (&wake_q)) { +/* +* We want to minimize wait_lock hold time especially +* when a large number of readers are to be woken up. +*/ +raw_spin_unlock_irq (&sem->wait_lock); +wake_up_q (&wake_q); +wake_q_init (&wake_q);/* Used again, reinit */ +raw_spin_lock_irq (&sem->wait_lock); +/* +* This waiter may have become first in the wait +* list after re-acquring the wait_lock. The +* rwsem_first_waiter() test in the main while +* loop below will correctly detect that. +*/ + } }else { count =atomic_long_add_return (RWSEM_FLAG_WAITERS , &sem->count); }
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 9/18 locking/rwsem: More optimal RT task handling of null owner
In reply to Waiman LongAn RT task can do optimistic spinning only if the lock holder is actually running. If the state of the lock holder isn't known, there is a possibility that high priority of the RT task may block forward progress of the lock holder if it happens to reside on the same CPU. This will lead to deadlock. So we have to make sure that an RT task will not spin on a reader-owned rwsem.
When the owner is temporarily set to NULL, there are two cases where we may want to continue spinning:
1) The lock owner is in the process of releasing the lock, sem->owner is cleared but the lock has not been released yet.
2) The lock was free and owner cleared, but another task just comes in and acquire the lock before we try to get it. The new owner may be a spinnable writer.
So an RT task is now made to retry one more time to see if it can acquire the lock or continue spinning on the new owning writer.
When testing on a 8-socket IvyBridge-EX system, the one additional retry seems to improve locking performance of RT write locking threads under heavy contentions. The table below shows the locking rates (in kops/s) with various write locking threads before and after the patch.
Locking threads Pre-patch Post-patch
--------------- --------- -----------
4 2,753 2,608
8 2,529 2,520
16 1,727 1,918
32 1,263 1,956
64 889 1,343--- kernel/locking/rwsem.c | 51 ++++++++++++++++++++++++++++++++++++------ 1 file changed, 44 insertions(+), 7 deletions(-)
kernel/locking/rwsem.c +44 -7
@@ -545,6 +545,7 @@ static noinline enum owner_state rwsem_spin_on_owner(struct rw_semaphore *sem)static bool rwsem_optimistic_spin (struct rw_semaphore *sem) {bool taken = false; +int prev_owner_state =OWNER_NULL ;preempt_disable ();
@@ -562,7 +563,12 @@ static bool rwsem_optimistic_spin(struct rw_semaphore *sem)* 2) readers own the lock as we can't determine if they are * actively running or not. */ -while (rwsem_spin_on_owner (sem) &OWNER_SPINNABLE ) { +for (;;) { +enum owner_state owner_state =rwsem_spin_on_owner (sem); + +if (!(owner_state &OWNER_SPINNABLE )) +break ; +/* * Try to acquire the lock */
@@ -572,13 +578,44 @@ static bool rwsem_optimistic_spin(struct rw_semaphore *sem) }/* -* When there's no owner, we might have preempted between the -* owner acquiring the lock and setting the owner field. If -* we're an RT task that will live-lock because we won't let -* the owner complete. +* An RT task cannot do optimistic spinning if it cannot +* be sure the lock holder is running or live-lock may +* happen if the current task and the lock holder happen +* to run in the same CPU. However, aborting optimistic +* spinning while a NULL owner is detected may miss some +* opportunity where spinning can continue without causing +* problem. +* +* There are 2 possible cases where an RT task may be able +* to continue spinning. +* +* 1) The lock owner is in the process of releasing the +* lock, sem->owner is cleared but the lock has not +* been released yet. +* 2) The lock was free and owner cleared, but another +* task just comes in and acquire the lock before +* we try to get it. The new owner may be a spinnable +* writer. +* +* To take advantage of two scenarios listed agove, the RT +* task is made to retry one more time to see if it can +* acquire the lock or continue spinning on the new owning +* writer. Of course, if the time lag is long enough or the +* new owner is not a writer or spinnable, the RT task will +* quit spinning. +* +* If the owner is a writer, the need_resched() check is +* done inside rwsem_spin_on_owner(). If the owner is not +* a writer, need_resched() check needs to be done here. */ -if (!sem->owner && (need_resched () ||rt_task (current))) -break ; +if (owner_state !=OWNER_WRITER ) { +if (need_resched ()) +break ; +if (rt_task (current) && + (prev_owner_state !=OWNER_WRITER )) +break ; + } + prev_owner_state = owner_state;/* * The cpu_relax() call is a compiler barrier which forces
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 10/18 locking/rwsem: Wake up almost all readers in wait queue
In reply to Waiman LongWhen the front of the wait queue is a reader, other readers immediately following the first reader will also be woken up at the same time. However, if there is a writer in between. Those readers behind the writer will not be woken up.
Because of optimistic spinning, the lock acquisition order is not FIFO anyway. The lock handoff mechanism will ensure that lock starvation will not happen.
Assuming that the lock hold times of the other readers still in the queue will be about the same as the readers that are being woken up, there is really not much additional cost other than the additional latency due to the wakeup of additional tasks by the waker. Therefore all the readers up to a maximum of 256 in the queue are woken up when the first waiter is a reader to improve reader throughput. This is somewhat similar in concept to a phase-fair R/W lock.
With a locking microbenchmark running on 5.1 based kernel, the total locking rates (in kops/s) on a 8-socket IvyBridge-EX system with equal numbers of readers and writers before and after this patch were as follows:
# of Threads Pre-Patch Post-patch
------------ --------- ----------
4 1,641 1,674
8 731 1,062
16 564 924
32 78 300
64 38 195
240 50 149There is no performance gain at low contention level. At high contention level, however, this patch gives a pretty decent performance boost.
--- kernel/locking/rwsem.c | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-)
kernel/locking/rwsem.c +23 -3
@@ -254,6 +254,14 @@ enum writer_wait_state {*/ #define RWSEM_WAIT_TIMEOUT DIV_ROUND_UP(HZ, 250) +/* +* Magic number to batch-wakeup waiting readers, even when writers are +* also present in the queue. This both limits the amount of work the +* waking thread must do and also prevents any potential counter overflow, +* however unlikely. +*/ +#define MAX_READERS_WAKEUP 0x100 +/* * handle the lock release when processes blocked on it that can now run * - if we come here from up_xxxx(), then the RWSEM_FLAG_WAITERS bit must
@@ -328,16 +336,22 @@ static void __rwsem_mark_wake(struct rw_semaphore *sem, }/* -* Grant an infinite number of read locks to the readers at the front -* of the queue. We know that woken will be at least 1 as we accounted +* Grant up to MAX_READERS_WAKEUP read locks to all the readers in the +* queue. We know that the woken will be at least 1 as we accounted * for above. Note we increment the 'active part' of the count by the * number of readers before waking any processes up. +* +* This is an adaptation of the phase-fair R/W locks where at the +* reader phase (first waiter is a reader), all readers are eligible +* to acquire the lock at the same time irrespective of their order +* in the queue. The writers acquire the lock according to their +* order in the queue. */ list_for_each_entry_safe (waiter, tmp, &sem->wait_list, list) {struct task_struct *tsk;if (waiter->type ==RWSEM_WAITING_FOR_WRITE ) -break ; +continue ; woken++; tsk = waiter->task;
@@ -356,6 +370,12 @@ static void __rwsem_mark_wake(struct rw_semaphore *sem,* after setting the reader waiter to nil. */ wake_q_add_safe (wake_q, tsk); + +/* +* Limit # of readers that can be woken up per wakeup call. +*/ +if (woken >=MAX_READERS_WAKEUP ) +break ; } adjustment = woken *RWSEM_READER_BIAS - adjustment;
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 11/18 locking/rwsem: Clarify usage of owner's nonspinaable bit
In reply to Waiman LongBit 1 of sem->owner (RWSEM_ANONYMOUSLY_OWNED) is used to designate an anonymous owner - readers or an anonymous writer. The setting of this anonymous bit is used as an indicator that optimistic spinning cannot be done on this rwsem.
With the upcoming reader optimistic spinning patches, a reader-owned rwsem can be spinned on for a limit period of time. We still need this bit to indicate a rwsem is nonspinnable, but not setting this bit loses its meaning that the owner is known. So rename the bit to RWSEM_NONSPINNABLE to clarify its meaning.
This patch also fixes a DEBUG_RWSEMS_WARN_ON() bug in __up_write().
--- include/linux/rwsem.h | 2 +- kernel/locking/rwsem.c | 43 +++++++++++++++++++++--------------------- 2 files changed, 22 insertions(+), 23 deletions(-)
include/linux/rwsem.h +1 -1
@@ -50,7 +50,7 @@ struct rw_semaphore { };/* -* Setting bit 1 of the owner field but not bit 0 will indicate +* Setting all bits of the owner field except bit 0 will indicate * that the rwsem is writer-owned with an unknown owner. */ #define RWSEM_OWNER_UNKNOWN ((struct task_struct *)-2L)
kernel/locking/rwsem.c +21 -22
103 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 12/18 locking/rwsem: Enable readers spinning on writer
In reply to Waiman LongThis patch enables readers to optimistically spin on a
rwsem when it is owned by a writer instead of going to sleep directly. The rwsem_can_spin_on_owner() function is extracted out of rwsem_optimistic_spin() and is called directly by __rwsem_down_read_failed_common() and __rwsem_down_write_failed_common().
With a locking microbenchmark running on 5.1 based kernel, the total locking rates (in kops/s) on a 8-socket IvyBrige-EX system with equal numbers of readers and writers before and after the patch were as follows:
# of Threads Pre-patch Post-patch
------------ --------- ----------
4 1,674 1,684
8 1,062 1,074
16 924 900
32 300 458
64 195 208
128 164 168
240 149 143The performance change wasn't significant in this case, but this change is required by a follow-on patch.
--- kernel/locking/lock_events_list.h | 1 + kernel/locking/rwsem.c | 86 ++++++++++++++++++++++++++----- 2 files changed, 75 insertions(+), 12 deletions(-)
kernel/locking/lock_events_list.h +1 -0
@@ -56,6 +56,7 @@ LOCK_EVENT(rwsem_sleep_reader) /* # of reader sleeps */ LOCK_EVENT(rwsem_sleep_writer) /* # of writer sleeps */ LOCK_EVENT(rwsem_wake_reader) /* # of reader wakeups */ LOCK_EVENT(rwsem_wake_writer) /* # of writer wakeups */ +LOCK_EVENT(rwsem_opt_rlock) /* # of read locks opt-spin acquired */ LOCK_EVENT(rwsem_opt_wlock) /* # of write locks opt-spin acquired */ LOCK_EVENT(rwsem_opt_fail) /* # of failed opt-spinnings */ LOCK_EVENT(rwsem_rlock) /* # of read locks acquired */
kernel/locking/rwsem.c +74 -12
155 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 13/18 locking/rwsem: Enable time-based spinning on reader-owned rwsem
In reply to Waiman LongWhen the rwsem is owned by reader, writers stop optimistic spinning simply because there is no easy way to figure out if all the readers are actively running or not. However, there are scenarios where the readers are unlikely to sleep and optimistic spinning can help performance.
This patch provides a simple mechanism for spinning on a reader-owned rwsem by a writer. It is a time threshold based spinning where the allowable spinning time can vary from 10us to 25us depending on the condition of the rwsem.
When the time threshold is exceeded, the nonspinnable bits will be set in the owner field to indicate that no more optimistic spinning will be allowed on this rwsem until it becomes writer owned again. Not even readers is allowed to acquire the reader-locked rwsem by optimistic spinning for fairness.
We also want a writer to acquire the lock after the readers hold the lock for a relatively long time. In order to give preference to writers under such a circumstance, the single RWSEM_NONSPINNABLE bit is now split into two - one for reader and one for writer. When optimistic spinning is disabled, both bits will be set. When the reader count drop down to 0, the writer nonspinnable bit will be cleared to allow writers to spin on the lock, but not the readers. When a writer acquires the lock, it will write its own task structure pointer into sem->owner and clear the reader nonspinnable bit in the process.
The time taken for each iteration of the reader-owned rwsem spinning loop varies. Below are sample minimum elapsed times for 16 iterations of the loop.
System Time for 16 Iterations
------ ----------------------
1-socket Skylake ~800ns 4-socket Broadwell ~300ns 2-socket ThunderX2 (arm64) ~250ns
When the lock cacheline is contended, we can see up to almost 10X increase in elapsed time. So 25us will be at most 500, 1300 and 1600 iterations for each of the above systems.
With a locking microbenchmark running on 5.1 based kernel, the total locking rates (in kops/s) on a 8-socket IvyBridge-EX system with equal numbers of readers and writers before and after this patch were as follows:
# of Threads Pre-patch Post-patch
------------ --------- ----------
2 1,759 6,684
4 1,684 6,738
8 1,074 7,222
16 900 7,163
32 458 7,316
64 208 520
128 168 425
240 143 474This patch gives a big boost in performance for mixed reader/writer workloads.
With 32 locking threads, the rwsem lock event data were:
rwsem_opt_fail=79850
rwsem_opt_nospin=5069
rwsem_opt_rlock=597484
rwsem_opt_wlock=957339
rwsem_sleep_reader=57782
rwsem_sleep_writer=55663
With 64 locking threads, the data looked like:
rwsem_opt_fail=346723
rwsem_opt_nospin=6293
rwsem_opt_rlock=1127119
rwsem_opt_wlock=1400628
rwsem_sleep_reader=308201
rwsem_sleep_writer=72281
So a lot more threads acquired the lock in the slowpath and more threads went to sleep.
--- kernel/locking/lock_events_list.h | 1 + kernel/locking/rwsem.c | 218 ++++++++++++++++++++++++------ 2 files changed, 180 insertions(+), 39 deletions(-)
kernel/locking/lock_events_list.h +1 -0
@@ -59,6 +59,7 @@ LOCK_EVENT(rwsem_wake_writer) /* # of writer wakeups */ LOCK_EVENT(rwsem_opt_rlock) /* # of read locks opt-spin acquired */ LOCK_EVENT(rwsem_opt_wlock) /* # of write locks opt-spin acquired */ LOCK_EVENT(rwsem_opt_fail) /* # of failed opt-spinnings */ +LOCK_EVENT(rwsem_opt_nospin) /* # of disabled reader opt-spinnings */ LOCK_EVENT(rwsem_rlock) /* # of read locks acquired */ LOCK_EVENT(rwsem_rlock_fast) /* # of fast read locks acquired */ LOCK_EVENT(rwsem_rlock_fail) /* # of failed read lock acquisitions */
kernel/locking/rwsem.c +179 -39
381 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 14/18 locking/rwsem: Adaptive disabling of reader optimistic spinning
In reply to Waiman LongReader optimistic spinning is helpful when the reader critical section is short and there aren't that many readers around. It makes readers relatively more preferred than writers. When a writer times out spinning on a reader-owned lock and set the nospinnable bits, there are two main reasons for that.
1) The reader critical section is long, perhaps the task sleeps after acquiring the read lock.
2) There are just too many readers contending the lock causing it to take a while to service all of them.
In the former case, long reader critical section will impede the progress of writers which is usually more important for system performance. In the later case, reader optimistic spinning tends to make the reader groups that contain readers that acquire the lock together smaller leading to more of them. That may hurt performance in some cases. In other words, the setting of nonspinnable bits indicates that reader optimistic spinning may not be helpful for those workloads that cause it.
Therefore, any writers that had observed the setting of the writer nonspinnable bit for a given rwsem after they fail to acquire the lock via optimistic spinning will set the reader nonspinnable bit once they acquire the write lock. This is to discourage reader optmistic spinning on that particular rwsem and make writers more preferred. This adaptive disabling of reader optimistic spinning will alleviate some of the negative side effect of this feature.
On a 2-socket 40-core 80-thread Skylake system, the page_fault1 test of the will-it-scale benchmark was run with various number of threads. The number of operations done before and after the patch were:
Threads Before patch After patch % change
------- ------------ ----------- --------
20 5409075 5436456 +0.5%
40 7174080 7903845 +10.2%
60 6749707 7009784 +3.9%
80 7071334 7353806 +4.0%This doesn't recover all the lost performance, but is close to half. Given the fact that reader optimistic spinning does benefit some workloads, this is a good compromise.
Using the rwsem locking microbenchmark with very short critical section, this patch also helps performance at high contention level as shown by the locking rates (kops/s) below with equal numbers of readers and writers before and after this patch:
# of Threads Pre-patch Post-patch
------------ --------- ----------
2 4,472 4,839
4 4,623 4,143
8 4,764 4,126
16 4,678 3,873
32 2,847 3,263
64 2,478 3,121
80 2,222 3,104--- kernel/locking/lock_events_list.h | 9 +++--- kernel/locking/rwsem.c | 52 +++++++++++++++++++++++++++++-- 2 files changed, 55 insertions(+), 6 deletions(-)
kernel/locking/lock_events_list.h +5 -4
@@ -56,10 +56,11 @@ LOCK_EVENT(rwsem_sleep_reader) /* # of reader sleeps */ LOCK_EVENT(rwsem_sleep_writer) /* # of writer sleeps */ LOCK_EVENT(rwsem_wake_reader) /* # of reader wakeups */ LOCK_EVENT(rwsem_wake_writer) /* # of writer wakeups */ -LOCK_EVENT(rwsem_opt_rlock) /* # of read locks opt-spin acquired */ -LOCK_EVENT(rwsem_opt_wlock) /* # of write locks opt-spin acquired */ -LOCK_EVENT(rwsem_opt_fail) /* # of failed opt-spinnings */ -LOCK_EVENT(rwsem_opt_nospin) /* # of disabled reader opt-spinnings */ +LOCK_EVENT(rwsem_opt_rlock) /* # of opt-acquired read locks */ +LOCK_EVENT(rwsem_opt_wlock) /* # of opt-acquired write locks */ +LOCK_EVENT(rwsem_opt_fail) /* # of failed optspins */ +LOCK_EVENT(rwsem_opt_nospin) /* # of disabled optspins */ +LOCK_EVENT(rwsem_opt_norspin) /* # of disabled reader-only optspins */ LOCK_EVENT(rwsem_rlock) /* # of read locks acquired */ LOCK_EVENT(rwsem_rlock_fast) /* # of fast read locks acquired */ LOCK_EVENT(rwsem_rlock_fail) /* # of failed read lock acquisitions */
kernel/locking/rwsem.c +50 -2
95 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 15/18 locking/rwsem: Add more rwsem owner access helpers
In reply to Waiman LongBefore combining owner and count, we are adding two new helpers for accessing the owner value in the rwsem.
1) struct task_struct *rwsem_get_owner(struct rw_semaphore *sem)
2) bool is_rwsem_reader_owned(struct rw_semaphore *sem)
--- kernel/locking/rwsem.c | 41 ++++++++++++++++++++++++++++++----------- 1 file changed, 30 insertions(+), 11 deletions(-)
kernel/locking/rwsem.c +30 -11
@@ -157,6 +157,11 @@ static inline void rwsem_clear_owner(struct rw_semaphore *sem)WRITE_ONCE (sem->owner,NULL ); } +static inline struct task_struct *rwsem_get_owner (struct rw_semaphore *sem) +{ +return READ_ONCE (sem->owner); +} +/* * The task_struct pointer of the last owning reader will be left in * the owner field.
@@ -198,6 +203,23 @@ static inline bool is_rwsem_spinnable(struct rw_semaphore *sem, bool wr)return is_rwsem_owner_spinnable (READ_ONCE (sem->owner), wr); } +/* +* Return true if the rwsem is owned by a reader. +*/ +static inline bool is_rwsem_reader_owned (struct rw_semaphore *sem) +{ +#ifdef CONFIG_DEBUG_RWSEMS +/* +* Check the count to see if it is write-locked. +*/ +long count =atomic_long_read (&sem->count); + +if (count &RWSEM_WRITER_MASK ) +return false; +#endif +return (unsigned long )sem->owner &RWSEM_READER_OWNED ; +} +#ifdef CONFIG_DEBUG_RWSEMS /* * With CONFIG_DEBUG_RWSEMS configured, it will make sure that if there
@@ -210,7 +232,7 @@ static inline void rwsem_clear_reader_owned(struct rw_semaphore *sem)unsigned long owner = (unsigned long )READ_ONCE (sem->owner);if ((owner & ~RWSEM_OWNER_FLAGS_MASK ) == (unsigned long )current) -cmpxchg_relaxed ((unsigned long *)&sem->owner, val, +cmpxchg_relaxed ((unsigned long *)&sem->owner, owner, owner & RWSEM_OWNER_FLAGS_MASK); }#else
@@ -565,7 +587,7 @@ static inline bool rwsem_can_spin_on_owner(struct rw_semaphore *sem, bool wr)preempt_disable ();rcu_read_lock (); - owner =READ_ONCE (sem->owner); + owner =rwsem_get_owner (sem);if (owner) { ret = is_rwsem_owner_spinnable(owner, wr) && (((unsigned long)owner & RWSEM_READER_OWNED) ||
@@ -614,7 +636,7 @@ static inline enum owner_state rwsem_owner_state(unsigned long owner, bool wr) static noinline enum owner_staterwsem_spin_on_owner (struct rw_semaphore *sem,bool wr) { -struct task_struct *tmp, *owner =READ_ONCE (sem->owner); +struct task_struct *tmp, *owner =rwsem_get_owner (sem);enum owner_state state =rwsem_owner_state ((unsigned long )owner, wr);if (state !=OWNER_WRITER )
@@ -627,7 +649,7 @@ rwsem_spin_on_owner(struct rw_semaphore *sem, bool wr)break ; } - tmp =READ_ONCE (sem->owner); + tmp =rwsem_get_owner (sem);if (tmp != owner) { state =rwsem_owner_state ((unsigned long )tmp, wr);break ;
@@ -1170,8 +1192,7 @@ inline void __down_read(struct rw_semaphore *sem)if (unlikely (atomic_long_fetch_add_acquire (RWSEM_READER_BIAS , &sem->count) &RWSEM_READ_FAILED_MASK )) {rwsem_down_read_slowpath (sem,TASK_UNINTERRUPTIBLE ); -DEBUG_RWSEMS_WARN_ON (!((unsigned long )sem->owner & -RWSEM_READER_OWNED ), sem); +DEBUG_RWSEMS_WARN_ON (!is_rwsem_reader_owned (sem), sem); }else {rwsem_set_reader_owned (sem); }
@@ -1183,8 +1204,7 @@ static inline int __down_read_killable(struct rw_semaphore *sem) &sem->count) & RWSEM_READ_FAILED_MASK)) { if (IS_ERR(rwsem_down_read_slowpath(sem, TASK_KILLABLE))) return -EINTR; - DEBUG_RWSEMS_WARN_ON(!((unsigned long)sem->owner & - RWSEM_READER_OWNED), sem); + DEBUG_RWSEMS_WARN_ON(!is_rwsem_reader_owned(sem), sem); } else {rwsem_set_reader_owned (sem); }
@@ -1255,7 +1275,7 @@ inline void __up_read(struct rw_semaphore *sem) {long tmp; -DEBUG_RWSEMS_WARN_ON (!((unsigned long )sem->owner &RWSEM_READER_OWNED ), sem); +DEBUG_RWSEMS_WARN_ON (!is_rwsem_reader_owned (sem), sem);rwsem_clear_reader_owned (sem); tmp =atomic_long_add_return_release (-RWSEM_READER_BIAS , &sem->count); if (unlikely((tmp & (RWSEM_LOCK_MASK|RWSEM_FLAG_WAITERS)) ==
@@ -1469,8 +1489,7 @@ EXPORT_SYMBOL(down_write_killable_nested);void up_read_non_owner (struct rw_semaphore *sem) { -DEBUG_RWSEMS_WARN_ON (!((unsigned long )sem->owner &RWSEM_READER_OWNED ), - sem); +DEBUG_RWSEMS_WARN_ON (!is_rwsem_reader_owned (sem), sem);__up_read (sem); }EXPORT_SYMBOL (up_read_non_owner);
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 16/18 locking/rwsem: Guard against making count negative
In reply to Waiman LongThe upper bits of the count field is used as reader count. When sufficient number of active readers are present, the most significant bit will be set and the count becomes negative. If the number of active readers keep on piling up, we may eventually overflow the reader counts. This is not likely to happen unless the number of bits reserved for reader count is reduced because those bits are need for other purpose.
To prevent this count overflow from happening, the most significant bit is now treated as a guard bit (RWSEM_FLAG_READFAIL). Read-lock attempts will now fail for both the fast and optimistic spinning paths whenever this bit is set. So all those extra readers will be put to sleep in the wait queue. Wakeup will not happen until the reader count reaches 0.
--- kernel/locking/rwsem.c | 73 +++++++++++++++++++++++++++++++++--------- 1 file changed, 58 insertions(+), 15 deletions(-)
kernel/locking/rwsem.c +58 -15
@@ -108,13 +108,28 @@#endif /* -* The definition of the atomic counter in the semaphore: +* On 64-bit architectures, the bit definitions of the count are: * -* Bit 0 - writer locked bit -* Bit 1 - waiters present bit -* Bit 2 - lock handoff bit -* Bits 3-7 - reserved -* Bits 8-X - 24-bit (32-bit) or 56-bit reader count +* Bit 0 - writer locked bit +* Bit 1 - waiters present bit +* Bit 2 - lock handoff bit +* Bits 3-7 - reserved +* Bits 8-62 - 55-bit reader count +* Bit 63 - read fail bit +* +* On 32-bit architectures, the bit definitions of the count are: +* +* Bit 0 - writer locked bit +* Bit 1 - waiters present bit +* Bit 2 - lock handoff bit +* Bits 3-7 - reserved +* Bits 8-30 - 23-bit reader count +* Bit 31 - read fail bit +* +* It is not likely that the most significant bit (read fail bit) will ever +* be set. This guard bit is still checked anyway in the down_read() fastpath +* just in case we need to use up more of the reader bits for other purpose +* in the future. * * atomic_long_fetch_add() is used to obtain reader lock, whereas * atomic_long_cmpxchg() will be used to obtain writer lock.
@@ -131,6 +146,7 @@#define RWSEM_WRITER_LOCKED (1UL << 0)#define RWSEM_FLAG_WAITERS (1UL << 1)#define RWSEM_FLAG_HANDOFF (1UL << 2) +#define RWSEM_FLAG_READFAIL (1UL << (BITS_PER_LONG - 1))#define RWSEM_READER_SHIFT 8#define RWSEM_READER_BIAS (1UL << RWSEM_READER_SHIFT)
@@ -138,7 +154,7 @@#define RWSEM_WRITER_MASK RWSEM_WRITER_LOCKED#define RWSEM_LOCK_MASK (RWSEM_WRITER_MASK|RWSEM_READER_MASK)#define RWSEM_READ_FAILED_MASK (RWSEM_WRITER_MASK|RWSEM_FLAG_WAITERS|\ - RWSEM_FLAG_HANDOFF) + RWSEM_FLAG_HANDOFF|RWSEM_FLAG_READFAIL)/* * All writes to owner are protected by WRITE_ONCE() to make sure that
@@ -872,13 +888,36 @@ static inline void clear_wr_nonspinnable(struct rw_semaphore *sem) { }* Wait for the read lock to be granted */ static struct rw_semaphore __sched * -rwsem_down_read_slowpath (struct rw_semaphore *sem,int state) +rwsem_down_read_slowpath (struct rw_semaphore *sem,int state,long count) { -long count, adjustment = -RWSEM_READER_BIAS ; +long adjustment = -RWSEM_READER_BIAS ;bool wake = false;struct rwsem_waiter waiter;DEFINE_WAKE_Q (wake_q); +if (unlikely (count <0 )) { +/* +* The sign bit has been set meaning that too many active +* readers are present. We need to decrement reader count & +* enter wait queue immediately to avoid overflowing the +* reader count. +* +* As preemption is not disabled, there is a remote +* possibility that preemption can happen in the narrow +* timing window between incrementing and decrementing +* the reader count and the task is put to sleep for a +* considerable amount of time. If sufficient number +* of such unfortunate sequence of events happen, we +* may still overflow the reader count. It is extremely +* unlikey, though. If this is a concern, we should consider +* disable preemption during this timing window to make +* sure that such unfortunate event will not happen. +*/ +atomic_long_add (-RWSEM_READER_BIAS , &sem->count); + adjustment =0 ; + goto queue; + } +if (!rwsem_can_spin_on_owner (sem, false)) goto queue;
@@ -1189,9 +1228,11 @@ static struct rw_semaphore *rwsem_downgrade_wake(struct rw_semaphore *sem)*/ inline void __down_read (struct rw_semaphore *sem) { -if (unlikely (atomic_long_fetch_add_acquire (RWSEM_READER_BIAS , - &sem->count) &RWSEM_READ_FAILED_MASK )) { -rwsem_down_read_slowpath (sem,TASK_UNINTERRUPTIBLE ); +long tmp =atomic_long_fetch_add_acquire (RWSEM_READER_BIAS , + &sem->count); + +if (unlikely (tmp &RWSEM_READ_FAILED_MASK )) { +rwsem_down_read_slowpath (sem,TASK_UNINTERRUPTIBLE , tmp);DEBUG_RWSEMS_WARN_ON (!is_rwsem_reader_owned (sem), sem); }else {rwsem_set_reader_owned (sem);
@@ -1200,9 +1241,11 @@ inline void __down_read(struct rw_semaphore *sem)static inline int __down_read_killable (struct rw_semaphore *sem) { -if (unlikely (atomic_long_fetch_add_acquire (RWSEM_READER_BIAS , - &sem->count) &RWSEM_READ_FAILED_MASK )) { -if (IS_ERR (rwsem_down_read_slowpath (sem,TASK_KILLABLE ))) +long tmp =atomic_long_fetch_add_acquire (RWSEM_READER_BIAS , + &sem->count); + +if (unlikely (tmp &RWSEM_READ_FAILED_MASK )) { +if (IS_ERR (rwsem_down_read_slowpath (sem,TASK_KILLABLE , tmp)))return -EINTR ;DEBUG_RWSEMS_WARN_ON (!is_rwsem_reader_owned (sem), sem); }else {
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 17/18 locking/rwsem: Merge owner into count on x86-64
In reply to Waiman LongWith separate count and owner, there are timing windows where the two values are inconsistent. That can cause problem when trying to figure out the exact state of the rwsem. For instance, a RT task will stop optimistic spinning if the lock is acquired by a writer but the owner field isn't set yet. That can be solved by combining the count and owner together in a single atomic value.
On 32-bit architectures, there aren't enough bits to hold both. 64-bit architectures, however, can have enough bits to do that. For x86-64, the physical address can use up to 52 bits. That is 4PB of memory. That leaves 12 bits available for other use. The task structure pointer is aligned to the L1 cache size. That means another 6 bits (64 bytes cacheline) will be available. Reserving 2 bits for status flags, we will have 16 bits for the reader count and the read fail bit. That can supports up to (32k-1) readers. Without 5-level page table, we can supports up to (2M-1) readers.
The owner value will still be duplicated in the owner field as that will ease debugging when looking at core dump.
This change is currently enabled for x86-64 only. Other 64-bit architectures may be enabled in the future if the need arises.
With a locking microbenchmark running on 5.1 based kernel, the total locking rates (in kops/s) on a 8-socket IvyBridge-EX system with writer-only locking threads and then equal numbers of readers and writers (mixed) before patch and after this and subsequent related patches were as follows:
Before Patch After Patch
# of Threads wlock mixed wlock mixed
------------ ----- ----- ----- -----
1 30,422 31,034 30,323 30,379
2 6,427 6,684 7,804 9,436
4 6,742 6,738 7,568 8,268
8 7,092 7,222 5,679 7,041
16 6,882 7,163 6,848 7,652
32 7,458 7,316 7,975 2,189
64 7,906 520 8,269 534
128 1,680 425 8,047 448In the single thread case, the complex write-locking operation does introduce a little bit of overhead (about 0.3%). For the contended cases, except for some anomalies in the data, there is no evidence that this change will adversely impact performance.
When running the same microbenchmark with RT locking threads instead, we got the following results:
Before Patch After Patch
# of Threads wlock mixed wlock mixed
------------ ----- ----- ----- -----
2 4,065 3,642 4,756 5,062
4 2,254 1,907 3,460 2,496
8 2,386 964 3,012 1,964
16 2,095 1,596 3,083 1,862
32 2,388 530 3,717 359
64 1,424 322 4,060 401
128 1,642 510 4,488 628It is obvious that RT tasks can benefit pretty significantly with this set of patches.
--- arch/x86/Kconfig | 6 +++ kernel/Kconfig.locks | 12 +++++ kernel/locking/rwsem.c | 102 +++++++++++++++++++++++++++++++++++++---- 3 files changed, 111 insertions(+), 9 deletions(-)
arch/x86/Kconfig +6 -0
@@ -80,6 +80,7 @@ config X86 select ARCH_USE_BUILTIN_BSWAP select ARCH_USE_QUEUED_RWLOCKS select ARCH_USE_QUEUED_SPINLOCKS + select ARCH_USE_RWSEM_OWNER_COUNT if X86_64 select ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH select ARCH_WANTS_DYNAMIC_TASK_STRUCT select ARCH_WANTS_THP_SWAP if X86_64
@@ -350,6 +351,11 @@ config PGTABLE_LEVELS default 3 if X86_PAE default 2 +config RWSEM_OWNER_COUNT_PA_BITS + int + default 52 if X86_5LEVEL + default 46 if X86_64 + config CC_HAS_SANE_STACKPROTECTOR bool default $(success,$(srctree)/scripts/gcc-x86_64-has-stack-protector.sh $(CC)) if 64BIT
kernel/Kconfig.locks +12 -0
@@ -251,3 +251,15 @@ config ARCH_USE_QUEUED_RWLOCKS config QUEUED_RWLOCKS def_bool y if ARCH_USE_QUEUED_RWLOCKS depends on SMP + +# +# An architecture that want to merge rwsem write-owner into count should +# select ARCH_USE_RWSEM_OWNER_COUNT and define RWSEM_OWNER_COUNT_PA_BITS +# as the correct number of physical address bits. +# +config ARCH_USE_RWSEM_OWNER_COUNT + bool + +config RWSEM_OWNER_COUNT + def_bool y if ARCH_USE_RWSEM_OWNER_COUNT + depends on SMP && 64BIT
kernel/locking/rwsem.c +93 -9
166 lines not on this page · raw message
Signature · 1 line
2.18.1
Waiman Long
reviewerPATCH v5 18/18 locking/rwsem: Remove redundant computation of writer lock word
In reply to Waiman LongOn 64-bit architectures, each rwsem writer will have its unique lock word for acquiring the lock. Right now, the writer code recomputes the lock word every time it tries to acquire the lock. This is a waste of time. The lock word is now cached and reused when it is needed.
When CONFIG_RWSEM_OWNER_COUNT isn't defined, the extra constant argument to rwsem_try_write_lock() and rwsem_try_write_lock_unqueued() should be optimized out by the compiler.
--- kernel/locking/rwsem.c | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)
kernel/locking/rwsem.c +12 -9
@@ -578,6 +578,7 @@ static void __rwsem_mark_wake(struct rw_semaphore *sem,* bit is set or the lock is acquired with handoff bit cleared. */ static inline bool rwsem_try_write_lock (long count,struct rw_semaphore *sem, +const long wlock,enum writer_wait_state wstate) {long new;
@@ -594,8 +595,7 @@ static inline bool rwsem_try_write_lock(long count, struct rw_semaphore *sem,return false; new = count |RWSEM_FLAG_HANDOFF ; }else { - new = (count |RWSEM_WRITER_LOCKED ) & - ~RWSEM_FLAG_HANDOFF ; + new = (count | wlock) & ~RWSEM_FLAG_HANDOFF ;if (list_is_singular (&sem->wait_list)) new &= ~RWSEM_FLAG_WAITERS ;
@@ -641,13 +641,14 @@ static inline bool rwsem_try_read_lock_unqueued(struct rw_semaphore *sem)/* * Try to acquire write lock before the writer has been put on wait queue. */ -static inline bool rwsem_try_write_lock_unqueued (struct rw_semaphore *sem) +static inline bool rwsem_try_write_lock_unqueued (struct rw_semaphore *sem, +const long wlock) {long count =atomic_long_read (&sem->count);while (!(count & (RWSEM_LOCK_MASK |RWSEM_FLAG_HANDOFF ))) {if (atomic_long_try_cmpxchg_acquire (&sem->count, &count, - count |RWSEM_WRITER_LOCKED )) { + count | wlock)) {rwsem_set_owner (sem);lockevent_inc (rwsem_opt_wlock);return true;
@@ -813,7 +814,7 @@ static inline u64 rwsem_rspin_threshold(struct rw_semaphore *sem)return sched_clock () + delta; } -static bool rwsem_optimistic_spin (struct rw_semaphore *sem,bool wlock) +static bool rwsem_optimistic_spin (struct rw_semaphore *sem,const long wlock) {bool taken = false;int prev_owner_state =OWNER_NULL ;
@@ -841,7 +842,7 @@ static bool rwsem_optimistic_spin(struct rw_semaphore *sem, bool wlock)/* * Try to acquire the lock */ - taken = wlock ?rwsem_try_write_lock_unqueued (sem) + taken = wlock ?rwsem_try_write_lock_unqueued (sem, wlock) :rwsem_try_read_lock_unqueued (sem);if (taken)
@@ -957,7 +958,8 @@ static inline bool rwsem_can_spin_on_owner(struct rw_semaphore *sem, bool wr)return false; } -static inline bool rwsem_optimistic_spin (struct rw_semaphore *sem,bool wlock) +static inline bool rwsem_optimistic_spin (struct rw_semaphore *sem, +const long wlock) {return false; }
@@ -1122,10 +1124,11 @@ rwsem_down_write_slowpath(struct rw_semaphore *sem, int state)struct rwsem_waiter waiter;struct rw_semaphore *ret = sem;DEFINE_WAKE_Q (wake_q); +const long wlock =RWSEM_WRITER_LOCKED ;/* do optimistic spinning and steal lock if possible */ if (rwsem_can_spin_on_owner (sem, true) && -rwsem_optimistic_spin (sem, true)) +rwsem_optimistic_spin (sem, wlock))return sem;/*
@@ -1193,7 +1196,7 @@ rwsem_down_write_slowpath(struct rw_semaphore *sem, int state)/* wait until we successfully acquire the lock */ set_current_state (state);while (true) { -if (rwsem_try_write_lock (count, sem, wstate)) +if (rwsem_try_write_lock (count, sem, wlock, wstate))break ;raw_spin_unlock_irq (&sem->wait_lock);
Signature · 1 line
2.18.1
Waiman Long
reviewerQuoted 10 lines · Waiman Long
v5:
- Drop v4 patch 1 as it is merged into tip's locking/core branch.
- Integrate the 2 followup patches into the series. The first follow-up patch is broken into 2 pieces. The first piece comes in before the "Enable readers spinning on writer" and the 2nd piece is merged into the "Enable time-based spinning on reader-owned rwsem" patch. The 2nd followup patch is added after that.
- Add a new patch to make allwake_up_q()calls after droppingwait_lockas suggested by PeterZ.
- Incorporate numerouos suggestions by PeterZ and Davidlohr.
This patchset is still being reviewed by Peter . The purpose of this series is mainly to sync up the version that Peter has and the ones that I am working on incorporating his feedback. Further changes may still be needed.
I run an overall performance test on this new patchset and present the data in this cover letter. However, I haven't run performance tests for individual patches. So the performance data listed in some of the patches may be stale.
Cheers,
Longman
Quoted 17 lines · Waiman Long
Quoted 10 lines · Waiman Long
v5:
- Drop v4 patch 1 as it is merged into tip's locking/core branch.
- Integrate the 2 followup patches into the series. The first follow-up patch is broken into 2 pieces. The first piece comes in before the "Enable readers spinning on writer" and the 2nd piece is merged into the "Enable time-based spinning on reader-owned rwsem" patch. The 2nd followup patch is added after that.
- Add a new patch to make allwake_up_q()calls after droppingwait_lockas suggested by PeterZ.
- Incorporate numerouos suggestions by PeterZ and Davidlohr.This patchset is still being reviewed by Peter . The purpose of this series is mainly to sync up the version that Peter has and the ones that I am working on incorporating his feedback. Further changes may still be needed.
Quoted 4 lines
I run an overall performance test on this new patchset and present the data in this cover letter. However, I haven't run performance tests for individual patches. So the performance data listed in some of the patches may be stale.
Just for those who'd like to follow the scope of changes, find below the v4->v5 interdiff. v5 is now included in tip:WIP.locking/core, and also merged into tip:master. (But not propagated towards linux-next yet.)
Thanks,
Ingo
==============>
arch/x86/Kconfig | 6 + include/linux/sched/wake_q.h | 5 + kernel/Kconfig.locks | 12 + kernel/locking/lock_events_list.h | 2 - kernel/locking/rwsem.c | 538 +++++++++++++++++++------------------- 5 files changed, 291 insertions(+), 272 deletions(-)
arch/x86/Kconfig +6 -0
@@ -80,6 +80,7 @@ config X86 select ARCH_USE_BUILTIN_BSWAP select ARCH_USE_QUEUED_RWLOCKS select ARCH_USE_QUEUED_SPINLOCKS + select ARCH_USE_RWSEM_OWNER_COUNT if X86_64 select ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH select ARCH_WANTS_DYNAMIC_TASK_STRUCT select ARCH_WANTS_THP_SWAP if X86_64
@@ -350,6 +351,11 @@ config PGTABLE_LEVELS default 3 if X86_PAE default 2 +config RWSEM_OWNER_COUNT_PA_BITS + int + default 52 if X86_5LEVEL + default 46 if X86_64 + config CC_HAS_SANE_STACKPROTECTOR bool default $(success,$(srctree)/scripts/gcc-x86_64-has-stack-protector.sh $(CC)) if 64BIT
include/linux/sched/wake_q.h +5 -0
@@ -51,6 +51,11 @@ static inline void wake_q_init(struct wake_q_head *head) head->lastp = &head->first; } +static inline bool wake_q_empty (struct wake_q_head *head) +{ +return head->first ==WAKE_Q_TAIL ; +} +extern void wake_q_add (struct wake_q_head *head,struct task_struct *task);extern void wake_q_add_safe (struct wake_q_head *head,struct task_struct *task);extern void wake_up_q (struct wake_q_head *head);
kernel/Kconfig.locks +12 -0
@@ -251,3 +251,15 @@ config ARCH_USE_QUEUED_RWLOCKS config QUEUED_RWLOCKS def_bool y if ARCH_USE_QUEUED_RWLOCKS depends on SMP + +# +# An architecture that want to merge rwsem write-owner into count should +# select ARCH_USE_RWSEM_OWNER_COUNT and define RWSEM_OWNER_COUNT_PA_BITS +# as the correct number of physical address bits. +# +config ARCH_USE_RWSEM_OWNER_COUNT + bool + +config RWSEM_OWNER_COUNT + def_bool y if ARCH_USE_RWSEM_OWNER_COUNT + depends on SMP && 64BIT
kernel/locking/lock_events_list.h +0 -2
@@ -65,8 +65,6 @@ LOCK_EVENT(rwsem_rlock) /* # of read locks acquired */ LOCK_EVENT(rwsem_rlock_fast) /* # of fast read locks acquired */ LOCK_EVENT(rwsem_rlock_fail) /* # of failed read lock acquisitions */ LOCK_EVENT(rwsem_rlock_handoff) /* # of read lock handoffs */ -LOCK_EVENT(rwsem_rtrylock) /* # of read trylock calls */ LOCK_EVENT(rwsem_wlock) /* # of write locks acquired */ LOCK_EVENT(rwsem_wlock_fail) /* # of failed write lock acquisitions */ LOCK_EVENT(rwsem_wlock_handoff) /* # of write lock handoffs */ -LOCK_EVENT(rwsem_wtrylock) /* # of write trylock calls */
kernel/locking/rwsem.c +268 -270
973 lines not on this page · raw message
Quoted 20 lines · Ingo Molnar
Quoted 17 lines · Waiman Long
Quoted 10 lines · Waiman Long
v5:
- Drop v4 patch 1 as it is merged into tip's locking/core branch.
- Integrate the 2 followup patches into the series. The first follow-up patch is broken into 2 pieces. The first piece comes in before the "Enable readers spinning on writer" and the 2nd piece is merged into the "Enable time-based spinning on reader-owned rwsem" patch. The 2nd followup patch is added after that.
- Add a new patch to make allwake_up_q()calls after droppingwait_lockas suggested by PeterZ.
- Incorporate numerouos suggestions by PeterZ and Davidlohr.This patchset is still being reviewed by Peter . The purpose of this series is mainly to sync up the version that Peter has and the ones that I am working on incorporating his feedback. Further changes may still be needed.
Quoted 8 lines
Quoted 4 lines
I run an overall performance test on this new patchset and present the data in this cover letter. However, I haven't run performance tests for individual patches. So the performance data listed in some of the patches may be stale.
Just for those who'd like to follow the scope of changes, find below the
v4->v5interdiff. v5 is now included in tip:WIP.locking/core, and also merged into tip:master. (But not propagated towards linux-next yet.)
Hm, I'm experiencing early boot hangs with v5, on defconfig-ish x86-64 kernels:
[ 0.153940] rcu: Hierarchical RCU implementation. [ 0.154289] rcu: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=17. [ 0.154829] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. [ 0.155390] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=17
I bisected it back to the v5 version of this patch:
2fd5f60fa4c3: locking/rwsem: Merge owner into count on x86-64
I'm moving -tip back to -v4 meanwhile.
Thanks,
Ingo
Waiman Long
reviewerQuoted 38 lines · Ingo Molnar
Quoted 18 lines · Ingo Molnar
Quoted 16 lines · Waiman Long
Quoted 10 lines · Waiman Long
v5:
- Drop v4 patch 1 as it is merged into tip's locking/core branch.
- Integrate the 2 followup patches into the series. The first follow-up patch is broken into 2 pieces. The first piece comes in before the "Enable readers spinning on writer" and the 2nd piece is merged into the "Enable time-based spinning on reader-owned rwsem" patch. The 2nd followup patch is added after that.
- Add a new patch to make allwake_up_q()calls after droppingwait_lockas suggested by PeterZ.
- Incorporate numerouos suggestions by PeterZ and Davidlohr.This patchset is still being reviewed by Peter . The purpose of this series is mainly to sync up the version that Peter has and the ones that I am working on incorporating his feedback. Further changes may still be needed.
Quoted 7 lines
Quoted 4 lines
I run an overall performance test on this new patchset and present the data in this cover letter. However, I haven't run performance tests for individual patches. So the performance data listed in some of the patches may be stale.
Just for those who'd like to follow the scope of changes, find below the
v4->v5interdiff. v5 is now included in tip:WIP.locking/core, and also merged into tip:master. (But not propagated towards linux-next yet.)Hm, I'm experiencing early boot hangs with v5, on defconfig-ish x86-64 kernels:
[ 0.153940] rcu: Hierarchical RCU implementation. [ 0.154289] rcu: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=17. [ 0.154829] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. [ 0.155390] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=17I bisected it back to the v5 version of this patch:
Quoted 7 lines
2fd5f60fa4c3: locking/rwsem: Merge owner into count on x86-64I'm moving -tip back to -v4 meanwhile.
Thanks,
Ingo
Sorry about that. Will look into that problem.
-Longman
Waiman Long
reviewerQuoted 41 lines · Waiman Long
Quoted 40 lines · Ingo Molnar
Quoted 18 lines · Ingo Molnar
Quoted 16 lines · Waiman Long
Quoted 10 lines · Waiman Long
v5:
- Drop v4 patch 1 as it is merged into tip's locking/core branch.
- Integrate the 2 followup patches into the series. The first follow-up patch is broken into 2 pieces. The first piece comes in before the "Enable readers spinning on writer" and the 2nd piece is merged into the "Enable time-based spinning on reader-owned rwsem" patch. The 2nd followup patch is added after that.
- Add a new patch to make allwake_up_q()calls after droppingwait_lockas suggested by PeterZ.
- Incorporate numerouos suggestions by PeterZ and Davidlohr.This patchset is still being reviewed by Peter . The purpose of this series is mainly to sync up the version that Peter has and the ones that I am working on incorporating his feedback. Further changes may still be needed.
Quoted 7 lines
Quoted 4 lines
I run an overall performance test on this new patchset and present the data in this cover letter. However, I haven't run performance tests for individual patches. So the performance data listed in some of the patches may be stale.
Just for those who'd like to follow the scope of changes, find below the
v4->v5interdiff. v5 is now included in tip:WIP.locking/core, and also merged into tip:master. (But not propagated towards linux-next yet.)Hm, I'm experiencing early boot hangs with v5, on defconfig-ish x86-64 kernels:
[ 0.153940] rcu: Hierarchical RCU implementation. [ 0.154289] rcu: RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=17. [ 0.154829] rcu: RCU calculated value of scheduler-enlistment delay is 100 jiffies. [ 0.155390] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=17I bisected it back to the v5 version of this patch:
2fd5f60fa4c3: locking/rwsem: Merge owner into count on x86-64
Quoted 9 lines
Quoted 5 lines
I'm moving -tip back to -v4 meanwhile.
Thanks,
Ingo
Sorry about that. Will look into that problem.
-Longman
Yes, there is a bug in that patch. The following change should fix it:
kernel/locking/rwsem.c +0 -0
@@ -198,9 +198,15 @@
/*
* Task structure pointer compression (64-bit only):
* (owner - PAGE_OFFSET) >> (L1_CACHE_SHIFT - 2)
+ *
+ * However, init_task may lie outside of the linearly mapped physical
+ * to virtual memory range and so has to be handled separately. */
static inline unsigned long rwsem_owner_count(struct task_struct *owner) {
+ if (unlikely(owner == &init_task))
+ return RWSEM_WRITER_MASK;
+
return ((unsigned long)owner - PAGE_OFFSET) >> (L1_CACHE_SHIFT - 2); }
@@ -208,6 +214,9 @@ static inline unsigned long rwsem_count_owner(long count)
{
unsigned long writer = (unsigned long)count & RWSEM_WRITER_MASK;
+ if (unlikely(writer == RWSEM_WRITER_MASK))
+ return (unsigned long)&init_task;
+
return writer ? (writer << (L1_CACHE_SHIFT - 2)) + PAGE_OFFSET : 0; }