linux-kernel - Re: [PATCH v2 2/2] io_uring/io-wq: limit io poller cpuset to ambient one

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4c854271-3c5e-4549-81e6-dfa0a69bf9b6@kernel.dk>
Date: Tue, 10 Sep 2024 10:06:17 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Felix Moessbauer <felix.moessbauer@...mens.com>
Cc: asml.silence@...il.com, linux-kernel@...r.kernel.org,
 io-uring@...r.kernel.org, cgroups@...r.kernel.org, dqminh@...udflare.com,
 longman@...hat.com, adriaan.schmidt@...mens.com, florian.bezdeka@...mens.com
Subject: Re: [PATCH v2 2/2] io_uring/io-wq: limit io poller cpuset to ambient
 one

On 9/10/24 9:45 AM, Felix Moessbauer wrote:
> The io worker 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 worker, this worker should inherit the cpuset
> of the cgroup.

This still has that same ambient usage in the title which I just
cannot make sense of?

-- 
Jens Axboe