virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Weiping Zhang <zhangweiping@didichuxing.com>
To: axboe@kernel.dk, cohuck@redhat.com, mst@redhat.com, jasowang@redhat.com
Cc: linux-block@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: [RFC PATCH 0/2] use larger max_request_size for virtio_blk
Date: Thu, 5 Apr 2018 18:09:58 +0800	[thread overview]
Message-ID: <cover.1522922101.git.zhangweiping@didichuxing.com> (raw)

Hi,

For virtio block device, actually there is no a hard limit for max request
size, and virtio_blk driver set -1 to blk_queue_max_hw_sectors(q, -1U);.
But it doesn't work, because there is a default upper limitation
BLK_DEF_MAX_SECTORS (1280 sectors). So this series want to add a new helper
blk_queue_max_hw_sectors_no_limit to set a proper max reqeust size.

Weiping Zhang (2):
  blk-setting: add new helper blk_queue_max_hw_sectors_no_limit
  virtio_blk: add new module parameter to set max request size

 block/blk-settings.c       | 20 ++++++++++++++++++++
 drivers/block/virtio_blk.c | 32 ++++++++++++++++++++++++++++++--
 include/linux/blkdev.h     |  2 ++
 3 files changed, 52 insertions(+), 2 deletions(-)

-- 
2.9.4

             reply	other threads:[~2018-04-05 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 10:09 Weiping Zhang [this message]
2018-04-05 10:10 ` [RFC PATCH 1/2] blk-setting: add new helper blk_queue_max_hw_sectors_no_limit Weiping Zhang
2018-04-05 10:10 ` [RFC PATCH 2/2] virtio_blk: add new module parameter to set max request size Weiping Zhang
2018-04-05 12:24 ` [RFC PATCH 0/2] use larger max_request_size for virtio_blk Martin K. Petersen
2018-04-05 14:29 ` Jens Axboe
2018-04-07  8:30   ` Weiping Zhang

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=cover.1522922101.git.zhangweiping@didichuxing.com \
    --to=zhangweiping@didichuxing.com \
    --cc=axboe@kernel.dk \
    --cc=cohuck@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).