All of lore.kernel.org
 help / color / mirror / Atom feed
From: willy@linux.intel.com (Matthew Wilcox)
Subject: [PATCH] NVMe: Fail SCSI->NVMe translation for UNMAP when anchor is set
Date: Wed, 18 Jun 2014 12:25:47 -0400	[thread overview]
Message-ID: <20140618162547.GJ12025@linux.intel.com> (raw)
In-Reply-To: <B8DB29EA17EB2742AC3405C31A9B9EE9614C0D68@ORSMSX111.amr.corp.intel.com>

On Wed, Jun 18, 2014@03:51:52PM +0000, Mayes, Barrett N wrote:
> > On the one hand, it says that ANC_SUP shall be set to 0.  
> 
> LSI proposed the following and asked for feedback by June 9.  I don't recall seeing any comments to this on the public reflector.
> 
> ANC_SUC
> Shall be set to 0, to indicate that setting the ANCHOR bit in UNMAP is not supported if the namespace is not resource or thin provisioned.
> Shall be set to 1, to indicate that setting the ANCHOR bit in UNMAP is supported if the namespace is resource provisioned. May be set to 1 if the namespace is thin provisioned.

Thanks!  Just found that unread email ;-)

I'm not sure about Guy's reasoning that NVMe supports three different
provisioning models like SCSI does.  Should probably take this to the
NVMe mailing list now ...

  parent reply	other threads:[~2014-06-18 16:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18  9:03 [PATCH] NVMe: Fail SCSI->NVMe translation for UNMAP when anchor is set Dan McLeran
2014-06-18 15:13 ` Keith Busch
2014-06-18 15:15   ` Dan McLeran
2014-06-18 15:27   ` Matthew Wilcox
2014-06-18 15:30     ` Dan McLeran
2014-06-18 15:45       ` Matthew Wilcox
2014-06-18 15:51         ` Mayes, Barrett N
2014-06-18 16:04           ` Keith Busch
2014-06-18 16:25           ` Matthew Wilcox [this message]
2014-06-18 17:23             ` Mayes, Barrett N
2014-06-18 15:35     ` 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=20140618162547.GJ12025@linux.intel.com \
    --to=willy@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.