public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: lizetao <[email protected]>
Cc: io-uring <[email protected]>
Subject: Re: 答复: [PATCH for-next] io_uring: ensure io_queue_deferred() is out-of-line
Date: Thu, 2 Jan 2025 11:25:00 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 1/2/25 5:38 AM, lizetao wrote:
> Hi,
> 
>> -----Original Message-----
>> From: Jens Axboe <[email protected]>
>> Sent: Tuesday, December 31, 2024 8:37 AM
>> To: io-uring <[email protected]>
>> Subject: [PATCH for-next] io_uring: ensure io_queue_deferred() is out-of-line
>>
>> This is not the hot path, it's a slow path. Yet the locking for it is in the hot path,
>> and __cold does not prevent it from being inlined.
>>
>> Move the locking to the function itself, and mark it noinline as well to avoid it
>> polluting the icache of the hot path.
>>
>> Signed-off-by: Jens Axboe <[email protected]>
>>
>> ---
>>
>> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c index
>> 42d4cc5da73b..db198bd435b5 100644
>> --- a/io_uring/io_uring.c
>> +++ b/io_uring/io_uring.c
>> @@ -550,8 +550,9 @@ void io_req_queue_iowq(struct io_kiocb *req)
>>  	io_req_task_work_add(req);
>>  }
>>
>> -static __cold void io_queue_deferred(struct io_ring_ctx *ctx)
>> +static __cold noinline void io_queue_deferred(struct io_ring_ctx *ctx)
>>  {
>> +	spin_lock(&ctx->completion_lock);
> Just a digression, whether the io_uring subsystem welcomes scope-based
> cleanup helpers, this is somewhat

We welcome any change that makes sense :-)

For this particular one, no point having io_queue_deferred() marked as
cold yet still inlined, and no point having the locking outside of the
helper as that gets inlined as well.

-- 
Jens Axboe

      reply	other threads:[~2025-01-02 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-31  0:36 [PATCH for-next] io_uring: ensure io_queue_deferred() is out-of-line Jens Axboe
2025-01-02 12:38 ` 答复: " lizetao
2025-01-02 18:25   ` 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] \
    /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