From: Nikolay Borisov <nborisov@suse.com>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>,
David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: let check_async_write return bool
Date: Mon, 10 May 2021 19:29:39 +0300 [thread overview]
Message-ID: <daaa1507-8dc5-14fa-d588-856c1439b9f1@suse.com> (raw)
In-Reply-To: <ac35b9ba276cf4eefcf9641a19eaabae715f6d2d.1620659830.git.johannes.thumshirn@wdc.com>
On 10.05.21 г. 18:17, Johannes Thumshirn wrote:
> The 'check_async_write' function is a helper used in
> 'btrfs_submit_metadata_bio' and it checks if asynchronous writing can be
> used for metadata.
>
> Make the function return bool and get rid of the local variable async in
> btrfs_submit_metadata_bio storing the result of check_async_write's tests.
>
> Signed-off-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Nit: Won't it make it more clear if the function is named
"should_write_async" or something along those lines?
> ---
> fs/btrfs/disk-io.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
> index c9a3036c23bf..4305e3a26a6b 100644
> --- a/fs/btrfs/disk-io.c
> +++ b/fs/btrfs/disk-io.c
> @@ -917,23 +917,22 @@ static blk_status_t btree_submit_bio_start(struct inode *inode, struct bio *bio,
> return btree_csum_one_bio(bio);
> }
>
> -static int check_async_write(struct btrfs_fs_info *fs_info,
> +static bool check_async_write(struct btrfs_fs_info *fs_info,
> struct btrfs_inode *bi)
> {
> if (btrfs_is_zoned(fs_info))
> - return 0;
> + return false;
> if (atomic_read(&bi->sync_writers))
> - return 0;
> + return false;
> if (test_bit(BTRFS_FS_CSUM_IMPL_FAST, &fs_info->flags))
> - return 0;
> - return 1;
> + return false;
> + return true;
> }
>
> blk_status_t btrfs_submit_metadata_bio(struct inode *inode, struct bio *bio,
> int mirror_num, unsigned long bio_flags)
> {
> struct btrfs_fs_info *fs_info = btrfs_sb(inode->i_sb);
> - int async = check_async_write(fs_info, BTRFS_I(inode));
> blk_status_t ret;
>
> if (btrfs_op(bio) != BTRFS_MAP_WRITE) {
> @@ -946,7 +945,7 @@ blk_status_t btrfs_submit_metadata_bio(struct inode *inode, struct bio *bio,
> if (ret)
> goto out_w_error;
> ret = btrfs_map_bio(fs_info, bio, mirror_num);
> - } else if (!async) {
> + } else if (!check_async_write(fs_info, BTRFS_I(inode))) {
> ret = btree_csum_one_bio(bio);
> if (ret)
> goto out_w_error;
>
next prev parent reply other threads:[~2021-05-10 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 15:17 [PATCH] btrfs: let check_async_write return bool Johannes Thumshirn
2021-05-10 16:29 ` Nikolay Borisov [this message]
2021-05-10 16:40 ` David Sterba
2021-05-10 19:15 ` 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=daaa1507-8dc5-14fa-d588-856c1439b9f1@suse.com \
--to=nborisov@suse.com \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@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