From: NeilBrown <neilb@suse.com>
To: Mike Snitzer <snitzer@redhat.com>, Christoph Hellwig <hch@infradead.org>
Cc: linux-block@vger.kernel.org, dm-devel@redhat.com,
Ming Lei <ming.lei@redhat.com>
Subject: Re: [dm-devel] why does __split_and_process_bio use bio_clone_bioset?
Date: Fri, 15 Jun 2018 09:34:29 +1000 [thread overview]
Message-ID: <87fu1pgcxm.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20180614200808.GA46373@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2906 bytes --]
On Thu, Jun 14 2018, Mike Snitzer wrote:
> On Thu, Jun 14 2018 at 2:12P -0400,
> Mike Snitzer <snitzer@redhat.com> wrote:
>
>> On Thu, Jun 14 2018 at 4:19am -0400,
>> Christoph Hellwig <hch@infradead.org> wrote:
>>
>> > Hi Neil,
>> >
>> > In commit 18a25da8 ("dm: ensure bio submission follows a depth-first
>> > tree walk") you've added a call to bio_clone_bioset to
>> > __split_and_process_bio. Unlike all other bio splitting code this
>> > actually allocates a new bio_vec array instead of just splitting the bio
>> > and the iterator. I can't actually find a good reason for that either
>> > in a cursory review of the code, the commit or the comments.
>> >
>> > Do you remember why this can't just use bio_clone_fast?
Good question. I don't remember having a good reason to choose it, and
if there was one I suspect I would have mentioned it in the commit
message.
So it was most likely an oversight.
Looking at the code now, I can see no justification for not using
bio_clone_fast() or similar.
Thanks for looking into this - I guess the next step is to get rid of
bio_clone_bioset() completely. Nice.
>>
>> Your question caused me to revisit this code and it is suspect for a
>> couple reasons:
>>
>> 1) I'm also not seeing why we need bio_clone_bioset()
>
> The patch below seems to work fine (given quick testing).. It also has a
> side-effect of not breaking integrity support (which commit 18a25da8
> appears to do because it isn't accounting for any of the integrity stuff
> bio_split, or dm.c:clone_bio, does).
>
> FYI, my other concerns in my my previous reply were unfounded and due to
> misreading the existing code.
>
> Neil, please still feel free to have a look at this to see if you can
> recall why you used bio_clone_bioset().
>
> If in the end you agree that the following patch is fine please let me
> know and I'll get a proper fix staged.
I agree with the patch.
Reviewed-by: NeilBrown <neilb@suse.com>
Thanks!
NeilBrown
>
> Thanks,
> Mike
>
> diff --git a/drivers/md/dm.c b/drivers/md/dm.c
> index 20a8d63..dfb4783 100644
> --- a/drivers/md/dm.c
> +++ b/drivers/md/dm.c
> @@ -1582,10 +1582,9 @@ static blk_qc_t __split_and_process_bio(struct mapped_device *md,
> * the usage of io->orig_bio in dm_remap_zone_report()
> * won't be affected by this reassignment.
> */
> - struct bio *b = bio_clone_bioset(bio, GFP_NOIO,
> - &md->queue->bio_split);
> + struct bio *b = bio_split(bio, bio_sectors(bio) - ci.sector_count,
> + GFP_NOIO, &md->queue->bio_split);
> ci.io->orig_bio = b;
> - bio_advance(bio, (bio_sectors(bio) - ci.sector_count) << 9);
> bio_chain(b, bio);
> ret = generic_make_request(bio);
> break;
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-14 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 8:19 why does __split_and_process_bio use bio_clone_bioset? Christoph Hellwig
2018-06-14 18:12 ` Mike Snitzer
2018-06-14 20:08 ` Mike Snitzer
2018-06-14 23:34 ` NeilBrown [this message]
2018-06-15 7:38 ` [dm-devel] " Christoph Hellwig
2018-06-15 18:26 ` Mike Snitzer
2018-06-16 15:20 ` Christoph Hellwig
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=87fu1pgcxm.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=dm-devel@redhat.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=snitzer@redhat.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;
as well as URLs for NNTP newsgroup(s).