[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20061030124102.f8957d06.pj@sgi.com>
Date: Mon, 30 Oct 2006 12:41:02 -0800
From: Paul Jackson <pj@....com>
To: "Paul Menage" <menage@...gle.com>
Cc: dmccr@...ibm.com, dev@...nvz.org, linux-kernel@...r.kernel.org,
devel@...nvz.org, ckrm-tech@...ts.sourceforge.net
Subject: Re: [ckrm-tech] [RFC] Resource Management - Infrastructure choices
> I believe that
> there are people out there who depend on them (right, PaulJ?)
Yes. For example a common usage pattern has the system admin carve
off a big chunk of CPUs and Memory Nodes into a cpuset for the batch
scheduler to manage, within which the batch scheduler creates child
cpusets, roughly one for each job under its control.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@....com> 1.925.600.0401
-
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