From: Jens Axboe <[email protected]>
To: hexue <[email protected]>
Cc: [email protected], [email protected],
[email protected]
Subject: Re: [PATCH v5] Subject: io_uring: releasing CPU resources when polling
Date: Fri, 28 Jun 2024 15:13:48 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/25/24 2:39 AM, hexue wrote:
> On 6/19/24 15:51, Jens Axboe wrote:
>> On 6/19/24 08:18, hexue wrote:
>>
>> While I do suspect there are cases where hybrid polling will be more
>> efficient, not sure there are many of them. And you're most likely
>> better off just doing IRQ driven IO at that point? Particularly with the
>> fairly substantial overhead of maintaining the data you need, and time
>> querying.
>
> I rebuilt the test cases based on your information, that is, each drive has
> only one thread with high pressure, there is a significant performance loss.
> I previously provided test data for a single drive with multi-threaded, which
> can achieve performance stable and CPU savings.
>
> Thanks for your data, I will reduce the cost of each IO and submit the next
> version.
Sounds good, thanks. I don't doubt it's useful for some cases as-is, but
I think there's the potential for it to be more useful.
--
Jens Axboe
prev parent reply other threads:[~2024-06-28 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240619071833epcas5p274ddb249a75e4b3006b48d1378071923@epcas5p2.samsung.com>
2024-06-19 7:18 ` [PATCH v5] Subject: io_uring: releasing CPU resources when polling hexue
2024-06-19 15:22 ` Pavel Begunkov
[not found] ` <CGME20240624025406epcas5p4ce2b80c63d185cf9e02615365fb3d89d@epcas5p4.samsung.com>
2024-06-24 2:54 ` hexue
2024-06-19 15:51 ` Jens Axboe
[not found] ` <CGME20240625083927epcas5p4b9d4887854da457946504e98f104e3c2@epcas5p4.samsung.com>
2024-06-25 8:39 ` hexue
2024-06-28 21:13 ` Jens Axboe [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] \
/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