From: Christoph Hellwig <hch@lst.de>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/7] nvme: update nvme_id_ns OPTPERF constants
Date: Tue, 24 Feb 2026 15:30:40 +0100 [thread overview]
Message-ID: <20260224143040.GB11710@lst.de> (raw)
In-Reply-To: <20260221033302.1451669-4-csander@purestorage.com>
> In NVMe verson 2.0 and below, OPTPERF comprises only bit 4 of NSFEAT in
> the Identify Namespace structure. Since version 2.1, OPTPERF includes
> both bits 4 and 5 of NSFEAT. Replace the NVME_NS_FEAT_IO_OPT constant
> with NVME_NS_FEAT_OPTPERF_SHIFT, NVME_NS_FEAT_OPTPERF_MASK, and
> NVME_NS_FEAT_OPTPERF_MASK_2_1, representing the first bit, pre-2.1 bit
> width, and post-2.1 bit width of OPTPERF.
Please add this in a comment in the code.
next prev parent reply other threads:[~2026-02-24 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 3:32 [PATCH v2 0/7] nvme: set discard_granularity from NPDG/NPDA Caleb Sander Mateos
2026-02-21 3:32 ` [PATCH v2 1/7] nvme: add preferred I/O size fields to struct nvme_id_ns_nvm Caleb Sander Mateos
2026-02-21 3:32 ` [PATCH v2 2/7] nvme: fold nvme_config_discard() into nvme_update_disk_info() Caleb Sander Mateos
2026-02-24 14:29 ` Christoph Hellwig
2026-02-21 3:32 ` [PATCH v2 3/7] nvme: update nvme_id_ns OPTPERF constants Caleb Sander Mateos
2026-02-24 14:30 ` Christoph Hellwig [this message]
2026-02-21 3:32 ` [PATCH v2 4/7] nvme: always issue I/O Command Set specific Identify Namespace Caleb Sander Mateos
2026-02-21 3:33 ` [PATCH v2 5/7] nvme: set discard_granularity from NPDG/NPDA Caleb Sander Mateos
2026-02-24 14:33 ` Christoph Hellwig
2026-02-24 15:15 ` Keith Busch
2026-02-24 16:05 ` Caleb Sander Mateos
2026-02-21 3:33 ` [PATCH v2 6/7] nvmet: use NVME_NS_FEAT_OPTPERF_SHIFT Caleb Sander Mateos
2026-02-21 3:33 ` [PATCH v2 7/7] nvmet: report NPDGL and NPDAL Caleb Sander Mateos
2026-02-24 14:34 ` Christoph Hellwig
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=20260224143040.GB11710@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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