Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030787AbXAZUiD (ORCPT ); Fri, 26 Jan 2007 15:38:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030793AbXAZUiC (ORCPT ); Fri, 26 Jan 2007 15:38:02 -0500 Received: from calculon.skynet.ie ([193.1.99.88]:44312 "EHLO calculon.skynet.ie" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030787AbXAZUiB (ORCPT ); Fri, 26 Jan 2007 15:38:01 -0500 Date: Fri, 26 Jan 2007 20:37:59 +0000 (GMT) From: Mel Gorman X-X-Sender: mel@skynet.skynet.ie To: Christoph Lameter Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 3/8] Allow huge page allocations to use GFP_HIGH_MOVABLE In-Reply-To: Message-ID: References: <20070125234458.28809.5412.sendpatchset@skynet.skynet.ie> <20070125234558.28809.21103.sendpatchset@skynet.skynet.ie> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 901 Lines: 24 On Fri, 26 Jan 2007, Christoph Lameter wrote: > On Fri, 26 Jan 2007, Mel Gorman wrote: > >> The zone-based approach does nothing to help jumbo frame allocations. It only >> helps hugepage allocations at runtime and potentially memory hot-remove. > > Sounds like the max order based approach is better in many ways. I agree but too many people are not pleased with the main allocator path being affected and wanted to see zones, so here we are :) > Also avoids modifications to vmstat.c/.h ;-) > -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab - 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/