From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: Jens Axboe <axboe@fb.com>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] blk-mq: Use non-atomic operations to manipulate the sw-ctx busy bits
Date: Wed, 31 Aug 2016 18:18:49 -0700 [thread overview]
Message-ID: <20160901011849.GA8276@vader> (raw)
In-Reply-To: <aa1d8314-3c5e-4554-61e1-95c61aa11624@sandisk.com>
On Wed, Aug 31, 2016 at 03:03:24PM -0700, Bart Van Assche wrote:
> Protect sw-ctx busy bit manipulations via the sw queue lock.
> This allows to convert the atomic bit operations into slightly
> faster non-atomic operations. Document that blk_mq_run_hw_queues()
> tests these bits without holding the sw queue lock.
>
> Signed-off-by: Bart Van Assche <bart.vanassche@sandisk.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Sagi Grimberg <sagi@grimberg.me>
> ---
> block/blk-mq.c | 16 +++++++++++++---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/block/blk-mq.c b/block/blk-mq.c
> index 13f5a6c..0dcafa6 100644
> --- a/block/blk-mq.c
> +++ b/block/blk-mq.c
> @@ -66,8 +66,9 @@ static void blk_mq_hctx_mark_pending(struct blk_mq_hw_ctx *hctx,
> {
> struct blk_align_bitmap *bm = get_bm(hctx, ctx);
>
> + lockdep_assert_held(&ctx->lock);
> if (!test_bit(CTX_TO_BIT(hctx, ctx), &bm->word))
> - set_bit(CTX_TO_BIT(hctx, ctx), &bm->word);
> + __set_bit(CTX_TO_BIT(hctx, ctx), &bm->word);
> }
>
> static void blk_mq_hctx_clear_pending(struct blk_mq_hw_ctx *hctx,
> @@ -75,7 +76,8 @@ static void blk_mq_hctx_clear_pending(struct blk_mq_hw_ctx *hctx,
> {
> struct blk_align_bitmap *bm = get_bm(hctx, ctx);
>
> - clear_bit(CTX_TO_BIT(hctx, ctx), &bm->word);
> + lockdep_assert_held(&ctx->lock);
> + __clear_bit(CTX_TO_BIT(hctx, ctx), &bm->word);
> }
NAK, we can't protect each bit with a separate lock, multiple software
queues share the bitmap. There's a race if we do non-atomic bit
operations on two software queues with bits in the same word.
--
Omar
next prev parent reply other threads:[~2016-09-01 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 22:03 [PATCH] blk-mq: Use non-atomic operations to manipulate the sw-ctx busy bits Bart Van Assche
2016-09-01 1:18 ` Omar Sandoval [this message]
2016-09-01 3:13 ` Bart Van Assche
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=20160901011849.GA8276@vader \
--to=osandov@osandov.com \
--cc=axboe@fb.com \
--cc=bart.vanassche@sandisk.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=sagi@grimberg.me \
/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