From: Jens Axboe <axboe@kernel.dk>
To: Xiaobing Li <xiaobing.li@samsung.com>, asml.silence@gmail.com
Cc: linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
kun.dou@samsung.com, peiwei.li@samsung.com, joshi.k@samsung.com,
kundan.kumar@samsung.com, wenwen.chen@samsung.com,
ruyi.zhang@samsung.com
Subject: Re: [PATCH v2] io_uring: Statistics of the true utilization of sq threads.
Date: Wed, 8 Nov 2023 08:26:04 -0700 [thread overview]
Message-ID: <60464608-a9b7-4cf8-bd6d-c982210c6f83@kernel.dk> (raw)
In-Reply-To: <20231108080732.15587-1-xiaobing.li@samsung.com>
On 11/8/23 1:07 AM, Xiaobing Li wrote:
> Since the sq thread has a while(1) structure, during this process, there
> may be a lot of time that is not processing IO but does not exceed the
> timeout period, therefore, the sqpoll thread will keep running and will
> keep occupying the CPU. Obviously, the CPU is wasted at this time;Our
> goal is to count the part of the time that the sqpoll thread actually
> processes IO, so as to reflect the part of the CPU it uses to process
> IO, which can be used to help improve the actual utilization of the CPU
> in the future.
There should be an explanation in here on what 'work' and 'total' mean.
> The test results are as follows:
> cat /proc/11440/fdinfo/6
> pos: 0
> flags: 02000002
> mnt_id: 16
> ino: 94449
> SqMask: 0xf
> SqHead: 1845170
> SqTail: 1845170
> CachedSqHead: 1845170
> CqMask: 0xf
> CqHead: 1845154
> CqTail: 1845154
> CachedCqTail: 1845154
> SQEs: 0
> CQEs: 0
> SqThread: -1
> SqThreadCpu: -1
> UserFiles: 1
> UserBufs: 0
> PollList:
> CqOverflowList:
> PID: 11440
> work: 18794
> total: 19123
These should go with the other Sq thread related ones, eg be SqWork and
SqTotal. It's counted in jiffies right now which is a bit odd in terms
of being exposed, as you'd need to know what the base of that unit is.
But probably not much of a concern, as work/total is really the metric
you care about. Maybe it'd be better to expose it as a percentage, and
get rid of total? Eg just have SqBusy: xx% be the output.
> diff --git a/io_uring/fdinfo.c b/io_uring/fdinfo.c
> index f04a43044d91..f0b79c533062 100644
> --- a/io_uring/fdinfo.c
> +++ b/io_uring/fdinfo.c
> @@ -213,6 +213,12 @@ __cold void io_uring_show_fdinfo(struct seq_file *m, struct file *f)
>
> }
>
> + if (ctx->sq_data) {
> + seq_printf(m, "PID:\t%d\n", task_pid_nr(ctx->sq_data->thread));
> + seq_printf(m, "work:\t%lu\n", ctx->sq_data->work);
> + seq_printf(m, "total:\t%lu\n", ctx->sq_data->total);
> + }
> +
This doesn't work, it needs proper locking. See how we get the other sq
values.
--
Jens Axboe
next prev parent reply other threads:[~2023-11-08 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231108081516epcas5p442a11004e3b4e6339972fd6da4c6692b@epcas5p4.samsung.com>
2023-11-08 8:07 ` [PATCH v2] io_uring: Statistics of the true utilization of sq threads Xiaobing Li
2023-11-08 15:26 ` Jens Axboe [this message]
2023-11-13 3:10 ` Xiaobing Li
2023-11-13 16:38 ` Jens Axboe
2023-11-08 16:23 ` Gabriel Krisman Bertazi
2023-11-09 16:14 ` Pavel Begunkov
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=60464608-a9b7-4cf8-bd6d-c982210c6f83@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=kun.dou@samsung.com \
--cc=kundan.kumar@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peiwei.li@samsung.com \
--cc=ruyi.zhang@samsung.com \
--cc=wenwen.chen@samsung.com \
--cc=xiaobing.li@samsung.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