From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 2/2] [RFC] nvme: enable asynchronous events notification by default
Date: Mon, 20 Jun 2016 16:21:35 -0400 [thread overview]
Message-ID: <20160620202135.GG12936@localhost.localdomain> (raw)
In-Reply-To: <576821E9.2060009@linux.vnet.ibm.com>
On Mon, Jun 20, 2016@02:03:37PM -0300, Guilherme G. Piccoli wrote:
> The goal of my patch is to do the 'job' of nvme-cli automatically from
> within the driver.
>
> One thing I was thinking is to add a sysfs parameter to be able to avoid the
> automatic enablement of async events in case we have a bogus adapter showing
> too many events, for example...not sure if this is necessary though, so I
> didn't add the parameter on this submission.
Instead of simply logging a message, is there something better we can do
to notify a user of an async event result? The event should be masked
by the controller until the appropriate log page is read, and I don't
think scanning the kernel logs is how such a program wants to find out
which page to read.
next prev parent reply other threads:[~2016-06-20 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 17:21 [PATCH 0/2] 2 patches about asynchronous events notification Guilherme G. Piccoli
2016-06-17 17:21 ` [PATCH 1/2] nvme: introduce asynchronous events textual output Guilherme G. Piccoli
2016-06-17 17:21 ` [PATCH 2/2] [RFC] nvme: enable asynchronous events notification by default Guilherme G. Piccoli
2016-06-20 6:55 ` Sagi Grimberg
2016-06-20 17:03 ` Guilherme G. Piccoli
2016-06-20 20:21 ` Keith Busch [this message]
2016-06-24 8:17 ` Christoph Hellwig
2016-06-28 15:11 ` Keith Busch
2016-06-29 4:17 ` Gabriel Krisman Bertazi
2016-07-06 22:47 ` Guilherme G. Piccoli
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=20160620202135.GG12936@localhost.localdomain \
--to=keith.busch@intel.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 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).