All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Bart Van Assche <bart.vanassche@wdc.com>
Cc: Omar Sandoval <osandov@fb.com>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH blktests 3/3] Add NVMeOF dm-mpath tests
Date: Fri, 17 Aug 2018 10:24:28 -0400	[thread overview]
Message-ID: <20180817142428.GA3413@redhat.com> (raw)
In-Reply-To: <20180815203728.19521-4-bart.vanassche@wdc.com>

On Wed, Aug 15 2018 at  4:37pm -0400,
Bart Van Assche <bart.vanassche@wdc.com> wrote:

> Add a series of tests for the NVMeOF drivers on top of the dm-mpath
> driver. These tests are similar to the tests under tests/srp. Both
> tests use the dm-mpath driver for multipath and the loopback
> functionality of the rdma_rxe driver. The only difference is that the
> nvmeof-mp tests use the NVMeOF initiator and target drivers instead
> of the SRP initiator and target drivers.
> 
> Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com>

I like the prospect of keeping NVMe honest by testing it with DM
multipath.

But will you grow dependent on ANA in the future?  If so then you're out
of luck given the way the NVMe driver's ANA support was maliciously
added without care for making it work without the NVMe driver's native
multipath support.

Seems very few people care about making NVMe multipath _not_ so tightly
coupled to native NVMe multipath.  And sadly I don't have time to work
on untangling the "all-in" nature of NVMe ANA and native NVMe
multipath.

Put differently: until Jens stops taking hch's pull requests despite
concerns being raised against hch's approach (that hch completely
ignores because he rules with an iron fist from the top of a mountain in
the Alps) we're pretty much screwed.

Mike

       reply	other threads:[~2018-08-17 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180815203728.19521-1-bart.vanassche@wdc.com>
     [not found] ` <20180815203728.19521-4-bart.vanassche@wdc.com>
2018-08-17 14:24   ` Mike Snitzer [this message]
2018-08-17 15:46     ` [PATCH blktests 3/3] Add NVMeOF dm-mpath tests Bart Van Assche
2018-08-17 16:04       ` Mike Snitzer
     [not found] ` <20180820073059.quvg3bh4ngv5ka4x@linux-x5ow.site>
     [not found]   ` <ee851ae7b88a93b9b5c9f1b0c6e206944c0b3c64.camel@wdc.com>
     [not found]     ` <20180821064619.7tyhlst74qkrw4fi@linux-x5ow.site>
2018-08-23  1:53       ` [PATCH blktests 0/3] Add NVMeOF multipath tests Bart Van Assche
2018-08-24  0:21         ` Omar Sandoval
2018-09-13  1:06           ` Omar Sandoval
2018-09-16  4:28             ` Bart Van Assche
2018-09-18 21:20           ` Bart Van Assche
2018-09-18 23:24             ` Omar Sandoval
2018-09-19  0:02               ` Bart Van Assche
2018-09-19  0:18                 ` Omar Sandoval
2018-09-27 23:26                   ` Bart Van Assche
2018-10-05 18:50                     ` Omar Sandoval

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=20180817142428.GA3413@redhat.com \
    --to=snitzer@redhat.com \
    --cc=bart.vanassche@wdc.com \
    --cc=jthumshirn@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.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.