Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758683AbYCYRwM (ORCPT ); Tue, 25 Mar 2008 13:52:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753112AbYCYRv6 (ORCPT ); Tue, 25 Mar 2008 13:51:58 -0400 Received: from one.firstfloor.org ([213.235.205.2]:53507 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751015AbYCYRv6 (ORCPT ); Tue, 25 Mar 2008 13:51:58 -0400 Date: Tue, 25 Mar 2008 18:55:08 +0100 From: Andi Kleen To: Christoph Lameter Cc: Andi Kleen , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [13/14] vcompound: Use vcompound for swap_map Message-ID: <20080325175508.GV2170@one.firstfloor.org> References: <20080321061703.921169367@sgi.com> <20080321061727.269764652@sgi.com> <8763vfixb8.fsf@basil.nowhere.org> <20080325075236.GG2170@one.firstfloor.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 954 Lines: 22 On Tue, Mar 25, 2008 at 10:45:06AM -0700, Christoph Lameter wrote: > On Tue, 25 Mar 2008, Andi Kleen wrote: > > > I liked your idea of fixing compound pages to not rely on order > > better. Ok it is likely more work to implement @) > > Right. It just requires a page allocator rewrite. Not when the trick of getting high order, returning left over pages is used. I meant just updating the GFP_COMPOUND code to always use number of pages instead of order so that it could deal with a compound where the excess pages are already returned. That is not actually that much work (I reimplemented this recently for dma alloc and it's < 20 LOC) Of course the full rewrite would be also great, agreed :) -Andi -- 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/