Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme-cli: add support for directive command
Date: Fri, 11 Aug 2017 13:03:14 -0400	[thread overview]
Message-ID: <20170811170314.GB7233@localhost.localdomain> (raw)
In-Reply-To: <1502420051-12378-1-git-send-email-kwan.huen@samsung.com>

On Thu, Aug 10, 2017@07:54:09PM -0700, kwan.huen@samsung.com wrote:
> Directive is a feature introduced in NVMe v1.3 that allows host
> and NVM subsystem or controller information exchange, namely data
> lifetime hint for example. Information is transmitted using
> the Directive Send and Directive Receive commands.
> 
> This patch set allows control of the directive resources of a
> directive-enabled nvme device.

The patches themselves look great, but I didn't realize this was a
feature user-space should be accessing. Providing this could mess up
the streams the kernel believes are set up, right?

  parent reply	other threads:[~2017-08-11 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170811025053epcas2p1ec98081d04a0488a2c08836c909f368c@epcas2p1.samsung.com>
2017-08-11  2:54 ` [PATCH] nvme-cli: add support for directive command kwan.huen
2017-08-11  2:54   ` [PATCH 1/2] nvme-cli: add nvme directive command support kwan.huen
2017-08-11  2:54   ` [PATCH 2/2] nvme-cli: add documentation for directive commands kwan.huen
2017-08-11 17:03   ` Keith Busch [this message]
2017-08-16  2:10     ` [PATCH] nvme-cli: add support for directive command Kwan (Hingkwan) Huen
2017-08-17 21:04       ` Keith Busch

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=20170811170314.GB7233@localhost.localdomain \
    --to=keith.busch@intel.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