Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [PATCH 1/2] block: Implement support for write zeros
Date: Tue, 07 Oct 2014 10:54:39 -0400	[thread overview]
Message-ID: <yq14mvgexqo.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20141007142127.GA5393@wil.cx> (Matthew Wilcox's message of "Tue,  7 Oct 2014 10:21:27 -0400")

>>>>> "Matthew" == Matthew Wilcox <willy at linux.intel.com> writes:

Matthew> Jens, did you want to ACK/NACK this one?  It seems resaonable
Matthew> to me.

But since that WRITE ZEROES fell in T10/T13 it would be an NVMe-specific
command (and it is already a subset of the existing WRITE SAME).

Since I'm redoing the zeroout/discard stuff for 3.19 anyway I'd rather
we wait and I can work with Keith on this.

-- 
Martin K. Petersen	Oracle Linux Engineering

      reply	other threads:[~2014-10-07 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 17:42 [PATCH 1/2] block: Implement support for write zeros Keith Busch
2014-07-08 17:42 ` [PATCH 2/2] NVMe: Implement WRITE_ZEROS support Keith Busch
2014-10-07 14:21 ` [PATCH 1/2] block: Implement support for write zeros Matthew Wilcox
2014-10-07 14:54   ` Martin K. Petersen [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=yq14mvgexqo.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.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