From: Gabriel Krisman Bertazi <krisman@suse.de>
To: axboe@kernel.dk
Cc: mingo@redhat.com, peterz@infradead.org, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
liusong@linux.alibaba.com, chaitanyak@nvidia.com,
Gabriel Krisman Bertazi <krisman@suse.de>
Subject: [PATCH 0/3] sbitmap: Fix two issues in the per-bitmap wakeup counter code
Date: Tue, 15 Nov 2022 17:45:50 -0500 [thread overview]
Message-ID: <20221115224553.23594-1-krisman@suse.de> (raw)
Jan reported two issues in the original thread.
The first is that wake_index was not updated after returning from
sbq_wake_ptr which meant we'd have to empty the wq before moving to the
next one. Patch 1/3 in this series reorders the code to avoid this
condition, increasing fairness of queue selection and preventing
starvation. I sent this patch already on the other thread and Jan
reviewed it, but since it is a small one, and a dependency for the
other, I'm resending it a along this series.
The second issue is trickier. When the selected queue is emptied after
the waitqueue_active check and before wake_up_nr, there is no waiters to
be awaken in that queue, even if other queues might have it. This
causes us to loose one too many wakeups, and there might not be enough
requests in flight to wake up every queued request.
The proposed fix, is to walk through every queue after doing the atomic
update, such that we ensure any waiters already queued are candidates
for awakening, and that we awake at least 1 waiter in any of the queues.
The patch is a bit more complex than the suggestion since it avoids
partial updates to wake_index, which measurably hurt performance
unnecessarily.
It survived the same tests done on the original patch.
btw, I'm still missing the latency and utilisation reports. I haven't
forgotten about it, but I didn't have a chance to collect them
yet. Sorry. I will follow up with them for completeness, even if the
original patch is already queued.
Gabriel Krisman Bertazi (3):
sbitmap: Advance the queue index before waking up a queue
wait: Return number of exclusive waiters awaken
sbitmap: Try each queue to wake up at least one waiter
include/linux/wait.h | 2 +-
kernel/sched/wait.c | 18 +++++++++++-------
lib/sbitmap.c | 36 +++++++++++++++++++-----------------
3 files changed, 31 insertions(+), 25 deletions(-)
--
2.35.3
next reply other threads:[~2022-11-15 22:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 22:45 Gabriel Krisman Bertazi [this message]
2022-11-15 22:45 ` [PATCH 1/3] sbitmap: Advance the queue index before waking up a queue Gabriel Krisman Bertazi
2022-11-15 22:45 ` [PATCH 2/3] wait: Return number of exclusive waiters awaken Gabriel Krisman Bertazi
2022-11-16 11:06 ` Jan Kara
2022-11-16 20:22 ` Peter Zijlstra
2022-11-15 22:45 ` [PATCH 3/3] sbitmap: Try each queue to wake up at least one waiter Gabriel Krisman Bertazi
2022-11-16 11:09 ` Jan Kara
2022-11-16 18:49 ` [PATCH 0/3] sbitmap: Fix two issues in the per-bitmap wakeup counter code Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221115224553.23594-1-krisman@suse.de \
--to=krisman@suse.de \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liusong@linux.alibaba.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).