[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080312183059.6716d630.pj@sgi.com>
Date: Wed, 12 Mar 2008 18:30:59 -0500
From: Paul Jackson <pj@....com>
To: Max Krasnyanskiy <maxk@...lcomm.com>
Cc: menage@...gle.com, mingo@...e.hu, a.p.zijlstra@...llo.nl,
linux-kernel@...r.kernel.org
Subject: Re: boot cgroup questions
Max K wrote:
> btw I still do not see the "incompatibility" argument.
It's similar, perhaps, to what happens when we try to accomodate two
architectures in one file system, with things like:
/x86_64/bin
/ia64/bin
replacing the well known /bin.
Things break. Apps such as the major batch schedulers (PBS and LSF)
and various other tools and scripts buried here and there have come
used to developing particular cpuset hierarchies over the last couple
of years.
Any time you force another dimension into such an existing hierarchy,
things break, and people get annoyed.
Sure ... the kernel doesn't care ... it can handle whatever hierarchy
you like.
--
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