From: hexue <xue01.he@samsung.com>
To: axboe@kernel.dk, asml.silence@gmail.com
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Re: [PATCH v8] io_uring: releasing CPU resources when polling
Date: Fri, 25 Oct 2024 14:10:59 +0800 [thread overview]
Message-ID: <20241025061059.1172576-1-xue01.he@samsung.com> (raw)
In-Reply-To: <62e57b0e-b646-4f96-bb83-5a0ecb4050da@kernel.dk>
On 10/24/24 14:49 Jens Axboe wrote:
>On 10/24/24 8:49 AM, Pavel Begunkov wrote:
>> On 10/24/24 15:40, Jens Axboe wrote:
>>> On 10/24/24 8:26 AM, Pavel Begunkov wrote:
>>>> On 10/24/24 15:18, Jens Axboe wrote:
>>>>> On 10/23/24 8:38 PM, hexue wrote:
>>>>>> On 9/25/2024 12:12, Pavel Begunkov wrote:
>>>> ...
>Ah true, well some other spot then, should be pretty easy to find 8
>bytes for iopoll_start. As mentioned, the point is really just to THINK
>about where it should go, rather than lazily just shove it at the end
>like no thought has been given to it.
Thanks a lot for these suggestions and help. I will revise and submit a
complete v9 patch, thank you very much.
--
Xue
prev parent reply other threads:[~2024-10-25 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240918021016epcas5p14d6e771ee39bee5dddf253c39b84110c@epcas5p1.samsung.com>
2024-09-18 2:10 ` [PATCH v8 RESEND] io_uring: releasing CPU resources when polling hexue
[not found] ` <CGME20240925082937epcas5p1baa4bb786ea874400d7b18553cd57625@epcas5p1.samsung.com>
2024-09-25 8:29 ` [PATCH V8] " hexue
2024-09-25 12:12 ` Pavel Begunkov
[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 [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 \
--in-reply-to=20241025061059.1172576-1-xue01.he@samsung.com \
--to=xue01.he@samsung.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@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