From: Jens Axboe <[email protected]>
To: [email protected], [email protected],
Breno Leitao <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH] io_uring: One wqe per wq
Date: Wed, 15 Mar 2023 14:44:01 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 10 Mar 2023 12:11:07 -0800, Breno Leitao wrote:
> Right now io_wq allocates one io_wqe per NUMA node. As io_wq is now
> bound to a task, the task basically uses only the NUMA local io_wqe, and
> almost never changes NUMA nodes, thus, the other wqes are mostly
> unused.
>
> Allocate just one io_wqe embedded into io_wq, and uses all possible cpus
> (cpu_possible_mask) in the io_wqe->cpumask.
>
> [...]
Applied, thanks!
[1/1] io_uring: One wqe per wq
commit: c122b27ea454f5f8ed3066964c67e9aea4e11fc8
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-03-15 20:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 20:11 [PATCH] io_uring: One wqe per wq Breno Leitao
2023-03-10 20:38 ` Jens Axboe
2023-03-11 20:56 ` Pavel Begunkov
2023-03-11 22:13 ` Jens Axboe
2023-03-13 3:56 ` Pavel Begunkov
2023-03-15 20:44 ` 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=167891304198.106283.16674521434746961243.b4-ty@kernel.dk \
[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