Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758062AbZCLQ2Z (ORCPT ); Thu, 12 Mar 2009 12:28:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756007AbZCLQ2G (ORCPT ); Thu, 12 Mar 2009 12:28:06 -0400 Received: from smtp.ultrahosting.com ([74.213.174.254]:45238 "EHLO smtp.ultrahosting.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756114AbZCLQ2F (ORCPT ); Thu, 12 Mar 2009 12:28:05 -0400 Date: Thu, 12 Mar 2009 12:08:11 -0400 (EDT) From: Christoph Lameter X-X-Sender: cl@qirst.com To: Matt Mackall cc: David Rientjes , KOSAKI Motohiro , Andrew Morton , Pekka Enberg , Paul Menage , Randy Dunlap , linux-kernel@vger.kernel.org Subject: Re: [patch -mm] cpusets: add memory_slab_hardwall flag In-Reply-To: <1236719283.3205.24.camel@calx> Message-ID: References: <20090309123011.A228.A69D9226@jp.fujitsu.com> <20090309181756.CF66.A69D9226@jp.fujitsu.com> <1236719283.3205.24.camel@calx> User-Agent: Alpine 1.10 (DEB 962 2008-03-14) 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: 1147 Lines: 25 On Tue, 10 Mar 2009, Matt Mackall wrote: > > > Yes, and that's why we require the cpuset hardwall on a configurable > > > per-cpuset basis. If a cpuset has set this option for its workload, then > > > it is demanding object allocations from local memory. Other cpusets that > > > do not have memory_slab_hardwall set can still allocate from any cpu slab > > > or partial slab, including those allocated for the hardwall cpuset. > > > > You cannot hardwall something that is used in a shared way by processes in > > multiple cpusets. > > He can enforce that every allocation made when a given task is current > conforms. His patch demonstrates that. Of course. But that may just be a subset of the data used by a task. If an inode, dentry and so on was already allocated in the context of another process then the locality of that allocation will not be changed. The hardwall will have no effect. -- 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/