Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264246AbUJGNAq (ORCPT ); Thu, 7 Oct 2004 09:00:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269820AbUJGM44 (ORCPT ); Thu, 7 Oct 2004 08:56:56 -0400 Received: from ecbull20.frec.bull.fr ([129.183.4.3]:54416 "EHLO ecbull20.frec.bull.fr") by vger.kernel.org with ESMTP id S269802AbUJGMyU (ORCPT ); Thu, 7 Oct 2004 08:54:20 -0400 Date: Thu, 7 Oct 2004 14:47:46 +0200 (CEST) From: Simon Derr X-X-Sender: derrs@openx3.frec.bull.fr To: Paul Jackson cc: colpatch@us.ibm.com, mbligh@aracnet.com, Simon.Derr@bull.net, pwil3058@bigpond.net.au, frankeh@watson.ibm.com, dipankar@in.ibm.com, akpm@osdl.org, ckrm-tech@lists.sourceforge.net, efocht@hpce.nec.com, lse-tech@lists.sourceforge.net, hch@infradead.org, steiner@sgi.com, jbarnes@sgi.com, sylvain.jeaugey@bull.net, djh@sgi.com, linux-kernel@vger.kernel.org, ak@suse.de, sivanich@sgi.com Subject: Re: [Lse-tech] [PATCH] cpusets - big numa cpu and memory placement In-Reply-To: <20041007015107.53d191d4.pj@sgi.com> Message-ID: References: <20040805100901.3740.99823.84118@sam.engr.sgi.com> <247790000.1091762644@[10.10.2.4]> <200408061730.06175.efocht@hpce.nec.com> <20040806231013.2b6c44df.pj@sgi.com> <411685D6.5040405@watson.ibm.com> <20041001164118.45b75e17.akpm@osdl.org> <20041001230644.39b551af.pj@sgi.com> <20041002145521.GA8868@in.ibm.com> <415ED3E3.6050008@watson.ibm.com> <415F37F9.6060002@bigpond.net.au> <821020000.1096814205@[10.10.2.4]> <20041003083936.7c844ec3.pj@sgi.com> <834330000.1096847619@[10.10.2.4]> <835810000.1096848156@[10.10.2.4]> <20041003175309.6b02b5c6.pj@sgi.com> <838090000.1096862199@[10.10.2.4]> <20041003212452.1a15a49a.pj@sgi.com> <843670000.1096902220@[10.10.2.4]> <58780000.1097004886@flay> <20041005172808.64d3cc2b.pj@sgi.com> <1193270000.1097025361@[10.10.2.4]> <20041005190852.7b1fd5b5.pj@sgi.com> <1097103580.4907.84.camel@arrakis> <20041007015107.53d191d4.pj@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1001 Lines: 21 On Thu, 7 Oct 2004, Paul Jackson wrote: > > I don't see what non-exclusive cpusets buys us. > > One can nest them, overlap them, and duplicate them ;) I would also add, if the decision comes to make 'real exclusive' cpusets, my previous example, as a use for non-exclusive cpusets: we are running jobs that need to be 'mostly' isolated on some part of the system, and run in a specific location. We use cpusets for that. But we can't afford to dedicate a part of the system for administrative tasks (daemons, init..). These tasks should not be put inside one of the 'exclusive' cpusets, even temporary : they do not belong there. They should just be allowed to steal a few cpu cycles from time to time : non exclusive cpusets are the way to go. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/