All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "snitzer@redhat.com" <snitzer@redhat.com>
Cc: "dm-devel@redhat.com" <dm-devel@redhat.com>
Subject: Re: Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks"
Date: Wed, 14 Mar 2018 16:34:03 +0000	[thread overview]
Message-ID: <1521045242.3006.4.camel@wdc.com> (raw)
In-Reply-To: <20180313214156.GA4325@redhat.com>

On Tue, 2018-03-13 at 17:41 -0400, Mike Snitzer wrote:
> On Tue, Mar 13 2018 at  1:10pm -0400,
> Bart Van Assche <Bart.VanAssche@wdc.com> wrote:
> > Even if that would be the case, that can't have been the cause of what I
> > reported. Before I run any dm tests I merge the block layer, SCSI and RDMA
> > changes that are scheduled for the next kernel version into the dm tree.
> 
> Well I've rebased dm-4.16 ontop of v4.15-rc5.  If you udate to latest
> dm-4.16 and look at the following diff it is pretty clear that these
> changes will not compromise dm-mpath's "mq" mode (which you're using):
> 
> git diff 8d47e65948ddea4398892946d9e50778a316b397^..e8f74a0f00113d74ac18d6de13096f9e2f95618a -- drivers/md/dm-mpath.c
> 
> I see no reason why you'd hit hangs with requests lingering on the requeue_list

Hello Mike,

I agree with you that the hanging requests shouldn't be related to the most recent
dm changes. I will try to find some time to root-cause this myself.

Bart.

  reply	other threads:[~2018-03-14 16:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 20:28 [PATCH] Revert "dm mpath: remove unnecessary NVMe branching in favor of scsi_dh checks" Bart Van Assche
2018-03-12 21:23 ` Mike Snitzer
2018-03-12 21:32   ` Bart Van Assche
2018-03-13  1:23     ` Mike Snitzer
2018-03-13 16:43       ` Bart Van Assche
2018-03-13 17:02         ` Mike Snitzer
2018-03-13 17:07           ` Mike Snitzer
2018-03-13 17:10             ` Bart Van Assche
2018-03-13 21:41               ` Mike Snitzer
2018-03-14 16:34                 ` Bart Van Assche [this message]
2018-03-13 15:25     ` Mike Snitzer
2018-03-13 16:31       ` Mike Snitzer
2018-03-13 16:46         ` Bart Van Assche
2018-03-13 16:58           ` Mike Snitzer
2018-03-30 17:04         ` Bart Van Assche
2018-03-13 16:38       ` Bart Van Assche

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=1521045242.3006.4.camel@wdc.com \
    --to=bart.vanassche@wdc.com \
    --cc=dm-devel@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.