From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765772AbXJZVMY (ORCPT ); Fri, 26 Oct 2007 17:12:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759107AbXJZVMQ (ORCPT ); Fri, 26 Oct 2007 17:12:16 -0400 Received: from netops-testserver-4-out.sgi.com ([192.48.171.29]:59725 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1758463AbXJZVMP (ORCPT ); Fri, 26 Oct 2007 17:12:15 -0400 Date: Fri, 26 Oct 2007 14:12:15 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: David Rientjes cc: Paul Jackson , Lee.Schermerhorn@hp.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: Message-ID: References: <20071025185506.8c373aa8.pj@sgi.com> <1193412644.5032.13.camel@localhost> <20071026120037.7b95a136.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 Fri, 26 Oct 2007, David Rientjes wrote: > You would pass NODE_MASK_ALL if your intent was to interleave over > everything you have access to, yes. Otherwise you can pass whatever you > want access to and your interleaved nodemask becomes > mpol_rebind_policy()'s newmask formal (the cpuset's new mems_allowed) > AND'd with pol->passed_nodemask. We would need two fields in the policy structure 1. The specified nodemask (generally ignored) 2. The effective nodemask (specified & cpuset_mems_allowed) If we have these two then its easy to get a bit further by making the first nodemask a relative nodemask. The calculation of the effective nodemask changes somewhat but the logic is then applicable to MPOL_BIND as well.