From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755072AbYCLXbS (ORCPT ); Wed, 12 Mar 2008 19:31:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752094AbYCLXbI (ORCPT ); Wed, 12 Mar 2008 19:31:08 -0400 Received: from relay2.sgi.com ([192.48.171.30]:58548 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751572AbYCLXbH (ORCPT ); Wed, 12 Mar 2008 19:31:07 -0400 Date: Wed, 12 Mar 2008 18:30:59 -0500 From: Paul Jackson To: Max Krasnyanskiy Cc: menage@google.com, mingo@elte.hu, a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org Subject: Re: boot cgroup questions Message-Id: <20080312183059.6716d630.pj@sgi.com> In-Reply-To: <47D8593A.6040503@qualcomm.com> References: <47D73086.2030008@qualcomm.com> <6599ad830803111827n1cb8e2c7i47c2ef3f3bb58995@mail.gmail.com> <47D7411E.1000009@qualcomm.com> <6599ad830803111936jd940deam8584bc971c3b6f41@mail.gmail.com> <47D74595.4080100@qualcomm.com> <6599ad830803112009y18d9e43ft8e3fc4a551d891da@mail.gmail.com> <20080311235939.1ebee8e3.pj@sgi.com> <47D81FE1.6030205@qualcomm.com> <20080312135746.89456f2a.pj@sgi.com> <47D82AD2.1070108@qualcomm.com> <20080312143253.3dd72c7f.pj@sgi.com> <47D83858.4030806@qualcomm.com> <20080312153712.bc5df7a1.pj@sgi.com> <47D8593A.6040503@qualcomm.com> Organization: SGI X-Mailer: Sylpheed version 2.2.4 (GTK+ 2.12.0; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 1.940.382.4214