Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759356AbYCHCAP (ORCPT ); Fri, 7 Mar 2008 21:00:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753760AbYCHCAD (ORCPT ); Fri, 7 Mar 2008 21:00:03 -0500 Received: from relay2.sgi.com ([192.48.171.30]:58481 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753357AbYCHCAA (ORCPT ); Fri, 7 Mar 2008 21:00:00 -0500 Date: Fri, 7 Mar 2008 17:59:38 -0800 (PST) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Paul Jackson cc: David Rientjes , akpm@linux-foundation.org, Lee.Schermerhorn@hp.com, ak@suse.de, linux-kernel@vger.kernel.org Subject: Re: [patch -mm 2/2] mempolicy: use default_policy mode instead of MPOL_DEFAULT In-Reply-To: <20080307193543.6a55ff8d.pj@sgi.com> Message-ID: References: <20080307192845.0492c6f9.pj@sgi.com> <20080307193543.6a55ff8d.pj@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 663 Lines: 14 And where is the patch to set the system (or cpuset....) default policy? ;-) Note that the system default policy changes during bootup. Could that be done with the default policy? We had some issues a while back with processes spawned at boot inheriting the interleave policy. If they could refer to default_policy instead then a change of default_policy would switch all spawned processes to use MPOL_DEFAULT? -- 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/