Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: wyung@micron.com (Winson Yung (wyung))
Subject: [PATCH] NVMe: Add support to receive NVMe asynchronous events
Date: Wed, 28 May 2014 13:35:28 -0700	[thread overview]
Message-ID: <53864890.5070609@micron.com> (raw)
In-Reply-To: <alpine.LRH.2.03.1405261834070.4700@AMR>

I had a look of the patch, it looks it does what I was trying to enable, 
except it misses the portion that enables it by calling set feature cmd. 
Is it something we can consider now? Also, for these critical warnings 
that exposed by the async events, can we also put them in the kernel log 
as well when they enabled?

/Winson

On 5/26/2014 5:56 PM, Keith Busch wrote:
> On Mon, 26 May 2014, Matthew Wilcox wrote:
>> You should probably take a look at Keith's work last year to allow userspace
>> to send async event requests:
>>
>> http://lists.infradead.org/pipermail/linux-nvme/2013-August/000350.html
>
> Yeah, that proposal just lets userspace consume the results of an async
> request from a FIFO read through the character device. The driver still
> has to do the sending since there's no mechanism for requests from user
> space with infinite timeout.
>
> I've no idea if the proposed method for consuming results of this kind
> of information was typical. I assumed it wasn't since it didn't get much
> traction. :)
>

  parent reply	other threads:[~2014-05-28 20:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 20:04 [PATCH] NVMe: Add support to receive NVMe asynchronous events Winson Yung (wyung)
2014-05-26 21:42 ` Keith Busch
2014-05-27  5:02   ` Winson Yung (wyung)
2014-05-26 23:51 ` Matthew Wilcox
2014-05-27  0:56   ` Keith Busch
2014-05-27  5:35     ` Winson Yung (wyung)
2014-05-27  5:50       ` Keith Busch
2014-05-27  6:56         ` Robles, Raymond C
2014-05-28 20:35     ` Winson Yung (wyung) [this message]
2014-05-29  6:40       ` Keith Busch
2014-05-27  5:15   ` Winson Yung (wyung)

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=53864890.5070609@micron.com \
    --to=wyung@micron.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