From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with ESMTP id 0542B6B004D for ; Tue, 18 Aug 2009 12:53:33 -0400 (EDT) Date: Tue, 18 Aug 2009 17:53:41 +0100 From: Mel Gorman Subject: Re: [RFC PATCH 0/3] Reduce searching in the page allocator fast-path Message-ID: <20090818165340.GB13435@csn.ul.ie> References: <1250594162-17322-1-git-send-email-mel@csn.ul.ie> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: Sender: owner-linux-mm@kvack.org To: Christoph Lameter Cc: Linux Memory Management List , Nick Piggin , Linux Kernel Mailing List List-ID: On Tue, Aug 18, 2009 at 10:22:01AM -0400, Christoph Lameter wrote: > > This could be combined with the per cpu ops patch that makes the page > allocator use alloc_percpu for its per cpu data needs. That in turn would > allow the use of per cpu atomics in the hot paths, maybe we can > get to a point where we can drop the irq disable there. > It would appear that getting rid of IRQ disabling and using per-cpu-atomics would be a problem independent of searching the free lists. Either would be good, both would be better or am I missing something that makes them mutually exclusive? Can you point me to which patchset you are talking about specifically that uses per-cpu atomics in the hot path? There are a lot of per-cpu patches related to you that have been posted in the last few months and I'm not sure what any of their merge status' is. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org