All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <tom.leiming@gmail.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>, Mike Snitzer <snitzer@redhat.com>,
	Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: [PATCH 0/3] block: fix mismatch of figuring out physical segment number
Date: Mon, 6 Aug 2018 10:37:11 +0800	[thread overview]
Message-ID: <CACVXFVNhqmyL4cHJ--k+cOhqCA2vkaLGCXnxEzB3urhrC=AAzg@mail.gmail.com> (raw)
In-Reply-To: <20180731104914.17249-1-ming.lei@redhat.com>

On Tue, Jul 31, 2018 at 6:49 PM, Ming Lei <ming.lei@redhat.com> wrote:
> Hi,
>
> This patchset fixes one issue related with physical segment computation,
> which is found by Mike. In case of dm-rq, the warning of 'blk_cloned_rq_check_limits:
> over max segments limit' can be triggered easily.
>
> Follows the cause:
>
> 1) in IO fast path(blk_queue_split()), we always figure out physical segment number
> no matter the flag of QUEUE_FLAG_NO_SG_MERGE is set or not.
>
> 2) only blk_recount_segments() and blk_recalc_rq_segments() uses the flag of
> QUEUE_FLAG_NO_SG_MERGE, but the two are only called in some unusual
> cases, such as request clone in dm-rq.
>
> 3) the above two computation don't match, and cause the warning of
> "blk_cloned_rq_check_limits: over max segments limit".
>
> This patchset fixes this issue by killing the queue flag since it is basically
> bypassed since v4.4, and no one complains that at all. Also multipage bvec will
> come soon, and it doesn't make sense to keep QUEUE_FLAG_NO_SG_MERGE any more.
>
>
> Ming Lei (3):
>   block: don't use bio->bi_vcnt to figure out segment number
>   block: kill QUEUE_FLAG_NO_SG_MERGE
>   block: kill BLK_MQ_F_SG_MERGE
>
>  block/blk-merge.c            | 39 +++++++--------------------------------
>  block/blk-mq-debugfs.c       |  2 --
>  block/blk-mq.c               |  3 ---
>  drivers/block/loop.c         |  2 +-
>  drivers/block/nbd.c          |  2 +-
>  drivers/block/rbd.c          |  2 +-
>  drivers/block/skd_main.c     |  1 -
>  drivers/block/xen-blkfront.c |  2 +-
>  drivers/md/dm-rq.c           |  2 +-
>  drivers/md/dm-table.c        | 13 -------------
>  drivers/mmc/core/queue.c     |  3 +--
>  drivers/scsi/scsi_lib.c      |  2 +-
>  include/linux/blk-mq.h       |  1 -
>  include/linux/blkdev.h       |  1 -
>  14 files changed, 14 insertions(+), 61 deletions(-)
>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Mike Snitzer <snitzer@redhat.com>
> Cc: Kent Overstreet <kent.overstreet@gmail.com>

Hello Guys,

Ping...


Thanks,
Ming Lei

      parent reply	other threads:[~2018-08-06  2:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 10:49 [PATCH 0/3] block: fix mismatch of figuring out physical segment number Ming Lei
2018-07-31 10:49 ` [PATCH 1/3] block: don't use bio->bi_vcnt to figure out " Ming Lei
2018-08-01 14:52   ` Christoph Hellwig
2018-07-31 10:49 ` [PATCH 2/3] block: kill QUEUE_FLAG_NO_SG_MERGE Ming Lei
2018-08-01 14:54   ` Christoph Hellwig
2018-08-01 23:11     ` Ming Lei
2018-07-31 10:49 ` [PATCH 3/3] block: kill BLK_MQ_F_SG_MERGE Ming Lei
2018-07-31 15:32 ` [PATCH 0/3] block: fix mismatch of figuring out physical segment number Mike Snitzer
2018-08-06  2:37 ` Ming Lei [this message]

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='CACVXFVNhqmyL4cHJ--k+cOhqCA2vkaLGCXnxEzB3urhrC=AAzg@mail.gmail.com' \
    --to=tom.leiming@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kent.overstreet@gmail.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=snitzer@redhat.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 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.