public inbox for [email protected]
 help / color / mirror / Atom feed
From: Xiaobing Li <[email protected]>
To: [email protected]
Cc: [email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected],
	[email protected], [email protected]
Subject: Re: Re: [PATCH v5] io_uring: Statistics of the true utilization of sq threads.
Date: Sun, 24 Dec 2023 21:36:36 -0500	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 12/22/23 07:31 AM, Jens Axboe wrote:
> Yep that would work, just leave the stats calculation to the tool
> querying it. Which is really how it should be.
>
>> In addition, on register opcode - generally it is used for resource like
>> buffers, handles etc.. I am not sure how that can help here. If you have
>> something in mind, could you please elaborate in more detail?
>
> It's also a bit of a dumping ground for any kind of out-of-band
> mechanism, so it would work fine for something like this too. But since
> we already have fdinfo and with your idea of just logging work and total
> time, then we should probably just stick with that.

Thanks for explained. I'll send out a v6.

      parent reply	other threads:[~2023-12-26  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20231218085950epcas5p4171efba84d8c14bf1307aa16c48414ca@epcas5p4.samsung.com>
2023-12-18  8:51 ` [PATCH v5] io_uring: Statistics of the true utilization of sq threads Xiaobing Li
2023-12-18 15:53   ` Jens Axboe
     [not found]     ` <CGME20231222084334epcas5p10badfe3c82a6b8355c03f8d0aa192892@epcas5p1.samsung.com>
2023-12-22  8:35       ` Xiaobing Li
2023-12-22 14:31         ` Jens Axboe
     [not found]           ` <CGME20231225024445epcas5p1d0525b9595544d8fe7b8ea60f5741b58@epcas5p1.samsung.com>
2023-12-25  2:36             ` Xiaobing Li [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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [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