From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759189AbXJ3Xyh (ORCPT ); Tue, 30 Oct 2007 19:54:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754095AbXJ3Xy3 (ORCPT ); Tue, 30 Oct 2007 19:54:29 -0400 Received: from smtp-out.google.com ([216.239.45.13]:20828 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753112AbXJ3Xy2 (ORCPT ); Tue, 30 Oct 2007 19:54:28 -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=xo1Xnu+Vgnd+HNv+Bldly6zUCm8DL+vY6g2UXZRsUayIM6osl5p88GCftqDHFaBUJ Z9sDtWfB0EVfH3nYEuvYQ== Date: Tue, 30 Oct 2007 16:53:40 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Paul Jackson cc: clameter@sgi.com, 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: <20071030164414.b353e41c.pj@sgi.com> Message-ID: References: <1193433239.5032.95.camel@localhost> <1193434278.5032.106.camel@localhost> <20071026180713.aeedfac2.pj@sgi.com> <20071026194144.6042316a.pj@sgi.com> <20071027161955.e9d4d2db.pj@sgi.com> <20071028164637.8d1b45b0.pj@sgi.com> <20071028212745.57a7db67.pj@sgi.com> <20071029001554.c12b6b6c.pj@sgi.com> <20071030164414.b353e41c.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 Tue, 30 Oct 2007, Paul Jackson wrote: > > Those applications that currently rely on the remapping are going to be > > broken anyway because they are unknowingly receiving different nodes than > > they intended, this is the objection to remapping that Lee agreed with. > > No, they may or may not be broken. That depends on whether or not they had > specific hardware locality or affinity needs. > Of course they have specific affinity needs, that's why they used mempolicies. Remapping those policies to a set of nodes that resembles the original mempolicy's nodemask in terms of construction but without regard for the affinity those nodes have with respect to system topology could lead to performance degredations. > If you're running apps that have specific hardware affinity requirements, > then perhaps you shouldn't be moving them about in the first place ;). > And if they did have such needs, aren't they just as likely to be busted > by AND'ing off some of their nodes as they are by remapping those nodes? > No, because you're interleaving over the set of actual nodes you wanted to interleave over in the first place and not some pseudo-random set that your cpuset has access to. > I sure wish I knew what real world, actual, not hypothetical, situations > were motivating this. > You're defending the current remap behavior in terms of semantics of mempolicies? My position, and Choice C's position, is that you either get the exact (or partially-constructed) policy that you asked for, or you get the MPOL_DEFAULT behavior. What you don't get, even though it's currently how we do it, is a completely different set of nodes that you never intended to have a specific policy over. David