From: hch@infradead.org (Christoph Hellwig)
Subject: Linux NVMe and ANA
Date: Thu, 31 May 2018 09:14:31 -0700 [thread overview]
Message-ID: <20180531161431.GC10203@infradead.org> (raw)
In-Reply-To: <155c2475e1741dd2b90e092d87ec0bf2@mail.gmail.com>
On Wed, May 30, 2018@04:33:24PM +0530, Anand Nataraja Sundaram wrote:
> Hi Christoph,
>
>
>
> Is there any plans in the Linux NVMe community to add support for
> Asynchronous Namespace (ANA) ? I see the latest NVMe spec is ratified for
> ANA.
Work is going on on exactly the mailing list you are writing this to.
>
> Its my understanding ANA implementation will be agnostic of NVMe transport
> layer (RoCE, FC, PCIe etc..). Kindly correct me if wrong.
Yes.
parent reply other threads:[~2018-05-31 16:14 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <155c2475e1741dd2b90e092d87ec0bf2@mail.gmail.com>]
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=20180531161431.GC10203@infradead.org \
--to=hch@infradead.org \
/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