From: Jan Kara <jack@suse.cz>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: Gabriel Krisman Bertazi <krisman@suse.de>,
axboe@kernel.dk, linux-kernel@vger.kernel.org,
linux-block@vger.kernel.org, Hugh Dickins <hughd@google.com>,
Keith Busch <kbusch@kernel.org>,
Liu Song <liusong@linux.alibaba.com>, Jan Kara <jack@suse.cz>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] sbitmap: Use single per-bitmap counting to wake up queued tags
Date: Thu, 10 Nov 2022 12:16:36 +0100 [thread overview]
Message-ID: <20221110111636.ufgyp4tkbzexugk2@quack3> (raw)
In-Reply-To: <2a445c5c-fd15-c0bf-8655-2fb5bde3fe67@huaweicloud.com>
Hi!
On Thu 10-11-22 17:42:49, Yu Kuai wrote:
> 在 2022/11/06 7:10, Gabriel Krisman Bertazi 写道:
> > +void sbitmap_queue_wake_up(struct sbitmap_queue *sbq, int nr)
> > {
> > - struct sbq_wait_state *ws;
> > - unsigned int wake_batch;
> > - int wait_cnt, cur, sub;
> > - bool ret;
> > + unsigned int wake_batch = READ_ONCE(sbq->wake_batch);
> > + struct sbq_wait_state *ws = NULL;
> > + unsigned int wakeups;
> > - if (*nr <= 0)
> > - return false;
> > + if (!atomic_read(&sbq->ws_active))
> > + return;
> > - ws = sbq_wake_ptr(sbq);
> > - if (!ws)
> > - return false;
> > + atomic_add(nr, &sbq->completion_cnt);
> > + wakeups = atomic_read(&sbq->wakeup_cnt);
> > - cur = atomic_read(&ws->wait_cnt);
> > do {
> > - /*
> > - * For concurrent callers of this, callers should call this
> > - * function again to wakeup a new batch on a different 'ws'.
> > - */
> > - if (cur == 0)
> > - return true;
> > - sub = min(*nr, cur);
> > - wait_cnt = cur - sub;
> > - } while (!atomic_try_cmpxchg(&ws->wait_cnt, &cur, wait_cnt));
> > -
> > - /*
> > - * If we decremented queue without waiters, retry to avoid lost
> > - * wakeups.
> > - */
> > - if (wait_cnt > 0)
> > - return !waitqueue_active(&ws->wait);
> > + if (atomic_read(&sbq->completion_cnt) - wakeups < wake_batch)
> > + return;
>
> Should it be considered that completion_cnt overflow and becomes
> negtive?
Yes, the counters can (and will) certainly overflow but since we only care
about (completion_cnt - wakeups), we should be fine - this number is always
sane (and relatively small) and in the kernel we do compile with signed
overflows being well defined.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2022-11-10 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 23:10 [PATCH] sbitmap: Use single per-bitmap counting to wake up queued tags Gabriel Krisman Bertazi
2022-11-08 23:28 ` Chaitanya Kulkarni
2022-11-09 3:03 ` Gabriel Krisman Bertazi
2022-11-09 3:35 ` Chaitanya Kulkarni
2022-11-09 22:06 ` Jens Axboe
2022-11-09 22:48 ` Gabriel Krisman Bertazi
2022-11-10 3:25 ` Jens Axboe
2022-11-10 9:42 ` Yu Kuai
2022-11-10 11:16 ` Jan Kara [this message]
2022-11-10 13:18 ` Yu Kuai
2022-11-10 15:35 ` Jan Kara
2022-11-11 0:59 ` Yu Kuai
2022-11-11 15:38 ` Jens Axboe
2022-11-14 13:23 ` Jan Kara
2022-11-14 14:20 ` [PATCH] sbitmap: Advance the queue index before waking up the queue Gabriel Krisman Bertazi
2022-11-14 14:34 ` Jan Kara
2022-11-15 3:52 ` [PATCH] sbitmap: Use single per-bitmap counting to wake up queued tags Gabriel Krisman Bertazi
2022-11-15 10:24 ` Jan Kara
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=20221110111636.ufgyp4tkbzexugk2@quack3 \
--to=jack@suse.cz \
--cc=axboe@kernel.dk \
--cc=hughd@google.com \
--cc=kbusch@kernel.org \
--cc=krisman@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liusong@linux.alibaba.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.com \
/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