From: Jens Axboe <[email protected]>
To: hexue <[email protected]>
Cc: [email protected], [email protected],
[email protected]
Subject: Re: [PATCH v9 1/1] io_uring: releasing CPU resources when polling
Date: Mon, 4 Nov 2024 09:21:17 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/4/24 12:29 AM, hexue wrote:
> On 11/1/2024 08:06, Jens Axboe wrote:
>> On 11/1/24 3:19 AM, hexue wrote:
>>> A new hybrid poll is implemented on the io_uring layer. Once IO issued,
>>> it will not polling immediately, but block first and re-run before IO
>>> complete, then poll to reap IO. This poll function could be a suboptimal
>>> solution when running on a single thread, it offers the performance lower
>>> than regular polling but higher than IRQ, and CPU utilization is also lower
>>> than polling.
>>
>> This looks much better now.
>>
>> Do you have a patch for liburing to enable testing of hybrid polling
>> as well? Don't care about perf numbers for that, but it should get
>> exercised.
>
> Sure, I'll add some liburing test cases and submit patch soon.
Thanks! Bonus for also documenting the setup flag in
man/io_uring_setup.2 as well in the liburing repo. If things don't get
documented, then people don't know they exist...
--
Jens Axboe
next prev parent reply other threads:[~2024-11-04 16:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241101092007epcas5p29e0c6a6c7a732642cba600bb1c1faff0@epcas5p2.samsung.com>
2024-11-01 9:19 ` [PATCH v9 0/1] io_uring: releasing CPU resources when polling hexue
[not found] ` <CGME20241101092009epcas5p117843070fa5edd377469f13af388fc06@epcas5p1.samsung.com>
2024-11-01 9:19 ` [PATCH v9 1/1] " hexue
2024-11-01 14:06 ` Jens Axboe
[not found] ` <CGME20241104072914epcas5p2d44c91a277995d5c69bacd4e4308933d@epcas5p2.samsung.com>
2024-11-04 7:29 ` hexue
2024-11-04 16:21 ` Jens Axboe [this message]
2024-11-01 14:21 ` [PATCH v9 0/1] " Jens Axboe
2024-11-01 15:18 ` Jens Axboe
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