From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Ming Lei <ming.lei@canonical.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
stable@vger.kernel.org, tom.leiming@gmail.com,
Keith Busch <keith.busch@intel.com>,
Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: [PATCH 1/4] block: bio: introduce helpers to get the 1st and last bvec
Date: Mon, 15 Feb 2016 22:06:47 +0200 [thread overview]
Message-ID: <56C22FD7.4020005@dev.mellanox.co.il> (raw)
In-Reply-To: <20160215174212.648098b0@tom-T450>
> Cc Kent and Keith.
>
> Follows another version which should be more efficient.
> Kent and Keith, I appreciate much if you may give a review on it.
>
> diff --git a/include/linux/bio.h b/include/linux/bio.h
> index 56d2db8..ef45fec 100644
> --- a/include/linux/bio.h
> +++ b/include/linux/bio.h
> @@ -278,11 +278,21 @@ static inline void bio_get_first_bvec(struct bio *bio, struct bio_vec *bv)
> */
> static inline void bio_get_last_bvec(struct bio *bio, struct bio_vec *bv)
> {
> - struct bvec_iter iter;
> + struct bvec_iter iter = bio->bi_iter;
> + int idx;
> +
> + bio_advance_iter(bio, &iter, iter.bi_size);
> +
> + WARN_ON(!iter.bi_idx && !iter.bi_bvec_done);
> +
> + if (!iter.bi_bvec_done)
> + idx = iter.bi_idx - 1;
> + else /* in the middle of bvec */
> + idx = iter.bi_idx;
>
> - bio_for_each_segment(*bv, bio, iter)
> - if (bv->bv_len == iter.bi_size)
> - break;
> + *bv = bio->bi_io_vec[idx];
> + if (iter.bi_bvec_done)
> + bv->bv_len = iter.bi_bvec_done;
> }
>
> /*
>
This looks good too.
>
>>
>> However, given that it's a regression bug fix I'm not sure it's the best
>> idea to add logic here.
>
> But the issue is obviously in bio_will_gap(), isn't it?
>
> Simply reverting 52cc6eead9095(block: blk-merge: fast-clone bio when splitting rw bios)
> still might cause performance regression too.
That's correct. I assume that the bio splitting code affects
specific I/O pattern (gappy), however bio_will_gap is also tested
for bio merges (even if the bios won't merge eventually). This means
that each merge check will invoke bio_advance_iter() which is something
I'd like to avoid...
next prev parent reply other threads:[~2016-02-15 20:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1455519687-23873-1-git-send-email-ming.lei@canonical.com>
2016-02-15 7:01 ` [PATCH 1/4] block: bio: introduce helpers to get the 1st and last bvec Ming Lei
2016-02-15 8:19 ` Sagi Grimberg
2016-02-15 9:42 ` Ming Lei
2016-02-15 20:06 ` Sagi Grimberg [this message]
2016-02-16 13:03 ` Ming Lei
2016-02-17 3:08 ` Elliott, Robert (Persistent Memory)
2016-02-18 4:24 ` Kent Overstreet
2016-02-18 6:16 ` Ming Lei
2016-02-19 1:47 ` Ming Lei
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=56C22FD7.4020005@dev.mellanox.co.il \
--to=sagig@dev.mellanox.co.il \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=keith.busch@intel.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=stable@vger.kernel.org \
--cc=tom.leiming@gmail.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