From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH rfc 1/2] nvme: support smart read-only critical warning event
Date: Wed, 6 Dec 2017 23:47:46 +0100 [thread overview]
Message-ID: <20171206224746.GC14274@lst.de> (raw)
In-Reply-To: <0c6a853d-c8c5-2144-09e1-8e6cae90fb2a@grimberg.me>
On Tue, Dec 05, 2017@09:28:53AM +0200, Sagi Grimberg wrote:
> 2. handle the event in the kernel, issue the log page with retain bit on
> and only then notify userspace.
The retain bit is a new optional feature in nvme 1.3. I fear we
won't see all that many controllers respecting it.
next prev parent reply other threads:[~2017-12-06 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 9:24 [PATCH rfc 0/2] Support read-only subsystem critical warning Sagi Grimberg
2017-12-04 9:24 ` [PATCH rfc 1/2] nvme: support smart read-only critical warning event Sagi Grimberg
2017-12-04 20:07 ` Christoph Hellwig
2017-12-05 7:28 ` Sagi Grimberg
2017-12-05 7:57 ` Johannes Thumshirn
2017-12-06 22:47 ` Christoph Hellwig [this message]
2017-12-07 6:45 ` Sagi Grimberg
2017-12-04 9:24 ` [PATCH rfc 2/2] nvmet: expose option to emulate a nvm subsystem in read-only mode Sagi Grimberg
2017-12-04 16:19 ` Christoph Hellwig
2017-12-04 18:11 ` Sagi Grimberg
2017-12-04 20:06 ` Christoph Hellwig
2017-12-05 7:22 ` Sagi Grimberg
2017-12-06 22:46 ` Christoph Hellwig
2017-12-07 6:41 ` 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=20171206224746.GC14274@lst.de \
--to=hch@lst.de \
/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