From: Genes Lists <lists@sapience.com>
To: Andres Freund <andres@anarazel.de>,
Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Jens Axboe <axboe@kernel.dk>,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pavel Begunkov <asml.silence@gmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.4 800/800] io_uring: Use io_schedule* in cqring wait
Date: Sun, 23 Jul 2023 15:44:28 -0400 [thread overview]
Message-ID: <0b738504-07af-4e81-2a9f-2b6f3754a2f0@sapience.com> (raw)
In-Reply-To: <20230723185856.h6vjipo4rguf6emt@awork3.anarazel.de>
On 7/23/23 14:58, Andres Freund wrote:
> Just to confirm I understand: Your concern is how it looks in mpstat, not
> performance or anything like that?
Right - there is no performance issue or any other issue to my knowledge
and cores are idle.
So, as you said, its just a small reporting item - which is now quite clear.
thank you.
gene
next prev parent reply other threads:[~2023-07-23 19:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 19:37 [PATCH 6.4 000/800] 6.4.4-rc1 review Greg Kroah-Hartman
2023-07-16 19:39 ` [PATCH 6.4 119/800] sctp: add bpf_bypass_getsockopt proto callback Greg Kroah-Hartman
2023-07-16 19:50 ` [PATCH 6.4 800/800] io_uring: Use io_schedule* in cqring wait Greg Kroah-Hartman
2023-07-23 9:39 ` Oleksandr Natalenko
2023-07-23 10:50 ` Greg Kroah-Hartman
2023-07-23 10:55 ` Genes Lists
2023-07-23 10:56 ` Oleksandr Natalenko
2023-07-23 12:11 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-07-23 17:35 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-07-23 15:31 ` Jens Axboe
2023-07-23 17:43 ` Genes Lists
2023-07-23 18:06 ` Oleksandr Natalenko
2023-07-23 18:58 ` Andres Freund
2023-07-23 19:44 ` Genes Lists [this message]
2023-07-24 15:47 ` Jens Axboe
2023-07-24 18:04 ` Genes Lists
2023-07-17 5:53 ` [PATCH 6.4 000/800] 6.4.4-rc1 review Naresh Kamboju
2023-07-17 18:48 ` Greg Kroah-Hartman
2023-07-17 11:51 ` Ron Economos
2023-07-17 13:37 ` Guenter Roeck
2023-07-17 17:24 ` Greg Kroah-Hartman
2023-07-17 17:32 ` Conor Dooley
2023-07-17 20:46 ` Shuah Khan
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=0b738504-07af-4e81-2a9f-2b6f3754a2f0@sapience.com \
--to=lists@sapience.com \
--cc=andres@anarazel.de \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gregkh@linuxfoundation.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
--cc=stable@vger.kernel.org \
/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
all inboxes | Powered by JetHome®