summaryrefslogtreecommitdiffstats
path: root/kernel/reboot.c
diff options
context:
space:
mode:
authorWaiman Long <longman@redhat.com>2019-05-20 16:59:07 -0400
committerIngo Molnar <mingo@kernel.org>2019-06-17 12:28:00 +0200
commit00f3c5a3df2c1e3dab14d0dd2b71f852d46be97f (patch)
treee2a43358ed69c8cab7b5801552797cdd61d69b44 /kernel/reboot.c
parent4f23dbc1e657951e5d94c60369bc1db065961fb3 (diff)
downloadtalos-op-linux-00f3c5a3df2c1e3dab14d0dd2b71f852d46be97f.tar.gz
talos-op-linux-00f3c5a3df2c1e3dab14d0dd2b71f852d46be97f.zip
locking/rwsem: Always release wait_lock before waking up tasks
With 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. The rwsem_try_write_lock() function is also modified to read the rwsem count directly to avoid stale count value. Suggested-by: Peter Zijlstra <peterz@infradead.org> Signed-off-by: Waiman Long <longman@redhat.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Borislav Petkov <bp@alien8.de> Cc: Davidlohr Bueso <dave@stgolabs.net> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Tim Chen <tim.c.chen@linux.intel.com> Cc: Will Deacon <will.deacon@arm.com> Cc: huang ying <huang.ying.caritas@gmail.com> Link: https://lkml.kernel.org/r/20190520205918.22251-9-longman@redhat.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'kernel/reboot.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud