From: anish.jhaveri@paviliondata.com
To: Hannes Reinecke <hare@suse.de>
Cc: sagi@grimberg.me, hch@lst.de, axboe@kernel.dk,
keith.busch@intel.com, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 00/10] nvme multipath support on top of nvme-4.13 branch
Date: Mon, 18 Sep 2017 21:40:10 -0700 [thread overview]
Message-ID: <20170919044010.l2ja4k23xk6gipkl@haynes> (raw)
In-Reply-To: <a4e8f78f-34a7-5ba5-424a-0aaba62bc597@suse.de>
On Wed, Sep 13, 2017 at 08:57:13AM +0200, Hannes Reinecke wrote:
> In general I am _not_ in favour of this approach.
>
> This is essentially the same level of multipath support we had in the
> old qlogic and lpfc drivers in 2.4/2.6 series, and it took us _years_ to
> get rid of this.
> Main objection here is that it will be really hard (if not impossible)
> to use the same approach for other subsystems (eg SCSI), so we'll end up
> having different multipath implementations depending on which subsystem
> is being used.
> Which really is a maintenance nightmare.
>
> I'm not averse to having other multipath implementations in the kernel,
> but it really should be abstracted so that other subsystems can _try_ to
> leverage it.
Got it. Thanks!
next prev parent reply other threads:[~2017-09-19 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 4:20 [PATCH 00/10] nvme multipath support on top of nvme-4.13 branch Anish M Jhaveri
2017-09-13 6:57 ` Hannes Reinecke
2017-09-19 4:40 ` anish.jhaveri [this message]
2017-09-15 18:07 ` Christoph Hellwig
2017-09-19 5:10 ` Anish Jhaveri
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=20170919044010.l2ja4k23xk6gipkl@haynes \
--to=anish.jhaveri@paviliondata.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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