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]

Date:	Wed, 12 Mar 2008 12:11:14 -0700
From:	Max Krasnyanskiy <maxk@...lcomm.com>
To:	Paul Jackson <pj@....com>
CC:	menage@...gle.com, mingo@...e.hu, a.p.zijlstra@...llo.nl,
	linux-kernel@...r.kernel.org
Subject: Re: boot cgroup questions

Paul Jackson wrote:
> Max K wrote:
>> How is that any different from tasks ? Exact same example right back at you.
>> Suppose I have a task that needs to run in A and B but not C.
> 
> Can't happen.
Of course it can. See below.

> Each task belongs to exactly one cpuset, no exceptions.
Sure. Same for irqs.

> That's why you can't "treat irqs just like tasks".
Sure you can.

I was talking about running on the _cpus_ that belong to the "sets A and B but 
not C" and not that a task must belong to more than one cpuset. Unless I 
misinterpreted your example you were talking about exact same thing. In other 
words that an irq needs to assigned to the _cpus_ in the sets A and B but not C.
Makes sense ?

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/