Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH V4 0/2] nvmet: implement flush all support
Date: Mon, 2 Jul 2018 14:16:41 +0200	[thread overview]
Message-ID: <20180702121641.GA630@lst.de> (raw)
In-Reply-To: <BYAPR04MB4502F79155D2D089E041CD1086430@BYAPR04MB4502.namprd04.prod.outlook.com>

On Mon, Jul 02, 2018@05:43:14AM +0000, Chaitanya Kulkarni wrote:
> Hi Christoph,
> 
> It allows NVMeOF host to just send one command and complete the flush per-ctrl
> basis as opposed to per-ns basis.

Yes, but why would you ever do that?  Even when we discussed the issue
in the working group no one could actually come up with a practical use
case.

      reply	other threads:[~2018-07-02 12:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-26 22:17 [PATCH V4 0/2] nvmet: implement flush all support Chaitanya Kulkarni
2018-06-26 22:17 ` [PATCH V4 1/2] nvmet: move struct work_struct out of union Chaitanya Kulkarni
2018-06-26 22:17 ` [PATCH V4 2/2] nvmet: add support for flush all Chaitanya Kulkarni
2018-06-27  8:04   ` Sagi Grimberg
2018-06-28 14:42 ` [PATCH V4 0/2] nvmet: implement flush all support Christoph Hellwig
2018-07-02  5:43   ` Chaitanya Kulkarni
2018-07-02 12:16     ` 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=20180702121641.GA630@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