linux-kernel - Re: boot cgroup questions

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <47D82F6D.2000801@qualcomm.com>
Date:	Wed, 12 Mar 2008 12:30:53 -0700
From:	Max Krasnyanskiy <maxk@...lcomm.com>
To:	Paul Jackson <pj@....com>
CC:	Paul Menage <menage@...gle.com>, mingo@...e.hu,
	a.p.zijlstra@...llo.nl, linux-kernel@...r.kernel.org
Subject: Re: boot cgroup questions

Paul Jackson wrote:
> Paul M wrote:
>> Not cgroups, no. If you really wanted to extend cpusets specifically
>> to allow irqs to be assigned to a cpuset to control which cpus they
>> could execute on, then that might be a possibility. But I don't see
>> how this would be useful for any other cgroup subsystem, so it doesn't
>> belong in the generic framework.
> 
> Ok - a sensible decision.
> 
>> My feeling is that just using a simple bitmask assignment, unrelated
>> to cpusets or cgroups, as Max suggested in his later email is the way
>> to go.
> 
> I'll have to have another go at reading his replies.  I seem to have
> more difficulty making sense of his posts ... not sure why.
I'm sure it's because of gazillion typos in them :).

Max
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/