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 2/2] io_uring/io-wq: limit io poller cpuset to ambient one
Date: Tue, 10 Sep 2024 08:55:56 -0600 [thread overview]
Message-ID: <03b4c259-ab70-4a61-a428-82b0261752b5@kernel.dk> (raw)
In-Reply-To: <20240910143320.123234-3-felix.moessbauer@siemens.com>
On 9/10/24 8:33 AM, Felix Moessbauer wrote:
> The io work queue polling threads are userland threads that just never
> exit to the userland. By that, they are also assigned to a cgroup (the
> group of the creating task).
>
> When creating a new io poller, this poller should inherit the cpu limits
> of the cgroup, as it belongs to the cgroup of the creating task.
Same comment on polling threads and the use of ambient.
--
Jens Axboe
next prev parent reply other threads:[~2024-09-10 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 14:33 [PATCH 0/2] io_uring/io-wq: respect cgroup cpusets Felix Moessbauer
2024-09-10 14:33 ` [PATCH 1/2] io_uring/io-wq: do not allow pinning outside of cpuset Felix Moessbauer
2024-09-10 14:55 ` Jens Axboe
2024-09-10 14:33 ` [PATCH 2/2] io_uring/io-wq: limit io poller cpuset to ambient one Felix Moessbauer
2024-09-10 14:55 ` Jens Axboe [this message]
2024-09-10 14:53 ` [PATCH 0/2] io_uring/io-wq: respect cgroup cpusets Jens Axboe
2024-09-10 15:08 ` MOESSBAUER, Felix
2024-09-10 15:17 ` Jens Axboe
2024-09-10 15:37 ` MOESSBAUER, Felix
2024-09-10 15:39 ` Jens Axboe
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=03b4c259-ab70-4a61-a428-82b0261752b5@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