From: snitzer@redhat.com (Mike Snitzer)
Subject: [PATCH 5/9] nvme: add ANA support
Date: Mon, 4 Jun 2018 08:31:35 -0400 [thread overview]
Message-ID: <20180604123134.GA6547@redhat.com> (raw)
In-Reply-To: <20180604115103.0c116078@pentland.suse.de>
On Mon, Jun 04 2018 at 5:51P -0400,
Hannes Reinecke <hare@suse.de> wrote:
> On Mon, 4 Jun 2018 09:03:57 +0200
> Christoph Hellwig <hch@lst.de> wrote:
>
> > On Mon, Jun 04, 2018@08:36:58AM +0200, Hannes Reinecke wrote:
> > > This suffers from the 'nvme connect' stall if the first detected
> > > namespace is inaccessible.
> >
> > Yes. This isn't really different from any other NVMe target that
> > constantly returns errors when you connect.
> >
> > If we want to do this properly we need some block level (e.g. gendisk)
> > state that a given device is ready for I/O. And then don't scan
> > partition tables if it isn't, and instead do the scan once it becomes
> > life. In other words: this is something that should be handled
> > mostly at the block level.
>
> Okay; that was one option I figured out, but didn't want to mess with
> gendisk unless explicitly requested.
> I'll be looking into it.
Pretty sure this will bring about potentially trying discussion with
udev folks. The same kinds of requirements have been around in lvm for
a while (and by lvm I mean it brokers udev readiness while it is
activating particular dm targets whose sub devices shouldn't be scanned
yet or at all).
Mike
next prev parent reply other threads:[~2018-06-04 12:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 7:11 draft ANA support v2 Christoph Hellwig
2018-06-01 7:11 ` [PATCH 1/9] nvme: don't hold nvmf_transports_rwsem for more than transport lookups Christoph Hellwig
2018-06-03 12:26 ` Sagi Grimberg
2018-06-04 6:30 ` Hannes Reinecke
2018-06-01 7:11 ` [PATCH 2/9] nvme.h: add ANA definitions Christoph Hellwig
2018-06-03 12:27 ` Sagi Grimberg
2018-06-04 6:30 ` Hannes Reinecke
2018-06-04 11:58 ` Johannes Thumshirn
2018-06-01 7:11 ` [PATCH 3/9] nvme: add support for the log specific field Christoph Hellwig
2018-06-03 12:27 ` Sagi Grimberg
2018-06-04 6:31 ` Hannes Reinecke
2018-06-04 11:59 ` Johannes Thumshirn
2018-06-01 7:11 ` [PATCH 4/9] nvme: always failover on path or transport errors Christoph Hellwig
2018-06-01 15:27 ` Mike Snitzer
2018-06-04 6:29 ` Christoph Hellwig
2018-06-04 12:01 ` Johannes Thumshirn
2018-06-04 12:23 ` Mike Snitzer
2018-06-03 12:28 ` Sagi Grimberg
2018-06-04 6:32 ` Hannes Reinecke
2018-06-01 7:11 ` [PATCH 5/9] nvme: add ANA support Christoph Hellwig
2018-06-04 6:36 ` Hannes Reinecke
2018-06-04 7:03 ` Christoph Hellwig
2018-06-04 9:51 ` Hannes Reinecke
2018-06-04 12:31 ` Mike Snitzer [this message]
2018-06-04 13:37 ` Hannes Reinecke
2018-06-06 12:01 ` Popuri, Sriram
2018-06-06 12:13 ` Christoph Hellwig
2018-06-06 12:27 ` Popuri, Sriram
2018-06-06 12:50 ` Christoph Hellwig
2018-06-01 7:11 ` [PATCH 6/9] nvmet: track and limit the number of namespaces per subsystem Christoph Hellwig
2018-06-04 6:35 ` Hannes Reinecke
2018-06-04 12:04 ` Johannes Thumshirn
2018-06-01 7:11 ` [PATCH 7/9] nvmet: add minimal ANA support Christoph Hellwig
2018-06-04 6:41 ` Hannes Reinecke
2018-06-04 12:25 ` Johannes Thumshirn
2018-06-04 12:55 ` Christoph Hellwig
2018-06-01 7:11 ` [PATCH 8/9] nvmet: support configuring additional ANA groups Christoph Hellwig
2018-06-04 6:42 ` Hannes Reinecke
2018-06-04 6:53 ` Christoph Hellwig
2018-06-04 9:48 ` Hannes Reinecke
2018-06-01 7:11 ` [PATCH 9/9] nvmet: make ANATT configurable Christoph Hellwig
2018-06-04 10:21 ` Hannes Reinecke
2018-06-04 12:11 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2018-07-24 11:50 draft ANA support v5 Christoph Hellwig
2018-07-24 11:50 ` [PATCH 5/9] nvme: add ANA support Christoph Hellwig
2018-07-26 2:00 ` Martin K. Petersen
2018-07-26 11:34 ` Johannes Thumshirn
2018-07-26 15:34 draft ANA support v6 Christoph Hellwig
2018-07-26 15:35 ` [PATCH 5/9] nvme: add ANA support Christoph Hellwig
2018-07-26 17:20 ` Mike Snitzer
2018-07-27 13:20 ` Hannes Reinecke
2018-07-27 13:38 ` Mike Snitzer
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=20180604123134.GA6547@redhat.com \
--to=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 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.