From: Christoph Hellwig <hch@lst.de>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Christoph Hellwig <hch@lst.de>, David Sterba <dsterba@suse.com>,
Josef Bacik <josef@toxicpanda.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 06/10] btrfs: transfer the bio counter reference to the raid submission helpers
Date: Mon, 20 Jun 2022 09:47:42 +0200 [thread overview]
Message-ID: <20220620074742.GB11832@lst.de> (raw)
In-Reply-To: <1b21e3e9-cdd9-baa6-bd39-e9489de883ff@gmx.com>
On Mon, Jun 20, 2022 at 05:50:53AM +0800, Qu Wenruo wrote:
> In fact, the bio counter for btrfs_map_bio() is just increased and to
> allow the real bios (either the RAID56 code, or submit_stripe_bio()) to
> grab extra counter to cover the full lifespan of the real bio.
>
> Thus I don't think there is any bio counter to be "transferred" here.
What is the real bio?
In the parity raid case there is:
1) the upper level btrfs_bio, which is handed off to
raid56_parity_write / raid56_parity_recover.
It then to the bios list of the rbio and is eventually completed
2) lower-level RAID bios, which have no direct connection to the
btrfs_bio, as they are all driven off the rbio-based state
machine
For the non-parity case we have
1) the upper level btrfs_bio, which is submitted to the actual devic
as the last mirror (write case) or the only bio (read case)
2) the clones for the non-last mirror writes
btrfs_submit_bio calls btrfs_bio_counter_inc_blocked before
__btrfs_map_block to protect against device replace operations,
and that protection needs to last until the last bio using the
mapping returned from __btrfs_map_block has completed.
So we don't need an extra count for the parity case. In fact we
don't really need an extra count either for the non-parity case
except for additional mirror writes. So maybe things are cleaned
up if we also add this patch (which relies on the previous ones in
this series):
---
From 6351835b133ce00e2d65a6b2a398678b45426947 Mon Sep 17 00:00:00 2001
From: Christoph Hellwig <hch@lst.de>
Date: Mon, 20 Jun 2022 09:43:48 +0200
Subject: btrfs: don't take a bio_counter reference for cloned bios
There is no need for multiple bio_counter references for a single I/O.
Just release the reference when completing the bio and avoid additional
counter roundtrips.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/btrfs/ctree.h | 1 -
fs/btrfs/dev-replace.c | 5 -----
fs/btrfs/volumes.c | 7 ++-----
3 files changed, 2 insertions(+), 11 deletions(-)
diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
index 1347c92234a56..6857897c77108 100644
--- a/fs/btrfs/ctree.h
+++ b/fs/btrfs/ctree.h
@@ -3972,7 +3972,6 @@ static inline void btrfs_init_full_stripe_locks_tree(
/* dev-replace.c */
void btrfs_bio_counter_inc_blocked(struct btrfs_fs_info *fs_info);
-void btrfs_bio_counter_inc_noblocked(struct btrfs_fs_info *fs_info);
void btrfs_bio_counter_sub(struct btrfs_fs_info *fs_info, s64 amount);
static inline void btrfs_bio_counter_dec(struct btrfs_fs_info *fs_info)
diff --git a/fs/btrfs/dev-replace.c b/fs/btrfs/dev-replace.c
index a7dd6ba25e990..aa435d04e8ef3 100644
--- a/fs/btrfs/dev-replace.c
+++ b/fs/btrfs/dev-replace.c
@@ -1288,11 +1288,6 @@ int __pure btrfs_dev_replace_is_ongoing(struct btrfs_dev_replace *dev_replace)
return 1;
}
-void btrfs_bio_counter_inc_noblocked(struct btrfs_fs_info *fs_info)
-{
- percpu_counter_inc(&fs_info->dev_replace.bio_counter);
-}
-
void btrfs_bio_counter_sub(struct btrfs_fs_info *fs_info, s64 amount)
{
percpu_counter_sub(&fs_info->dev_replace.bio_counter, amount);
diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
index 33a232c897d14..86e200d2000f9 100644
--- a/fs/btrfs/volumes.c
+++ b/fs/btrfs/volumes.c
@@ -6647,14 +6647,14 @@ static void btrfs_end_bio(struct bio *bio)
}
}
- btrfs_bio_counter_dec(bioc->fs_info);
-
if (bio != orig_bio) {
bio_endio(orig_bio);
bio_put(bio);
return;
}
+ btrfs_bio_counter_dec(bioc->fs_info);
+
/*
* Only send an error to the higher layers if it is beyond the tolerance
* threshold.
@@ -6698,8 +6698,6 @@ static void submit_stripe_bio(struct btrfs_io_context *bioc,
bio->bi_end_io = btrfs_end_bio;
bio->bi_iter.bi_sector = physical >> 9;
- btrfs_bio_counter_inc_noblocked(fs_info);
-
if (!dev || !dev->bdev ||
test_bit(BTRFS_DEV_STATE_MISSING, &dev->dev_state) ||
(btrfs_op(bio) == BTRFS_MAP_WRITE &&
@@ -6781,7 +6779,6 @@ void btrfs_submit_bio(struct btrfs_fs_info *fs_info, struct bio *bio,
submit_stripe_bio(bioc, bio, dev_nr, should_clone);
}
- btrfs_bio_counter_dec(fs_info);
}
static bool dev_args_match_fs_devices(const struct btrfs_dev_lookup_args *args,
--
2.30.2
next prev parent reply other threads:[~2022-06-20 7:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:04 cleanup btrfs bio submission v2 Christoph Hellwig
2022-06-17 10:04 ` [PATCH 01/10] btrfs: remove a bunch of pointles stripe_len arguments Christoph Hellwig
2022-06-20 17:16 ` David Sterba
2022-06-20 17:38 ` Christoph Hellwig
2022-06-22 4:19 ` Christoph Hellwig
2022-06-22 14:07 ` David Sterba
2022-06-22 4:30 ` Qu Wenruo
2022-06-17 10:04 ` [PATCH 02/10] btrfs: return proper mapped length for RAID56 profiles in __btrfs_map_block() Christoph Hellwig
2022-06-17 10:04 ` [PATCH 03/10] btrfs: remove the btrfs_map_bio return value Christoph Hellwig
2022-06-17 10:04 ` [PATCH 04/10] btrfs: remove the raid56_parity_write " Christoph Hellwig
2022-06-17 10:38 ` Qu Wenruo
2022-06-18 11:04 ` Johannes Thumshirn
2022-06-17 10:04 ` [PATCH 05/10] btrfs: remove the raid56_parity_recover " Christoph Hellwig
2022-06-18 11:06 ` Johannes Thumshirn
2022-06-19 6:35 ` Christoph Hellwig
2022-06-19 10:35 ` Qu Wenruo
2022-06-17 10:04 ` [PATCH 06/10] btrfs: transfer the bio counter reference to the raid submission helpers Christoph Hellwig
2022-06-19 10:45 ` Qu Wenruo
2022-06-19 21:50 ` Qu Wenruo
2022-06-20 7:47 ` Christoph Hellwig [this message]
2022-06-20 8:03 ` Qu Wenruo
2022-06-20 8:09 ` Christoph Hellwig
2022-06-20 7:37 ` Christoph Hellwig
2022-06-20 7:45 ` Qu Wenruo
2022-06-20 7:49 ` Christoph Hellwig
2022-06-17 10:04 ` [PATCH 07/10] btrfs: simplify the reloc root check in btrfs_submit_data_write_bio Christoph Hellwig
2022-06-17 10:04 ` [PATCH 08/10] btrfs: handle allocation failure in btrfs_wq_submit_bio gracefully Christoph Hellwig
2022-06-28 15:20 ` Boris Burkov
2022-06-17 10:04 ` [PATCH 09/10] btrfs: remove the btrfs_submit_dio_bio return value Christoph Hellwig
2022-06-17 10:04 ` [PATCH 10/10] btrfs: remove bioc->stripes_pending Christoph Hellwig
2022-06-20 8:18 ` Nikolay Borisov
2022-06-20 8:34 ` Nikolay Borisov
2022-06-20 8:53 ` Christoph Hellwig
2022-06-20 9:34 ` Nikolay Borisov
2022-06-20 11:23 ` Christoph Hellwig
2022-06-22 16:07 ` David Sterba
2022-06-22 16:15 ` Christoph Hellwig
2022-07-07 18:34 ` David Sterba
2022-06-20 13:04 ` cleanup btrfs bio submission v2 Nikolay Borisov
2022-07-07 18:35 ` David Sterba
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=20220620074742.GB11832@lst.de \
--to=hch@lst.de \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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