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
| ||
|
Date: Mon, 6 Feb 2017 10:50:21 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Tejun Heo <tj@...nel.org> Cc: Andy Lutomirski <luto@...capital.net>, Linux API <linux-api@...r.kernel.org>, Li Zefan <lizefan@...wei.com>, Johannes Weiner <hannes@...xchg.org>, Ingo Molnar <mingo@...hat.com>, Paul Turner <pjt@...gle.com>, Mike Galbraith <efault@....de>, "open list:CONTROL GROUP (CGROUP)" <cgroups@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, kernel-team@...com, lvenanci@...hat.com Subject: Re: [PATCHSET for-4.11] cgroup: implement cgroup v2 thread mode On Thu, Feb 02, 2017 at 04:52:29PM -0500, Tejun Heo wrote: > > Why do you need to manually turn it on? That is, couldn't it be > > automatic based on what controllers are enabled? > > This came up already but it's not like some controllers are inherently > thread-only. Consider CPU, all in-context CPU cycle consumptions are > tied to the thread; however, we also want to be able to account for > CPU cycles consumed for, for example, memory reclaim or encryption > during writeback. > > I played with an interface where thread mode is enabled automatically > upto the common ancestor of the threads but not only was it > complicated to implement but also the eventual behavior was very > confusing as the resource domain can change without any active actions > from the user. I think keeping things simple is the right choice > here. Note that the explicit marking of the resource domains gets you exactly that. But let me reply in the other subthread.
Powered by blists - more mailing lists