From: Ming Lei <ming.lei@redhat.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Jens Axboe <axboe@fb.com>,
Linux Block Layer Mailinglist <linux-block@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Jan Kara <jack@suse.cz>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH] block: respect virtual boundary mask in bvecs
Date: Mon, 5 Nov 2018 18:55:50 +0800 [thread overview]
Message-ID: <20181105105548.GC12367@ming.t460p> (raw)
In-Reply-To: <20181105102301.9752-1-jthumshirn@suse.de>
On Mon, Nov 05, 2018 at 11:23:01AM +0100, Johannes Thumshirn wrote:
> With drivers like iSer we are seeing a lot of bio splitting and smaller I/Os
> being submitted to the driver.
>
> The root cause of this issue that the virtual boundary mask code does not take
> into consideration that some of the memory segments in the SG list may have
> come from a huge memory page that is being managed in the SG list as 4K
I guess you mean something like 64K PAGE_SIZE, instead of huge page.
> blocks. This means that many of the segments in the SG list will have an
> offset into the page that is not 0 but will be a multiple of 4K.
>
> Cc: Jan Kara <jack@suse.cz>
> Cc: Sagi Grimberg <sagi@grimberg.me>
> Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> ---
> block/blk-merge.c | 2 +-
> block/blk.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/block/blk-merge.c b/block/blk-merge.c
> index 6b5ad275ed56..208658a901c6 100644
> --- a/block/blk-merge.c
> +++ b/block/blk-merge.c
> @@ -46,7 +46,7 @@ static inline bool bio_will_gap(struct request_queue *q,
> bio_get_first_bvec(prev_rq->bio, &pb);
> else
> bio_get_first_bvec(prev, &pb);
> - if (pb.bv_offset)
> + if (pb.bv_offset & queue_virt_boundary(q))
> return true;
The change should only make difference in case that PAGE_SIZE is bigger
than 4K. If yes, please add the description in commit log.
Thanks,
Ming
next prev parent reply other threads:[~2018-11-05 20:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 10:23 [PATCH] block: respect virtual boundary mask in bvecs Johannes Thumshirn
2018-11-05 10:55 ` Ming Lei [this message]
2018-11-05 11:50 ` Johannes Thumshirn
2018-11-05 12:01 ` Ming Lei
2018-11-06 12:34 ` Johannes Thumshirn
2018-11-06 14:56 ` Ming Lei
2018-11-06 15:14 ` Keith Busch
2018-11-07 3:14 ` Sagi Grimberg
2018-11-07 3:11 ` Sagi Grimberg
2018-11-06 14:31 ` Keith Busch
2018-11-06 14:53 ` Bart Van Assche
2018-11-06 14:56 ` Johannes Thumshirn
2018-11-07 3:30 ` Sagi Grimberg
2018-11-07 16:10 ` Bart Van Assche
2018-11-07 16:10 ` Bart Van Assche
2018-11-08 15:04 ` 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=20181105105548.GC12367@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@fb.com \
--cc=hare@suse.de \
--cc=jack@suse.cz \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sagi@grimberg.me \
/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 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.