From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: David Sterba <dsterba@suse.cz>,
Nikolay Borisov <nborisov@suse.com>,
Josef Bacik <josef@toxicpanda.com>,
"linux-btrfs @ vger . kernel . org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v4 2/5] btrfs: use BIOs instead of buffer_heads from superblock writeout
Date: Wed, 5 Feb 2020 10:16:05 -0800 [thread overview]
Message-ID: <20200205181605.GA11348@infradead.org> (raw)
In-Reply-To: <20200205143831.13959-3-johannes.thumshirn@wdc.com>
On Wed, Feb 05, 2020 at 11:38:28PM +0900, Johannes Thumshirn wrote:
> +static void btrfs_end_super_write(struct bio *bio)
> {
> + struct btrfs_device *device = bio->bi_private;
> + struct bio_vec *bvec;
> + struct bvec_iter_all iter_all;
> + struct page *page;
> +
> + bio_for_each_segment_all(bvec, bio, iter_all) {
> + page = bvec->bv_page;
> +
> + if (blk_status_to_errno(bio->bi_status)) {
Nit: this could simply check bio->bi_status without a conversion.
> + btrfs_warn_rl_in_rcu(device->fs_info,
> + "lost page write due to IO error on %s",
> + rcu_str_deref(device->name));
But maybe you want to print the error here?
> + gfp_mask = mapping_gfp_constraint(mapping, ~__GFP_FS) | __GFP_NOFAIL;
Same comment on the ask as in the previous patch.
> + u8 *ptr;
I'd use a typed pointer here again..
> + ptr = kmap(page);
> + memcpy(ptr, sb, BTRFS_SUPER_INFO_SIZE);
With which you could do a struct assignment here and very slightly
improve type safety.
> @@ -3497,9 +3506,23 @@ static int write_dev_supers(struct btrfs_device *device,
> op_flags = REQ_SYNC | REQ_META | REQ_PRIO;
> if (i == 0 && !btrfs_test_opt(device->fs_info, NOBARRIER))
> op_flags |= REQ_FUA;
Question on the existing code: why is it safe to not use FUA for the
subsequent superblocks?
> +
> + /*
> + * Directly use BIOs here instead of relying on the page-cache
> + * to do I/O, so we don't loose the ability to do integrity
> + * checking.
> + */
> + bio = bio_alloc(gfp_mask, 1);
> + bio_set_dev(bio, device->bdev);
> + bio->bi_iter.bi_sector = bytenr >> SECTOR_SHIFT;
> + bio->bi_private = device;
> + bio->bi_end_io = btrfs_end_super_write;
> + bio_add_page(bio, page, BTRFS_SUPER_INFO_SIZE,
> + offset_in_page(bytenr));
Missing return value check. But given that it is a single page and
can't error out please switch to __bio_add_page here.
> + bio->bi_opf = REQ_OP_WRITE | op_flags;
You could kill the op_flags variable and just assign everything directly
to bio->bi_opf.
next prev parent reply other threads:[~2020-02-05 18:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 14:38 [PATCH v4 0/5] btrfs: remove buffer heads form superblock handling Johannes Thumshirn
2020-02-05 14:38 ` [PATCH v4 1/5] btrfs: use the page-cache for super block reading Johannes Thumshirn
2020-02-05 16:53 ` Christoph Hellwig
2020-02-06 8:17 ` Johannes Thumshirn
2020-02-06 14:57 ` Christoph Hellwig
2020-02-06 15:29 ` Johannes Thumshirn
2020-02-07 16:13 ` David Sterba
2020-02-10 7:16 ` Johannes Thumshirn
2020-02-06 9:29 ` Johannes Thumshirn
2020-02-05 14:38 ` [PATCH v4 2/5] btrfs: use BIOs instead of buffer_heads from superblock writeout Johannes Thumshirn
2020-02-05 18:16 ` Christoph Hellwig [this message]
2020-02-06 8:20 ` Johannes Thumshirn
2020-02-06 14:59 ` Christoph Hellwig
2020-02-06 15:18 ` Johannes Thumshirn
2020-02-07 16:08 ` David Sterba
2020-02-05 14:38 ` [PATCH v4 3/5] btrfs: remove btrfsic_submit_bh() Johannes Thumshirn
2020-02-05 14:38 ` [PATCH v4 4/5] btrfs: remove buffer_heads from btrfsic_process_written_block() Johannes Thumshirn
2020-02-05 14:38 ` [PATCH v4 5/5] btrfs: remove buffer_heads form superblock mirror integrity checking Johannes Thumshirn
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=20200205181605.GA11348@infradead.org \
--to=hch@infradead.org \
--cc=dsterba@suse.cz \
--cc=johannes.thumshirn@wdc.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@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