From: Jan Kara <jack@suse.cz>
To: Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>, Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC 4/6] bdev: simplify waiting for concurrent claimers
Date: Wed, 25 Oct 2023 17:54:39 +0200 [thread overview]
Message-ID: <20231025155439.5otniolu5mydjoon@quack3> (raw)
In-Reply-To: <20231024-vfs-super-rework-v1-4-37a8aa697148@kernel.org>
On Tue 24-10-23 16:53:42, Christian Brauner wrote:
> Simplify the mechanism to wait for concurrent block devices claimers
> and make it possible to introduce an additional state in the following
> patches.
>
> Signed-off-by: Christian Brauner <brauner@kernel.org>
The simplification looks good but a few notes below:
> diff --git a/block/bdev.c b/block/bdev.c
> index 9deacd346192..7d19e04a8df8 100644
> --- a/block/bdev.c
> +++ b/block/bdev.c
> @@ -482,6 +482,14 @@ static bool bd_may_claim(struct block_device *bdev, void *holder,
> return true;
> }
>
> +static bool wait_claimable(const struct block_device *bdev)
> +{
> + enum bd_claim bd_claim;
> +
> + bd_claim = smp_load_acquire(&bdev->bd_claim);
> + return bd_claim == BD_CLAIM_DEFAULT;
> +}
Aren't you overdoing it here a bit? Given this is used only in a retry
loop and all the checks that need to be reliable are done under bdev_lock,
I'd say having:
return READ_ONCE(bdev->bd_claim) == BD_CLAIM_DEFAULT;
shound be fine here? And probably just inline that into the
wait_var_event() call...
> @@ -511,31 +519,25 @@ int bd_prepare_to_claim(struct block_device *bdev, void *holder,
> }
>
> /* if claiming is already in progress, wait for it to finish */
> - if (whole->bd_claiming) {
> - wait_queue_head_t *wq = bit_waitqueue(&whole->bd_claiming, 0);
> - DEFINE_WAIT(wait);
> -
> - prepare_to_wait(wq, &wait, TASK_UNINTERRUPTIBLE);
> + if (whole->bd_claim) {
This test implicitely assumes that 0 is BD_CLAIM_DEFAULT. I guess that's
fine although I somewhat prefer explicit value test like:
if (whole->bd_claim != BD_CLAIM_DEFAULT)
> mutex_unlock(&bdev_lock);
> - schedule();
> - finish_wait(wq, &wait);
> + wait_var_event(&whole->bd_claim, wait_claimable(whole));
> goto retry;
> }
>
> /* yay, all mine */
> - whole->bd_claiming = holder;
> + whole->bd_claim = BD_CLAIM_ACQUIRE;
Here I'd use WRITE_ONCE() to avoid KCSAN warnings and having to think
whether this can race with wait_claimable() or not.
> mutex_unlock(&bdev_lock);
> return 0;
> }
> EXPORT_SYMBOL_GPL(bd_prepare_to_claim); /* only for the loop driver */
>
> -static void bd_clear_claiming(struct block_device *whole, void *holder)
> +static void bd_clear_claiming(struct block_device *whole)
> {
> lockdep_assert_held(&bdev_lock);
> - /* tell others that we're done */
> - BUG_ON(whole->bd_claiming != holder);
> - whole->bd_claiming = NULL;
> - wake_up_bit(&whole->bd_claiming, 0);
> + smp_store_release(&whole->bd_claim, BD_CLAIM_DEFAULT);
> + smp_mb();
> + wake_up_var(&whole->bd_claim);
And here since we are under bdev_lock and the waiter is going to check
under bdev_lock as well, we should be able to do:
WRITE_ONCE(whole->bd_claim, BD_CLAIM_DEFAULT);
/* Pairs with barrier in prepare_to_wait_event() -> set_current_state() */
smp_mb();
wake_up_var(&whole->bd_claim);
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2023-10-25 15:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 14:53 [PATCH RFC 0/6] fs,block: yield devices Christian Brauner
2023-10-24 14:53 ` [PATCH RFC 1/6] fs: simplify setup_bdev_super() calls Christian Brauner
2023-10-25 15:29 ` Jan Kara
2023-10-27 6:42 ` Christoph Hellwig
2023-10-24 14:53 ` [PATCH RFC 2/6] xfs: simplify device handling Christian Brauner
2023-10-25 15:30 ` Jan Kara
2023-10-27 6:42 ` Christoph Hellwig
2023-10-24 14:53 ` [PATCH RFC 3/6] ext4: " Christian Brauner
2023-10-25 15:30 ` Jan Kara
2023-10-27 6:42 ` Christoph Hellwig
2023-10-24 14:53 ` [PATCH RFC 4/6] bdev: simplify waiting for concurrent claimers Christian Brauner
2023-10-25 15:54 ` Jan Kara [this message]
2023-10-27 7:21 ` Christoph Hellwig
2023-10-24 14:53 ` [PATCH RFC 5/6] block: mark device as about to be released Christian Brauner
2023-10-24 14:53 ` [PATCH RFC 6/6] fs: add ->yield_devices() Christian Brauner
2023-10-25 17:20 ` [PATCH RFC 0/6] fs,block: yield devices Jan Kara
2023-10-25 20:46 ` Christian Brauner
2023-10-26 10:35 ` Jan Kara
2023-10-26 12:07 ` Christian Brauner
2023-10-26 13:04 ` Jan Kara
2023-10-26 15:08 ` Christian Brauner
2023-10-26 15:58 ` Jan Kara
2023-10-27 7:24 ` Christoph Hellwig
2023-10-26 11:50 ` (subset) " Christian Brauner
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=20231025155439.5otniolu5mydjoon@quack3 \
--to=jack@suse.cz \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.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).