From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>
Subject: [PATCH V3 00/10] block: enable multi-page bvec for passthrough IO
Date: Fri, 29 Mar 2019 15:07:53 +0800 [thread overview]
Message-ID: <20190329070803.10958-1-ming.lei@redhat.com> (raw)
Hi,
Now the whole IO stack is capable of handling multi-page bvec, and it has
been enabled in the normal FS IO path. However, it isn't done for
passthrough IO.
Without enabling multi-bvec for passthough IO, we won't go ahead for
optimizing related IO paths, such as bvec merging, bio_add_pc_page
simplification.
This patch enables multi-page bvec for passthrough IO. Turns out
bio_add_pc_page() is simpliefied a lot, especially the physical segment
number of passthrough bio is always same with bio.bi_vcnt. Also the
bvec merging inside bio is killed.
blktests(block/029) is added for covering passthough IO path, and this
patchset does pass the new block/029 test.
V3:
- fix build warning on patch 1 and 7, only the two patches are
changed
V2:
- add new patch of 'block: avoid to break XEN by multi-page bvec'
- add one new patch to cleanup bio_add_pc_page()
- add another two new patches for cleanup of mapping bvec to sg
- most of others are patch style changes
Ming Lei (10):
block: pass page to xen_biovec_phys_mergeable
block: avoid to break XEN by multi-page bvec
block: don't merge adjacent bvecs to one segment in bio
blk_queue_split
block: cleanup bio_add_pc_page
block: check if page is mergeable in one helper
block: put the same page when adding it to bio
block: enable multi-page bvec for passthrough IO
block: remove argument of 'request_queue' from __blk_bvec_map_sg
block: reuse __blk_bvec_map_sg() for mapping page sized bvec
block: don't check if adjacent bvecs in one bio can be mergeable
block/bio.c | 134 ++++++++++++++++++++++++++++---------------------
block/blk-merge.c | 106 +++++++++++++++++++-------------------
block/blk.h | 2 +-
drivers/xen/biomerge.c | 5 +-
include/linux/bio.h | 3 ++
include/xen/xen.h | 4 +-
6 files changed, 137 insertions(+), 117 deletions(-)
--
2.9.5
next reply other threads:[~2019-03-29 7:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-29 7:07 Ming Lei [this message]
2019-03-29 7:07 ` [PATCH V3 01/10] block: pass page to xen_biovec_phys_mergeable Ming Lei
2019-03-29 7:07 ` [PATCH V3 02/10] block: avoid to break XEN by multi-page bvec Ming Lei
2019-03-29 7:07 ` [PATCH V3 03/10] block: don't merge adjacent bvecs to one segment in bio blk_queue_split Ming Lei
2019-03-29 7:07 ` [PATCH V3 04/10] block: cleanup bio_add_pc_page Ming Lei
2019-03-29 7:07 ` [PATCH V3 05/10] block: check if page is mergeable in one helper Ming Lei
2019-03-29 7:07 ` [PATCH V3 06/10] block: put the same page when adding it to bio Ming Lei
2019-03-29 7:08 ` [PATCH V3 07/10] block: enable multi-page bvec for passthrough IO Ming Lei
2019-03-29 7:08 ` [PATCH V3 08/10] block: remove argument of 'request_queue' from __blk_bvec_map_sg Ming Lei
2019-03-29 7:08 ` [PATCH V3 09/10] block: reuse __blk_bvec_map_sg() for mapping page sized bvec Ming Lei
2019-03-29 7:08 ` [PATCH V3 10/10] block: don't check if adjacent bvecs in one bio can be mergeable Ming Lei
2019-03-29 14:20 ` [PATCH V3 00/10] block: enable multi-page bvec for passthrough IO Jens Axboe
2019-03-29 14:22 ` Jens Axboe
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=20190329070803.10958-1-ming.lei@redhat.com \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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