From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Johannes Thumshirn <jthumshirn@suse.de>,
Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@intel.com>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvme: make controller 'state' sysfs attribute pollable
Date: Mon, 25 Sep 2017 14:52:11 +0200 [thread overview]
Message-ID: <20170925125211.GD8130@lst.de> (raw)
In-Reply-To: <daf5fe87-6b93-68aa-65be-b442615b9bd0@suse.de>
On Mon, Sep 25, 2017 at 10:23:16AM +0200, Hannes Reinecke wrote:
> > We could have such an interface I assume. But it would suck to maintain
> > yet another state (we are already having enough trouble to have a
> > coherent controller state machine).
>
> Weell ... we could be using a notifier chain for that.
> I think I should post my patchset.
The point is: if you want proper multipath behavior use the nvme
in-kernel multipath code. If you want to weird crap in userspace don't
expect any help from the kernel driver.
next prev parent reply other threads:[~2017-09-25 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 10:40 [PATCH] nvme: make controller 'state' sysfs attribute pollable Johannes Thumshirn
2017-09-20 10:49 ` Sagi Grimberg
2017-09-20 14:59 ` Christoph Hellwig
2017-09-21 5:19 ` Johannes Thumshirn
2017-09-21 14:10 ` Christoph Hellwig
2017-09-25 5:37 ` Sagi Grimberg
2017-09-25 5:59 ` Hannes Reinecke
2017-09-25 7:09 ` Sagi Grimberg
2017-09-25 8:23 ` Hannes Reinecke
2017-09-25 12:52 ` Christoph Hellwig [this message]
2017-09-21 12:47 ` Guan Junxiong
2017-09-25 5:36 ` Sagi Grimberg
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=20170925125211.GD8130@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=jthumshirn@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).