From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760848AbXHCBDL (ORCPT ); Thu, 2 Aug 2007 21:03:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755019AbXHCBC6 (ORCPT ); Thu, 2 Aug 2007 21:02:58 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:50642 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754899AbXHCBC5 (ORCPT ); Thu, 2 Aug 2007 21:02:57 -0400 Date: Thu, 2 Aug 2007 18:02:56 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Nick Piggin cc: Andi Kleen , Ingo Molnar , Linux Kernel Mailing List , Linux Memory Management List Subject: Re: [rfc] balance-on-fork NUMA placement In-Reply-To: <20070803005700.GD14775@wotan.suse.de> Message-ID: References: <20070731054142.GB11306@wotan.suse.de> <200707311114.09284.ak@suse.de> <20070802034201.GA32631@wotan.suse.de> <20070803002639.GC14775@wotan.suse.de> <20070803005700.GD14775@wotan.suse.de> 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, 3 Aug 2007, Nick Piggin wrote: > > Ok. So MPOL_BIND on a single node. We would have to save the current > > memory policy on the stack and then restore it later. Then you would need > > a special call anyways. > > Well the memory policy will already be set to MPOL_BIND at this point. > The slab allocator I think would just have to honour the node at the > object level. Who set the policy? The parent process may have its own memory policy. If you set that then the earlier policy is lost.