From: John Garry <john.g.garry@oracle.com>
To: Keith Busch <kbusch@meta.com>,
axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org,
io-uring@vger.kernel.org
Cc: sagi@grimberg.me, asml.silence@gmail.com, anuj20.g@samsung.com,
joshi.k@samsung.com, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv13 10/11] nvme: register fdp parameters with the block layer
Date: Wed, 11 Dec 2024 09:30:37 +0000 [thread overview]
Message-ID: <a8964dab-8075-4417-bcf3-87c67fe758c0@oracle.com> (raw)
In-Reply-To: <20241210194722.1905732-11-kbusch@meta.com>
On 10/12/2024 19:47, Keith Busch wrote:
>
> +static int nvme_query_fdp_granularity(struct nvme_ctrl *ctrl,
> + struct nvme_ns_info *info, u8 fdp_idx)
> +{
> + struct nvme_fdp_config_log hdr, *h;
> + struct nvme_fdp_config_desc *desc;
> + size_t size = sizeof(hdr);
> + int i, n, ret;
> + void *log;
> +
> + ret = nvme_get_log_lsi(ctrl, 0, NVME_LOG_FDP_CONFIGS, 0,
> + NVME_CSI_NVM, &hdr, size, 0, info->endgid);
> + if (ret) {
> + dev_warn(ctrl->device,
> + "FDP configs log header status:0x%x endgid:%x\n", ret,
> + info->endgid);
About endgid, I guess that there is a good reason but sometimes "0x" is
prefixed for hex prints and sometimes not. Maybe no prefix is used when
we know that the variable is to hold a value from a HW register / memory
structure - I don't know.
further nitpicking: And ret holds a kernel error code - the driver seems
inconsistent for printing this. Sometimes it's %d and sometimes 0x%x.
> + return ret;
> + }
> +
> + size = le32_to_cpu(hdr.sze);
> + h = kzalloc(size, GFP_KERNEL);
> + if (!h) {
> + dev_warn(ctrl->device,
> + "failed to allocate %lu bytes for FDP config log\n",
> + size);
do we normally print ENOMEM messages? I see that the bytes is printed,
but I assume that this is a sane value (of little note).
> + return -ENOMEM;
> + }
> +
> + ret = nvme_get_log_lsi(ctrl, 0, NVME_LOG_FDP_CONFIGS, 0,
> + NVME_CSI_NVM, h, size, 0, info->endgid);
> + if (ret) {
> + dev_warn(ctrl->device,
> + "FDP configs log status:0x%x endgid:%x\n", ret,
> + info->endgid);
> + goto out;
> + }
> +
> + n = le16_to_cpu(h->numfdpc) + 1;
> + if (fdp_idx > n) {
> + dev_warn(ctrl->device, "FDP index:%d out of range:%d\n",
> + fdp_idx, n);
> + /* Proceed without registering FDP streams */> + ret = 0;
nit: maybe you want to be explicit, but logically ret is already 0
> + goto out;
> + }
> +
> + log = h + 1;
> + desc = log;
> + for (i = 0; i < fdp_idx; i++) {
> + log += le16_to_cpu(desc->dsze);
> + desc = log;
> + }
> +
> + if (le32_to_cpu(desc->nrg) > 1) {
> + dev_warn(ctrl->device, "FDP NRG > 1 not supported\n");
> + ret = 0;
Same here
> + goto out;
> + }
> +
> + info->runs = le64_to_cpu(desc->runs);
> +out:
> + kfree(h);
> + return ret;
> +}
next prev parent reply other threads:[~2024-12-11 9:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 19:47 [PATCHv13 00/11] block write streams with nvme fdp Keith Busch
2024-12-10 19:47 ` [PATCHv13 01/11] fs: add a write stream field to the kiocb Keith Busch
2024-12-10 19:47 ` [PATCHv13 02/11] block: add a bi_write_stream field Keith Busch
2024-12-10 19:47 ` [PATCHv13 03/11] block: introduce max_write_streams queue limit Keith Busch
2024-12-10 19:47 ` [PATCHv13 04/11] block: introduce a write_stream_granularity " Keith Busch
2024-12-11 8:46 ` John Garry
2024-12-10 19:47 ` [PATCHv13 05/11] block: expose write streams for block device nodes Keith Busch
2024-12-11 5:53 ` Nitesh Shetty
2024-12-10 19:47 ` [PATCHv13 06/11] io_uring: enable per-io write streams Keith Busch
2024-12-11 6:44 ` Nitesh Shetty
2024-12-10 19:47 ` [PATCHv13 07/11] nvme: add a nvme_get_log_lsi helper Keith Busch
2024-12-10 19:47 ` [PATCHv13 08/11] nvme: pass a void pointer to nvme_get/set_features for the result Keith Busch
2024-12-10 19:47 ` [PATCHv13 09/11] nvme: add FDP definitions Keith Busch
2024-12-10 19:47 ` [PATCHv13 10/11] nvme: register fdp parameters with the block layer Keith Busch
2024-12-11 6:41 ` Nitesh Shetty
2024-12-11 9:30 ` John Garry [this message]
2024-12-11 15:55 ` Keith Busch
2024-12-11 11:23 ` Hannes Reinecke
2024-12-11 14:40 ` kernel test robot
2024-12-11 17:18 ` kernel test robot
2024-12-10 19:47 ` [PATCHv13 11/11] nvme: use fdp streams if write stream is provided Keith Busch
2024-12-11 7:13 ` [PATCHv13 00/11] block write streams with nvme fdp Christoph Hellwig
2024-12-12 5:51 ` Kanchan Joshi
2024-12-12 6:05 ` 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=a8964dab-8075-4417-bcf3-87c67fe758c0@oracle.com \
--to=john.g.garry@oracle.com \
--cc=anuj20.g@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@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