From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH rfc 1/2] nvme: support smart read-only critical warning event
Date: Tue, 05 Dec 2017 08:57:31 +0100 [thread overview]
Message-ID: <mqda7yxehec.fsf@linux-x5ow.site> (raw)
In-Reply-To: <0c6a853d-c8c5-2144-09e1-8e6cae90fb2a@grimberg.me> (Sagi Grimberg's message of "Tue, 5 Dec 2017 09:28:53 +0200")
Sagi Grimberg <sagi at grimberg.me> writes:
> 2. handle the event in the kernel, issue the log page with retain bit on
> and only then notify userspace.
>
> I personally prefer (2), what do others think?
Sorry for chiming in so late, but I agree with Sagi.
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2017-12-05 7:57 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 [this message]
2017-12-06 22:47 ` Christoph Hellwig
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=mqda7yxehec.fsf@linux-x5ow.site \
--to=jthumshirn@suse.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