From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [PATCH v2 3/3] nvme: Set physical block size and optimal I/O size according to NVMe 1.4
Date: Thu, 13 Jun 2019 19:57:59 -0400 [thread overview]
Message-ID: <yq1blz1rqbc.fsf@oracle.com> (raw)
In-Reply-To: <fcd3b41c-38b9-4865-05c0-2f96c9382ea5@acm.org> (Bart Van Assche's message of "Thu, 13 Jun 2019 10:57:18 -0700 (PDT)")
Bart,
> Namespace Atomic Write Unit Power Fail (NAWUPF): This field indicates
> the namespace specific size of the write operation guaranteed to be
> written atomically to the NVM during a power fail or error condition.
> A value of 0h indicates that the size for this namespace is the same
> size as that reported in the AWUPF field of the Identify Controller data
> structure. All other values specify a size in terms of logical blocks
> using the same encoding as the AWUPF field.
There's some ambiguity there. But I think you're right that the encoding
statement qualifies it. This means that there is no explicit way of
expressing a NAWUPF of 1 logical block but that is OK since it is
implied.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-06-13 23:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 21:06 [PATCH v2 0/3] NVMe 1.4 Identify Namespace Support Bart Van Assche
2019-06-10 21:06 ` [PATCH v2 1/3] nvme: Introduce NVMe 1.4 Identify Namespace fields in struct nvme_id_ns Bart Van Assche
2019-06-10 21:06 ` [PATCH v2 2/3] nvmet: Export NVMe namespace attributes Bart Van Assche
2019-06-14 4:42 ` Chaitanya Kulkarni
2019-06-14 15:31 ` Bart Van Assche
2019-06-14 17:18 ` Chaitanya Kulkarni
2019-06-14 17:43 ` Bart Van Assche
2019-06-14 17:53 ` Chaitanya Kulkarni
2019-06-14 23:56 ` Bart Van Assche
2019-06-10 21:06 ` [PATCH v2 3/3] nvme: Set physical block size and optimal I/O size according to NVMe 1.4 Bart Van Assche
2019-06-13 1:53 ` Martin K. Petersen
2019-06-13 17:57 ` Bart Van Assche
2019-06-13 23:57 ` 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=yq1blz1rqbc.fsf@oracle.com \
--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