From: Kanchan Joshi <joshi.k@samsung.com>
To: Milan Broz <gmazyland@gmail.com>,
linux-block <linux-block@vger.kernel.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@infradead.org>,
"dm-devel@lists.linux.dev" <dm-devel@lists.linux.dev>
Subject: Re: sysfs integrity fields use
Date: Wed, 26 Feb 2025 15:34:31 +0530 [thread overview]
Message-ID: <aa29b282-6e04-409d-bfe5-bf8e3ac3499d@samsung.com> (raw)
In-Reply-To: <ba3840dd-e3a7-4896-89c9-0f131bb46fa5@gmail.com>
On 2/25/2025 4:33 PM, Milan Broz wrote:
> Sure, it is formatted to 4k data + 64 bytes metadata profile:
>
> # nvme id-ns -H /dev/nvme0n1
> ...
>
> LBA Format 0 : Metadata Size: 0 bytes - Data Size: 512 bytes -
> Relative Performance: 0 Best
> LBA Format 1 : Metadata Size: 8 bytes - Data Size: 512 bytes -
> Relative Performance: 0 Best
> LBA Format 2 : Metadata Size: 0 bytes - Data Size: 4096 bytes -
> Relative Performance: 0 Best
> LBA Format 3 : Metadata Size: 64 bytes - Data Size: 4096 bytes -
> Relative Performance: 0 Best (in use)
>
> formatted with
> # nvme format --lbaf=3 --force /dev/nvme0n1
Since you're not passing "--pi=[1-3]", it takes 0 as default, which
means protection-info is off.
next prev parent reply other threads:[~2025-02-26 10:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250225092525epcas5p31dd0a19ffdfb39f3f2ce4acd1c6da7ee@epcas5p3.samsung.com>
2025-02-25 9:23 ` sysfs integrity fields use Milan Broz
2025-02-25 10:10 ` Kanchan Joshi
2025-02-25 10:44 ` Kanchan Joshi
2025-02-25 11:03 ` Milan Broz
2025-02-26 10:04 ` Kanchan Joshi [this message]
2025-02-25 15:38 ` Christoph Hellwig
2025-02-26 14:02 ` Milan Broz
2025-02-27 14:46 ` [PATCH] docs: sysfs-block: Clarify integrity sysfs attributes for non-PI metadata Milan Broz
2025-03-03 17:25 ` Martin K. Petersen
2025-03-03 18:52 ` Milan Broz
2025-03-06 2:28 ` Martin K. Petersen
2025-03-18 15:44 ` [PATCH] docs: sysfs-block: Clarify integrity sysfs attributes Milan Broz
2025-03-20 7:04 ` Christoph Hellwig
2025-03-20 11:44 ` Jens Axboe
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=aa29b282-6e04-409d-bfe5-bf8e3ac3499d@samsung.com \
--to=joshi.k@samsung.com \
--cc=dm-devel@lists.linux.dev \
--cc=gmazyland@gmail.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=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