From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from spaceape7.eur.corp.google.com (spaceape7.eur.corp.google.com [172.28.16.141]) by smtp-out.google.com with ESMTP id l56J69Ya000459 for ; Wed, 6 Jun 2007 20:06:09 +0100 Received: from py-out-1112.google.com (pybu77.prod.google.com [10.34.97.77]) by spaceape7.eur.corp.google.com with ESMTP id l56J4GHM030317 for ; Wed, 6 Jun 2007 20:06:05 +0100 Received: by py-out-1112.google.com with SMTP id u77so440143pyb for ; Wed, 06 Jun 2007 12:06:05 -0700 (PDT) Message-ID: <65dd6fd50706061206y558e7f90t3740424fae7bdc9c@mail.gmail.com> Date: Wed, 6 Jun 2007 12:06:05 -0700 From: "Ollie Wild" Subject: Re: [PATCH 3/4] mm: move_page_tables{,_up} In-Reply-To: <20070605151203.738393000@chello.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070605150523.786600000@chello.nl> <20070605151203.738393000@chello.nl> Sender: owner-linux-mm@kvack.org Return-Path: To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, Andrew Morton , Ingo Molnar , Andi Kleen List-ID: On 6/5/07, Peter Zijlstra wrote: > Provide functions for moving page tables upwards. Now that we're initializing the temporary stack location to STACK_TOP_MAX, do we still need move_page_tables_up() for variable length argument support? I originally added it into shift_arg_pages() to support 32-bit apps exec'ing 64-bit apps when we were using TASK_SIZE as our temporary location. Maybe we should decouple this patch from the others and submit it as an enhancement to support memory defragmentation. Ollie -- 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