From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>,
Caleb Sander Mateos <csander@purestorage.com>
Cc: io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] io_uring/wq: avoid indirect do_work/free_work calls
Date: Mon, 31 Mar 2025 13:06:33 -0600 [thread overview]
Message-ID: <174344799393.1769197.3886261668995690740.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250329161527.3281314-1-csander@purestorage.com>
On Sat, 29 Mar 2025 10:15:24 -0600, Caleb Sander Mateos wrote:
> struct io_wq stores do_work and free_work function pointers which are
> called on each work item. But these function pointers are always set to
> io_wq_submit_work and io_wq_free_work, respectively. So remove these
> function pointers and just call the functions directly.
>
>
Applied, thanks!
[1/1] io_uring/wq: avoid indirect do_work/free_work calls
commit: 842b5d5f87039d978a9748f8728cabe07a676252
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-03-31 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-29 16:15 [PATCH] io_uring/wq: avoid indirect do_work/free_work calls Caleb Sander Mateos
2025-03-29 19:07 ` Jens Axboe
2025-03-31 19:06 ` 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 \
--in-reply-to=174344799393.1769197.3886261668995690740.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=csander@purestorage.com \
--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