All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Mike Snitzer <snitzer@redhat.com>, Hannes Reinecke <hare@suse.de>,
	Jens Axboe <axboe@fb.com>,
	linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Ewan Milne <emilne@redhat.com>, Jeff Moyer <jmoyer@redhat.com>
Subject: Re: block: Always check queue limits for cloned requests
Date: Mon, 30 Nov 2015 08:12:51 +0100	[thread overview]
Message-ID: <20151130071251.GA315@x4> (raw)
In-Reply-To: <20151130141141.6ce3fadb@tom-T450>

On 2015.11.30 at 14:11 +0800, Ming Lei wrote:
> On Sun, 29 Nov 2015 18:05:06 +0100
> Markus Trippelsdorf <markus@trippelsdorf.de> wrote:
> > 
> > No, I'm not using DM multipath. 
> 
> 
> OK, I guess it is still one block merge issue, care to test the
> following patch?
> 
> The patch can address one issue when bio->bi_seg_front_size
> is set as too small mistakenly, then fewer physical segment may
> be figured out.

Many thanks. Your patch fixes the issue for me.

-- 
Markus

  reply	other threads:[~2015-11-30  7:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26  7:46 [PATCH] block: Always check queue limits for cloned requests Hannes Reinecke
2015-11-26 13:11 ` Mike Snitzer
2015-11-29 11:49   ` Markus Trippelsdorf
2015-11-29 15:43     ` Hannes Reinecke
2015-11-29 16:15       ` Markus Trippelsdorf
2015-11-29 16:49         ` Mike Snitzer
2015-11-29 17:05           ` Markus Trippelsdorf
2015-11-30  6:11             ` Ming Lei
2015-11-30  7:12               ` Markus Trippelsdorf [this message]
2015-11-30  6:47             ` Hannes Reinecke

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=20151130071251.GA315@x4 \
    --to=markus@trippelsdorf.de \
    --cc=axboe@fb.com \
    --cc=emilne@redhat.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=snitzer@redhat.com \
    --cc=tom.leiming@gmail.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.