From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753718AbYCMA5W (ORCPT ); Wed, 12 Mar 2008 20:57:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751803AbYCMA5M (ORCPT ); Wed, 12 Mar 2008 20:57:12 -0400 Received: from wolverine02.qualcomm.com ([199.106.114.251]:53678 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751749AbYCMA5L (ORCPT ); Wed, 12 Mar 2008 20:57:11 -0400 X-IronPort-AV: E=McAfee;i="5200,2160,5250"; a="1073361" Message-ID: <47D87BE5.4010702@qualcomm.com> Date: Wed, 12 Mar 2008 17:57:09 -0700 From: Max Krasnyanskiy User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Paul Jackson CC: menage@google.com, mingo@elte.hu, a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org Subject: Re: boot cgroup questions 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> <20080312183059.6716d630.pj@sgi.com> In-Reply-To: <20080312183059.6716d630.pj@sgi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Paul Jackson wrote: > 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. Crazy idea. How about we add support for sym links to the cgroup fs ? It's still much cleaner imo than dealing with complex irq grouping schemes. In other words with symlinks we could do `-- cpuset |-- A -> X/A |-- B -> X/B |-- C `-- X |-- A `-- B The software that is used to the flat structure won't know the difference. Max