[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080303113621.1dfdda87.pj@sgi.com>
Date: Mon, 3 Mar 2008 11:36:21 -0600
From: Paul Jackson <pj@....com>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: maxk@...lcomm.com, mingo@...e.hu, tglx@...utronix.de,
oleg@...sign.ru, rostedt@...dmis.org, linux-kernel@...r.kernel.org,
rientjes@...gle.com
Subject: Re: [RFC/PATCH] cpuset: cpuset irq affinities
Peter wrote:
> The system group can overlap with anything that does need system services.
I suppose IRQs need to overlap like this, but cpusets often can't
overlap like this.
If a system has the cgroup hierarchy you draw:
/cgroup
/cgroup/system
/cgroup/system/boot
/cgroup/big_honking_app
/cgroup/rt_domain
this must not force the cpuset hierarchy to be:
/dev/cpuset
/dev/cpuset/system
/dev/cpuset/system/boot
/dev/cpuset/big_honking_app
/dev/cpuset/rt_domain
I guess this means IRQs cannot be added to the cpuset subsystem
of cgroups. Rather they have to be added to some other cgroup
subsystem, perhaps a new one just for IRQs.
In perhaps the most common sort of cpuset hierarchy:
/dev/cpuset
/dev/cpuset/boot
/dev/cpuset/batch_sched
/dev/cpuset/big_honking_app
/dev/cpuset/rt_domain
none of boot or its siblings overlap.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.940.382.4214
--
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/
Powered by blists - more mailing lists