From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ollie Wild <aaw@google.com>
Cc: linux-kernel@vger.kernel.org,
parisc-linux@lists.parisc-linux.org, linux-mm@kvack.org,
linux-arch@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 3/4] mm: move_page_tables{,_up}
Date: Wed, 06 Jun 2007 21:12:14 +0200 [thread overview]
Message-ID: <1181157134.5676.28.camel@lappy> (raw)
In-Reply-To: <65dd6fd50706061206y558e7f90t3740424fae7bdc9c@mail.gmail.com>
On Wed, 2007-06-06 at 12:06 -0700, Ollie Wild wrote:
> On 6/5/07, Peter Zijlstra <a.p.zijlstra@chello.nl> 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.
PA-RISC will still need it, right?
On the defrag thingy, I talked with Mel today, and neither of us can see
a usefull application of these functions to his defrag work.
--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-06-06 19:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 15:05 [PATCH 0/4] no MAX_ARG_PAGES Peter Zijlstra
2007-06-05 15:05 ` [PATCH 1/4] arch: personality independent stack top Peter Zijlstra
2007-06-05 15:05 ` [PATCH 2/4] audit: rework execve audit Peter Zijlstra
2007-06-05 23:39 ` Andrew Morton
2007-06-06 5:52 ` Peter Zijlstra
2007-06-05 15:05 ` [PATCH 3/4] mm: move_page_tables{,_up} Peter Zijlstra
2007-06-05 19:46 ` Christoph Lameter
2007-06-05 23:39 ` Andrew Morton
2007-06-06 19:06 ` Ollie Wild
2007-06-06 19:12 ` Peter Zijlstra [this message]
2007-06-06 19:50 ` Ollie Wild
2007-06-06 19:53 ` Peter Zijlstra
2007-06-05 15:05 ` [PATCH 4/4] mm: variable length argument support Peter Zijlstra, Ollie Wild
2007-06-05 23:39 ` Andrew Morton
2007-06-06 0:48 ` Ollie Wild
2007-06-06 6:02 ` Peter Zijlstra
2007-06-06 8:36 ` Andrew Morton
2007-06-06 8:44 ` Paul Mundt
2007-06-06 8:54 ` Peter Zijlstra
2007-06-06 9:06 ` Andrew Morton
2007-06-06 9:12 ` Peter Zijlstra
2007-06-06 14:40 ` [parisc-linux] " Grant Grundler
2007-06-06 9:34 ` Peter Zijlstra
2007-06-06 9:44 ` Paul Mundt
2007-06-06 9:47 ` Peter Zijlstra
2007-06-06 9:53 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1181157134.5676.28.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=aaw@google.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox