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>, ris Ostrovsky <boris.ostrovsky@oracle.com>, Juergen Gross <jgross@suse.com>, xen-devel@lists.xenproject.org, Omar Sandoval <osandov@fb.com>, Christoph Hellwig <hch@lst.de> Subject: [PATCH 0/6] block: enable multi-page bvec for passthrough IO Date: Sat, 9 Mar 2019 09:37:31 +0800 [thread overview] Message-ID: <20190309013737.27741-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. https://marc.info/?l=linux-block&m=155175063417139&w=2 Ming Lei (6): block: pass page to xen_biovec_phys_mergeable block: don't merge adjacent bvecs to one segment in bio blk_queue_split 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: don't check if adjacent bvecs in one bio can be mergeable block/bio.c | 121 +++++++++++++++++++++++++++---------------------- block/blk-merge.c | 98 ++++++++++++++++++++------------------- block/blk.h | 2 +- drivers/xen/biomerge.c | 5 +- include/linux/bio.h | 12 ++++- include/xen/xen.h | 2 +- 6 files changed, 134 insertions(+), 106 deletions(-) Cc: ris Ostrovsky <boris.ostrovsky@oracle.com> Cc: Juergen Gross <jgross@suse.com> Cc: xen-devel@lists.xenproject.org Cc: Omar Sandoval <osandov@fb.com> Cc: Christoph Hellwig <hch@lst.de> -- 2.9.5
WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com> To: Jens Axboe <axboe@kernel.dk> Cc: Juergen Gross <jgross@suse.com>, Ming Lei <ming.lei@redhat.com>, linux-block@vger.kernel.org, xen-devel@lists.xenproject.org, ris Ostrovsky <boris.ostrovsky@oracle.com>, Christoph Hellwig <hch@lst.de>, Omar Sandoval <osandov@fb.com> Subject: [PATCH 0/6] block: enable multi-page bvec for passthrough IO Date: Sat, 9 Mar 2019 09:37:31 +0800 [thread overview] Message-ID: <20190309013737.27741-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. https://marc.info/?l=linux-block&m=155175063417139&w=2 Ming Lei (6): block: pass page to xen_biovec_phys_mergeable block: don't merge adjacent bvecs to one segment in bio blk_queue_split 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: don't check if adjacent bvecs in one bio can be mergeable block/bio.c | 121 +++++++++++++++++++++++++++---------------------- block/blk-merge.c | 98 ++++++++++++++++++++------------------- block/blk.h | 2 +- drivers/xen/biomerge.c | 5 +- include/linux/bio.h | 12 ++++- include/xen/xen.h | 2 +- 6 files changed, 134 insertions(+), 106 deletions(-) Cc: ris Ostrovsky <boris.ostrovsky@oracle.com> Cc: Juergen Gross <jgross@suse.com> Cc: xen-devel@lists.xenproject.org Cc: Omar Sandoval <osandov@fb.com> Cc: Christoph Hellwig <hch@lst.de> -- 2.9.5 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
next reply other threads:[~2019-03-09 1:58 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-09 1:37 Ming Lei [this message] 2019-03-09 1:37 ` [PATCH 0/6] block: enable multi-page bvec for passthrough IO Ming Lei 2019-03-09 1:37 ` [PATCH 1/6] block: pass page to xen_biovec_phys_mergeable Ming Lei 2019-03-09 1:37 ` Ming Lei 2019-03-11 14:16 ` Christoph Hellwig 2019-03-11 14:16 ` Christoph Hellwig 2019-03-11 19:57 ` Boris Ostrovsky 2019-03-11 19:57 ` Boris Ostrovsky 2019-03-09 1:37 ` [PATCH 2/6] block: don't merge adjacent bvecs to one segment in bio blk_queue_split Ming Lei 2019-03-09 1:37 ` Ming Lei 2019-03-11 14:21 ` Christoph Hellwig 2019-03-11 14:21 ` Christoph Hellwig 2019-03-12 1:22 ` Ming Lei 2019-03-12 1:22 ` Ming Lei 2019-03-11 19:58 ` Boris Ostrovsky 2019-03-11 19:58 ` Boris Ostrovsky 2019-03-09 1:37 ` [PATCH 3/6] block: check if page is mergeable in one helper Ming Lei 2019-03-11 14:23 ` Christoph Hellwig 2019-03-17 8:05 ` Ming Lei 2019-03-09 1:37 ` [PATCH 4/6] block: put the same page when adding it to bio Ming Lei 2019-03-11 14:28 ` Christoph Hellwig 2019-03-09 1:37 ` [PATCH 5/6] block: enable multi-page bvec for passthrough IO Ming Lei 2019-03-11 14:35 ` Christoph Hellwig 2019-03-12 1:06 ` Ming Lei 2019-03-09 1:37 ` [PATCH 6/6] block: don't check if adjacent bvecs in one bio can be mergeable Ming Lei 2019-03-11 14:40 ` Christoph Hellwig 2019-03-12 1:19 ` 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=20190309013737.27741-1-ming.lei@redhat.com \ --to=ming.lei@redhat.com \ --cc=axboe@kernel.dk \ --cc=boris.ostrovsky@oracle.com \ --cc=hch@lst.de \ --cc=jgross@suse.com \ --cc=linux-block@vger.kernel.org \ --cc=osandov@fb.com \ --cc=xen-devel@lists.xenproject.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.