From: kwan.huen@samsung.com (Kwan (Hingkwan) Huen)
Subject: [PATCH] nvme-cli: add support for directive command
Date: Wed, 16 Aug 2017 02:10:48 +0000 [thread overview]
Message-ID: <4f5e8a927f0d485b8a51a50224a4d64e@samsung.com> (raw)
In-Reply-To: <20170811170314.GB7233@localhost.localdomain>
> From: Keith Busch [mailto:keith.busch at intel.com]
> Sent: Friday, August 11, 2017 10:03 AM
> To: Kwan (Hingkwan) Huen <kwan.huen at samsung.com>
> Cc: linux-nvme at lists.infradead.org; axboe at kernel.dk; Changho Choi
> <changho.c at samsung.com>; Vijay Balakrishnan <vijay.bala at samsung.com>
> Subject: Re: [PATCH] nvme-cli: add support for directive command
>
> 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?
Hi Keith,
Sorry for late!
That's a valid concern. But the only thing I can see, which potentially cause
problem, is the stream directive enable/disable. With kernel enables and
manages the streams, if the tool can disable it, it'll cause IO error because the
device no longer takes stream write commands. I think we can disable this
directive enable/disable in this patch for now to avoid this problem, until
we have a better way to coordinate this with the driver.
Besides that, I think it is still valuable for the tool that allows users
to quickly check the directive functionalities and get status. In addition, the patch
also enables other features, e.g., users can allocate stream resources
dedicated to namespace.
Regards,
kwan
next prev parent reply other threads:[~2017-08-16 2:10 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 ` [PATCH] nvme-cli: add support for directive command Keith Busch
2017-08-16 2:10 ` Kwan (Hingkwan) Huen [this message]
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=4f5e8a927f0d485b8a51a50224a4d64e@samsung.com \
--to=kwan.huen@samsung.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