Linux Device Mapper development
 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: Tue, 13 Mar 2018 16:38:38 +0000	[thread overview]
Message-ID: <1520959117.2638.12.camel@wdc.com> (raw)
In-Reply-To: <20180313152551.GA2785@redhat.com>

On Tue, 2018-03-13 at 11:25 -0400, Mike Snitzer wrote:
> A pointer to the commit ids in question would be helpful so I can
> appreciate the details better.

Not sure whether this list is complete, but this is the most important one:

63cf1a902c9dd6b0761861ea87fce3663f59403b IB/srpt: Add RDMA/CM support

> Why is there need for a virtual machine?
> Just using extra isolation so as not to conflict with anything on the
> host?

Running these tests directly on the host is also fine. I wanted to explain
that no InfiniBand hardware is required.

Bart.

      parent reply	other threads:[~2018-03-13 16:38 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
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 [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=1520959117.2638.12.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