From: krisman@linux.vnet.ibm.com (Gabriel Krisman Bertazi)
Subject: [PATCH 2/2] [RFC] nvme: enable asynchronous events notification by default
Date: Wed, 29 Jun 2016 01:17:35 -0300 [thread overview]
Message-ID: <87r3bgsk68.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160628151137.GA8607@localhost.localdomain> (Keith Busch's message of "Tue, 28 Jun 2016 11:11:39 -0400")
Keith Busch <keith.busch at intel.com> writes:
> On Fri, Jun 24, 2016@01:17:26AM -0700, Christoph Hellwig wrote:
>> Yes, I'm not too excited about handling the AERs in kernel space,
>> having a userspace daemon to listen for them would generally be more
>> useful.
>
> How do daemons typically want to be notified of an event like this? I'm
> thinking sysfs_notify or maybe a KOBJ_CHANGE uevent. I don't know, this
> is unfamiliar territory to me.
For IPR (IBM Hardware RAID SCSI controller) we use KOBJ_CHANGE events
for a very similar situation, in which the driver signals a userspace
daemon, which goes over a sysfs attribute to collect adapter data dumps.
I'm also working on another async notifications mechanism for IPR,
similar to what is supported by nvme, in which I plan to use the same
uevent interface for userspace notifications.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2016-06-29 4:17 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
2016-06-24 8:17 ` Christoph Hellwig
2016-06-28 15:11 ` Keith Busch
2016-06-29 4:17 ` Gabriel Krisman Bertazi [this message]
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=87r3bgsk68.fsf@linux.vnet.ibm.com \
--to=krisman@linux.vnet.ibm.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).