From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753485AbXJ3XRz (ORCPT ); Tue, 30 Oct 2007 19:17:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754157AbXJ3XRg (ORCPT ); Tue, 30 Oct 2007 19:17:36 -0400 Received: from smtp-out.google.com ([216.239.33.17]:34875 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753515AbXJ3XRf (ORCPT ); Tue, 30 Oct 2007 19:17:35 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:date:from:x-x-sender:to:cc:subject:in-reply-to: message-id:references:mime-version:content-type; b=MIwc2D5qmnQIEdOmJ2gnttHb7L+gZ1EoX4ietYstcFVtarQ+qL1NgAQF1yS8mKsLO Fzs/oHOvS10J9LDfi4DJg== Date: Tue, 30 Oct 2007 16:17:18 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Paul Jackson cc: Lee Schermerhorn , clameter@sgi.com, akpm@linux-foundation.org, ak@suse.de, linux-kernel@vger.kernel.org Subject: Re: [patch 2/2] cpusets: add interleave_over_allowed option In-Reply-To: <20071029114109.46285026.pj@sgi.com> Message-ID: References: <20071025185506.8c373aa8.pj@sgi.com> <1193412644.5032.13.camel@localhost> <20071026120037.7b95a136.pj@sgi.com> <1193433239.5032.95.camel@localhost> <1193434278.5032.106.camel@localhost> <1193670617.5035.38.camel@localhost> <20071029114109.46285026.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 On Mon, 29 Oct 2007, Paul Jackson wrote: > But in any case, we (the kernel) are just providing the mechanisms. > If they don't fit ones needs, don't use them ;). > The kernel is providing the mechanism to interleave over a set of nodes or prefer a single node for allocations, but it also provides for remapping those to different nodes, without regard to locality or affinity to specific hardware, when the cpuset changes. That's what Choice C is intended to replace: a node means a node so either you get an effected mempolicy over the nodemask you asked for, or MPOL_DEFAULT is used because you lack sufficient access. David