sched/wait: Determine whether the wait queue is empty before waking up
RFC PATCH 1/1 sched/wait: Determine whether the wait queue is empty before waking up
When we did some benchmark tests (such as pipe tests), we found that the wake behavior was still triggered when the wait queue was empty, even though it would exit later.
This processing consumes some unnecessary resources. Can we determine at the beginning of the wake up whether there are elements in the queue that need to be awakened? I think this judgment is probably good for performance and should be safe.
Looking forward to your reply, thank you.
--- kernel/sched/wait.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/sched/wait.c +3 -0
@@ -205,6 +205,9 @@ void __wake_up_sync_key(struct wait_queue_head *wq_head, unsigned int mode,if (unlikely (!wq_head))return ; +if (unlikely (!wq_has_sleeper (wq_head))) +return ; +__wake_up_common_lock (wq_head, mode,1 ,WF_SYNC , key); }EXPORT_SYMBOL_GPL (__wake_up_sync_key);
Signature · 1 line
2.20.1
Valentin Schneider
reviewerQuoted 21 lines · Wang You
When we did some benchmark tests (such as pipe tests), we found that the wake behavior was still triggered when the wait queue was empty, even though it would exit later.
This processing consumes some unnecessary resources. Can we determine at the beginning of the wake up whether there are elements in the queue that need to be awakened? I think this judgment is probably good for performance and should be safe.
Looking forward to your reply, thank you.
Signed-off-by Wang You <[email protected]>--- kernel/sched/wait.c | 3 +++ 1 file changed, 3 insertions(+)kernel/sched/wait.c +0
-0
kernel/sched/wait.c void __wake_up_sync_key(struct wait_queue_head *wq_head, unsigned int mode, · line 210
Quoted 6 lines
kernel/sched/wait.c +3
-0@@ -205,6 +205,9 @@ void __wake_up_sync_key(struct wait_queue_head *wq_head, unsigned int mode,if (unlikely (!wq_head))return ; +if (unlikely (!wq_has_sleeper (wq_head))) +return ; +
Hm so I suppose that if we end up in wake_up*() then the update of the wait condition has been done (so this shouldn't lead to missed wakeups), but that still means an extra smp_mb() before grabbing the wq_head->lock.
I'd suggest benchmarking the change, this is going to cause unwanted overhead when dealing with busy queues, and I'm not sure it's saving much vs grabbing wq_head->lock before noticing the list is empty.
Quoted 5 lines
kernel/sched/wait.c +0
-1__wake_up_common_lock (wq_head, mode,1 ,WF_SYNC , key); }EXPORT_SYMBOL_GPL (__wake_up_sync_key); --2.20.1