From: Jens Axboe <[email protected]>
To: Ruyi Zhang <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCH] io_uring/fdinfo: add timeout_list to fdinfo
Date: Tue, 13 Aug 2024 06:06:08 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 8/11/24 8:00 PM, Ruyi Zhang wrote:
> io_uring fdinfo contains most of the runtime information,
> which is helpful for debugging io_uring applications;
> However, there is currently a lack of timeout-related
> information, and this patch adds timeout_list information.
Please wrap this at 72 chars, lines are too short right now.
> @@ -219,9 +221,19 @@ __cold void io_uring_show_fdinfo(struct seq_file *m, struct file *file)
>
> seq_printf(m, " user_data=%llu, res=%d, flags=%x\n",
> cqe->user_data, cqe->res, cqe->flags);
> -
> }
> -
> spin_unlock(&ctx->completion_lock);
Some unrelated whitespace changes here?
> +
> + seq_puts(m, "TimeoutList:\n");
> + spin_lock(&ctx->timeout_lock);
> + list_for_each_entry(timeout, &ctx->timeout_list, list) {
> + struct io_kiocb *req = cmd_to_io_kiocb(timeout);
> + struct io_timeout_data *data = req->async_data;
> +
> + seq_printf(m, " off=%d, target_seq=%d, repeats=%x, ts.tv_sec=%lld, ts.tv_nsec=%ld\n",
> + timeout->off, timeout->target_seq, timeout->repeats,
> + data->ts.tv_sec, data->ts.tv_nsec);
> + }
> + spin_unlock(&ctx->timeout_lock);
That seq_printf() line is way too long, please wrap like what is done
for the overflow printing above.
Outside of that, please also rebase on the for-6.12/io_uring branch, as
this one would not apply there.
Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2024-08-13 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240812020140epcas5p3431842ed5508ffb5ae9f1d1812cae4d5@epcas5p3.samsung.com>
2024-08-12 2:00 ` [PATCH] io_uring/fdinfo: add timeout_list to fdinfo Ruyi Zhang
2024-08-13 12:06 ` Jens Axboe [this message]
2024-08-13 13:19 ` Pavel Begunkov
[not found] <CGME20240814091610epcas5p36e83248f7f1be4171549abf6a8c037ee@epcas5p3.samsung.com>
2024-08-14 9:15 ` Ruyi Zhang
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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