From: Fengnan Chang <changfengnan@bytedance.com>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: axboe@kernel.dk, xiaobing.li@samsung.com,
io-uring@vger.kernel.org, Diangang Li <lidiangang@bytedance.com>
Subject: Re: [External] Re: [PATCH] io_uring: add IORING_SETUP_NO_SQTHREAD_STATS flag to disable sqthread stats collection
Date: Thu, 16 Oct 2025 20:09:47 +0800 [thread overview]
Message-ID: <CAPFOzZuhDU0yD=nGioR1a3u9C0ZXxOpahZxv=PsHThEJJK=A3w@mail.gmail.com> (raw)
In-Reply-To: <28a8fdc0-2693-4ff1-bcb3-2b8f67e7b794@gmail.com>
Pavel Begunkov <asml.silence@gmail.com> 于2025年10月16日周四 20:03写道:
>
> On 10/16/25 12:45, Fengnan Chang wrote:
> > introduces a new flag IORING_SETUP_NO_SQTHREAD_STATS that allows
> > user to disable the collection of statistics in the sqthread.
> > When this flag is set, the getrusage() calls in the sqthread are
> > skipped, which can provide a small performance improvement in high
> > IOPS workloads.
>
> It was added for dynamically adjusting SQPOLL timeouts, at least that
> what the author said, but then there is only the fdinfo to access it,
> which is slow and unreliable, and no follow up to expose it in a
> better way. To be honest, I have serious doubts it has ever been used,
> and I'd be tempted to completely remove it out of the kernel. Fdinfo
> format wasn't really stable for io_uring and we can leave it printing
> some made up values like 100% util.
Agree, IMO turning off stats by default would be a better approach, but
I'm concerned that some people are using this in fdinfo. I'd like to hear
the author's opinion.
>
> If it's there for outside monitoring, that should be done with bpf,
> with maybe additional tracepoints.
>
> --
> Pavel Begunkov
>
next prev parent reply other threads:[~2025-10-16 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 11:45 [PATCH] io_uring: add IORING_SETUP_NO_SQTHREAD_STATS flag to disable sqthread stats collection Fengnan Chang
2025-10-16 12:04 ` Pavel Begunkov
2025-10-16 12:09 ` Fengnan Chang [this message]
[not found] ` <CGME20251017091046epcas5p35dfbcf4979f79b3a80441aed2d31a906@epcas5p3.samsung.com>
2025-10-17 9:06 ` Xiaobing Li
2025-10-17 9:21 ` [External] " Fengnan Chang
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='CAPFOzZuhDU0yD=nGioR1a3u9C0ZXxOpahZxv=PsHThEJJK=A3w@mail.gmail.com' \
--to=changfengnan@bytedance.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=lidiangang@bytedance.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