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: Tue, 13 Mar 2018 17:10:59 +0000 [thread overview]
Message-ID: <1520961057.2638.22.camel@wdc.com> (raw)
In-Reply-To: <20180313170721.GA3262@redhat.com>
On Tue, 2018-03-13 at 13:07 -0400, Mike Snitzer wrote:
> Just a thought: Maybe dm-4.16 (rc4 based) is missing a blk-mq fix?
>
> Might be worth cherry-picking the 2 topmost commits from dm-4.16 into
> the linus-based (rc5) tree you reported the original issue against?
>
> (looking at jens' rc5 block pull request, it seems unlikely but...)
Hello Mike,
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.
Bart.
next prev parent reply other threads:[~2018-03-13 17:10 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 [this message]
2018-03-13 21:41 ` Mike Snitzer
2018-03-14 16:34 ` Bart Van Assche
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=1520961057.2638.22.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox