From: Jens Axboe <axboe@kernel.dk>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: asml.silence@gmail.com, linux-kernel@vger.kernel.org,
io-uring@vger.kernel.org, cgroups@vger.kernel.org,
dqminh@cloudflare.com, longman@redhat.com,
adriaan.schmidt@siemens.com, florian.bezdeka@siemens.com
Subject: Re: [PATCH v3 0/2] io_uring/io-wq: respect cgroup cpusets
Date: Wed, 11 Sep 2024 07:28:18 -0600 [thread overview]
Message-ID: <172606129845.167290.7805052336711734654.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240910171157.166423-1-felix.moessbauer@siemens.com>
On Tue, 10 Sep 2024 19:11:55 +0200, Felix Moessbauer wrote:
> this series continues the affinity cleanup work started in
> io_uring/sqpoll. It has been successfully tested against the liburing
> testsuite (make runtests), liburing @ caae94903d2e201.
>
> The test wq-aff.t succeeds if at least cpu 0,1 are in
> the set and fails otherwise. This is expected, as the test wants
> to pin on these cpus. I'll send a patch for liburing to skip that test
> in case this pre-condition is not met.
>
> [...]
Applied, thanks!
[1/2] io_uring/io-wq: do not allow pinning outside of cpuset
commit: 0997aa5497c714edbb349ca366d28bd550ba3408
[2/2] io_uring/io-wq: inherit cpuset of cgroup in io worker
commit: 84eacf177faa605853c58e5b1c0d9544b88c16fd
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-09-11 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 17:11 [PATCH v3 0/2] io_uring/io-wq: respect cgroup cpusets Felix Moessbauer
2024-09-10 17:11 ` [PATCH v3 1/2] io_uring/io-wq: do not allow pinning outside of cpuset Felix Moessbauer
2024-09-10 17:11 ` [PATCH v3 2/2] io_uring/io-wq: inherit cpuset of cgroup in io worker Felix Moessbauer
2024-09-10 17:42 ` Waiman Long
2024-09-11 7:02 ` MOESSBAUER, Felix
2024-09-11 13:28 ` 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=172606129845.167290.7805052336711734654.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=adriaan.schmidt@siemens.com \
--cc=asml.silence@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=dqminh@cloudflare.com \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.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