From: hch@lst.de (hch@lst.de)
Subject: [PATCH] nvme: do not block connect call on inaccessible devices
Date: Tue, 5 Jun 2018 14:50:36 +0200 [thread overview]
Message-ID: <20180605125036.GB13305@lst.de> (raw)
In-Reply-To: <3c752b110b15ae35dcf772cc350e729d54b2d52b.camel@wdc.com>
On Tue, Jun 05, 2018@12:35:13PM +0000, Bart Van Assche wrote:
> Is there a standard for AENs over NVMeOF? If so, how many receive buffers
> should the initiator reserve for AENs? Which credit mechanism should be used
> for AEN communication?
Take a look at sections 5.2 and 7.7 of NVMe 1.3. All that text
actually goes back to 1.0 without major change.
next prev parent reply other threads:[~2018-06-05 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 8:29 [PATCH] nvme: do not block connect call on inaccessible devices Hannes Reinecke
2018-06-05 11:17 ` Christoph Hellwig
2018-06-05 12:23 ` Hannes Reinecke
2018-06-05 12:35 ` Bart Van Assche
2018-06-05 12:50 ` hch [this message]
2018-06-05 12:51 ` Christoph Hellwig
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=20180605125036.GB13305@lst.de \
--to=hch@lst.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