From: Pavel Begunkov <asml.silence@gmail.com>
To: hexue <xue01.he@samsung.com>, axboe@kernel.dk
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V8] io_uring: releasing CPU resources when polling
Date: Wed, 25 Sep 2024 13:12:00 +0100 [thread overview]
Message-ID: <293e5757-4160-4734-931c-9830df7c2f88@gmail.com> (raw)
In-Reply-To: <20240925082932.3329096-1-xue01.he@samsung.com>
On 9/25/24 09:29, hexue wrote:
> On 24/08/12 1:59AM, hexue wrote:
>> This patch add a new hybrid poll at io_uring level, it also set a signal
>> "IORING_SETUP_HY_POLL" to application, aim to provide a interface for users
>> to enable use new hybrid polling flexibly.
>
> Hi, just a gentle ping, is there still in merge window? or any comment for
> this patch?
I don't have a strong opinion on the feature, but the open question
we should get some decision on is whether it's really well applicable to
a good enough set of apps / workloads, if it'll even be useful in the
future and/or for other vendors, and if the merit outweighs extra
8 bytes + 1 flag per io_kiocb and the overhead of 1-2 static key'able
checks in hot paths.
--
Pavel Begunkov
next prev parent reply other threads:[~2024-09-25 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240918021016epcas5p14d6e771ee39bee5dddf253c39b84110c@epcas5p1.samsung.com>
2024-09-18 2:10 ` [PATCH v8 RESEND] " hexue
[not found] ` <CGME20240925082937epcas5p1baa4bb786ea874400d7b18553cd57625@epcas5p1.samsung.com>
2024-09-25 8:29 ` [PATCH V8] " hexue
2024-09-25 12:12 ` Pavel Begunkov [this message]
[not found] ` <CGME20241024023812epcas5p1e5798728def570cb57679eebdd742d7b@epcas5p1.samsung.com>
2024-10-24 2:38 ` Re: [PATCH v8] " hexue
2024-10-24 14:18 ` Jens Axboe
2024-10-24 14:26 ` Pavel Begunkov
2024-10-24 14:40 ` Jens Axboe
2024-10-24 14:49 ` Pavel Begunkov
2024-10-24 14:49 ` Jens Axboe
[not found] ` <CGME20241025061108epcas5p173629b3149be6e3b96853eb32e61b9ab@epcas5p1.samsung.com>
2024-10-25 6:10 ` hexue
[not found] <CGME20240819025446epcas5p43dde8e55435917ecd0175400b0b7cc62@epcas5p4.samsung.com>
2024-08-19 2:54 ` [PATCH V8] " hexue
[not found] <CGME20240812015950epcas5p26c0eb254964abfe8a7ff05de0ead05f8@epcas5p2.samsung.com>
2024-08-12 1:59 ` [PATCH v8] " hexue
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=293e5757-4160-4734-931c-9830df7c2f88@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xue01.he@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
all inboxes | Powered by JetHome®