Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262130AbUKBP5L (ORCPT ); Tue, 2 Nov 2004 10:57:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262135AbUKBP43 (ORCPT ); Tue, 2 Nov 2004 10:56:29 -0500 Received: from jade.aracnet.com ([216.99.193.136]:54725 "EHLO jade.spiritone.com") by vger.kernel.org with ESMTP id S261456AbUKBPtY (ORCPT ); Tue, 2 Nov 2004 10:49:24 -0500 Date: Tue, 02 Nov 2004 07:46:59 -0800 From: "Martin J. Bligh" To: Brent Casavant , linux-kernel@vger.kernel.org, linux-mm@kvack.org cc: hugh@veritas.com, ak@suse.de Subject: Re: [PATCH] Use MPOL_INTERLEAVE for tmpfs files Message-ID: <14340000.1099410418@[10.10.2.4]> In-Reply-To: References: X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1033 Lines: 21 > This patch causes memory allocation for tmpfs files to be distributed > evenly across NUMA machines. In most circumstances today, tmpfs files > will be allocated on the same node as the task writing to the file. > In many cases, particularly when large files are created, or a large > number of files are created by a single task, this leads to a severe > imbalance in free memory amongst nodes. This patch corrects that > situation. Yeah, but it also ruins your locality of reference (in a NUMA sense). Not convinced that's a good idea. You're guaranteeing universally consistent worse-case performance for everyone. And you're only looking at a situation where there's one allocator on the system, and that's imbalanced. You WANT your data to be local. That's the whole idea. M. - 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/