From: Klaus Jensen <its@irrelevant.dk>
To: Ankit Kumar <ankit.kumar@samsung.com>
Cc: kbusch@kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/3] docs: update hw/nvme documentation for protection information
Date: Tue, 8 Aug 2023 07:59:09 +0200 [thread overview]
Message-ID: <ZNHZrdFsSVa5DlOZ@cormorant.local> (raw)
In-Reply-To: <20230807212745.70151-4-ankit.kumar@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1501 bytes --]
On Aug 8 02:57, Ankit Kumar wrote:
> Add missing entry for pif ("protection information format").
> Protection information size can be 8 or 16 bytes, Update the pil entry
> as per the NVM command set specification.
>
> Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
> ---
> docs/system/devices/nvme.rst | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/docs/system/devices/nvme.rst b/docs/system/devices/nvme.rst
> index 2a3af268f7..30d46d9338 100644
> --- a/docs/system/devices/nvme.rst
> +++ b/docs/system/devices/nvme.rst
> @@ -271,9 +271,13 @@ The virtual namespace device supports DIF- and DIX-based protection information
>
> ``pil=UINT8`` (default: ``0``)
> Controls the location of the protection information within the metadata. Set
> - to ``1`` to transfer protection information as the first eight bytes of
> - metadata. Otherwise, the protection information is transferred as the last
> - eight bytes.
> + to ``1`` to transfer protection information as the first bytes of metadata.
> + Otherwise, the protection information is transferred as the last bytes of
> + metadata.
> +
> +``pif=UINT8`` (default: ``0``)
> + By default, the namespace device uses 16 bit guard protection information
> + format. Set to ``2`` to enable 64 bit guard protection information format.
>
I'll add a small note that pif=1 (32b guard) is not supported.
Thanks,
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-08-08 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230807160836epcas5p34398954fecd7388469012404b09b78f9@epcas5p3.samsung.com>
2023-08-07 21:27 ` [PATCH 0/3] hw/nvme: bug fixes and doc update Ankit Kumar
[not found] ` <CGME20230807160837epcas5p3b360bae29265c0851f13491952b40f38@epcas5p3.samsung.com>
2023-08-07 21:27 ` [PATCH 1/3] hw/nvme: fix CRC64 for guard tag Ankit Kumar
2023-08-08 5:58 ` Klaus Jensen
[not found] ` <CGME20230807160838epcas5p389c82acd77fd8c74fc7f83300b9d0aa9@epcas5p3.samsung.com>
2023-08-07 21:27 ` [PATCH 2/3] hw/nvme: fix disable pi checks for Type 3 protection Ankit Kumar
2023-08-08 5:57 ` Klaus Jensen
[not found] ` <CGME20230807160839epcas5p3fc18f1e23b454a6db48de18c822ac2d4@epcas5p3.samsung.com>
2023-08-07 21:27 ` [PATCH 3/3] docs: update hw/nvme documentation for protection information Ankit Kumar
2023-08-08 5:59 ` Klaus Jensen [this message]
2023-08-08 6:04 ` [PATCH 0/3] hw/nvme: bug fixes and doc update Michael Tokarev
2023-08-08 6:06 ` Klaus Jensen
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=ZNHZrdFsSVa5DlOZ@cormorant.local \
--to=its@irrelevant.dk \
--cc=ankit.kumar@samsung.com \
--cc=kbusch@kernel.org \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).