From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvmet: Add support for HOST_ID feature.
Date: Mon, 28 Aug 2017 07:36:29 -0700 [thread overview]
Message-ID: <20170828143629.GA24146@infradead.org> (raw)
In-Reply-To: <1503922057-1141-1-git-send-email-omri@excelero.com>
On Mon, Aug 28, 2017@03:07:37PM +0300, Omri Mann wrote:
> Add host_id feature to NVMeoF targets. This will be required in order to
> support reservations.
For Fabrics the host id is set in the connect command and Set Features
must return an error (see section 5.21.1.19.2 in NVMe 1.3). But the
Get Features is still useful.
prev parent reply other threads:[~2017-08-28 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 12:07 [PATCH] nvmet: Add support for HOST_ID feature Omri Mann
2017-08-28 13:43 ` Sagi Grimberg
2017-08-28 18:10 ` Verkamp, Daniel
2017-08-28 20:15 ` Sagi Grimberg
2017-08-29 8:32 ` Christoph Hellwig
2017-08-28 14:36 ` Christoph Hellwig [this message]
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=20170828143629.GA24146@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