From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Keith Busch <kbusch@meta.com>, fio@vger.kernel.org, axboe@kernel.dk
Cc: its@irrelevant.dk, vincentfu@gmail.com,
Keith Busch <kbusch@kernel.org>,
Ankit Kumar <ankit.kumar@samsung.com>
Subject: Re: [PATCHv3] fio: add fdp support for io_uring_cmd nvme engine
Date: Fri, 24 Feb 2023 07:46:37 +0900 [thread overview]
Message-ID: <52dfb03e-66ef-0f37-1e18-a153ccc8ff9f@opensource.wdc.com> (raw)
In-Reply-To: <20230223185508.3527294-1-kbusch@meta.com>
On 2/24/23 03:55, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Add support for NVMe TP4146 Flexible Data Placemen, allowing placement
> identifiers in write commands. The user can enabled this with the new
> "fdp=1" parameter for fio's io_uring_cmd ioengine. By default, the fio
> jobs will cycle through all the namespace's available placement
> identifiers for write commands. The user can limit which placement
> identifiers can be used with additional parameter, "fdp_pli=<list,>",
> which can be used to separate write intensive jobs from less intensive
> ones.
>
> Setting up your namespace for FDP is outside the scope of 'fio', so this
> assumes the namespace is already properly configured for the mode.
>
> Based-on-a-patch-by: Ankit Kumar <ankit.kumar@samsung.com>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
[...]
> +static int fdp_ruh_info(struct thread_data *td, struct fio_file *f,
> + struct fio_ruhs_info *ruhs)
> +{
> + int ret = -EINVAL;
> +
> + if (td->io_ops && td->io_ops->fdp_fetch_ruhs)
> + ret = td->io_ops->fdp_fetch_ruhs(td, f, ruhs);
> + else
> + log_err("%s: engine (%s) lacks fetch ruhs.\n",
> + f->file_name, td->io_ops->name);
> + if (ret < 0) {
> + td_verror(td, errno, "fdp fetch ruhs failed");
> + log_err("%s: fdp fetch ruhs failed (%d).\n",
> + f->file_name, errno);
Nit: for the !td->io_ops->fdp_fetch_ruhs case, this error message will also be
displayed. You could reverse the earlier if and return earlier to avoid that and
make the error messages clearer. Not a big deal though :)
> + }
> +
> + return ret;
> +}
> +
> +static int init_ruh_info(struct thread_data *td, struct fio_file *f)
> +{
> + struct fio_ruhs_info *ruhs, *tmp;
> + int i, ret;
> +
> + ruhs = calloc(1, sizeof(*ruhs) + 128 * sizeof(*ruhs->plis));
> + if (!ruhs)
> + return -ENOMEM;
> +
> + ret = fdp_ruh_info(td, f, ruhs);
> + if (ret) {
> + log_info("fio: ruh info failed for %s (%d).\n",
> + f->file_name, -ret);
> + goto out;
> + }
> +
> + if (ruhs->nr_ruhs > 128)
> + ruhs->nr_ruhs = 128;
> +
> + if (td->o.fdp_nrpli == 0) {
> + f->ruhs_info = ruhs;
> + return 0;
> + }
> +
> + for (i = 0; i < td->o.fdp_nrpli; i++) {
> + if (td->o.fdp_plis[i] > ruhs->nr_ruhs) {
> + ret = -EINVAL;
> + goto out;
> + }
> + }
> +
> + tmp = calloc(1, sizeof(*tmp) + ruhs->nr_ruhs * sizeof(*tmp->plis));
Nit: since you checked the calloc above, you could check this one too.
> + tmp->nr_ruhs = td->o.fdp_nrpli;
> + for (i = 0; i < td->o.fdp_nrpli; i++)
> + tmp->plis[i] = ruhs->plis[td->o.fdp_plis[i]];
> + f->ruhs_info = tmp;
> +out:
> + free(ruhs);
> + return ret;
> +}
Apart from these 2 nits, looks OK to me.
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2023-02-23 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 18:55 [PATCHv3] fio: add fdp support for io_uring_cmd nvme engine Keith Busch
2023-02-23 22:46 ` Damien Le Moal [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=52dfb03e-66ef-0f37-1e18-a153ccc8ff9f@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=ankit.kumar@samsung.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=vincentfu@gmail.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;
as well as URLs for NNTP newsgroup(s).