From: David Howells <dhowells@redhat.com>
To: Ollie Wild <aaw@google.com>
Cc: linux-kernel@vger.kernel.org,
parisc-linux@lists.parisc-linux.org,
Linus Torvalds <torvalds@osdl.org>,
Arjan van de Ven <arjan@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
linux-mm@kvack.org, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>,
linux-arch@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: Removing MAX_ARG_PAGES (request for comments/assistance)
Date: Tue, 02 Jan 2007 17:52:14 +0000 [thread overview]
Message-ID: <22336.1167760334@redhat.com> (raw)
In-Reply-To: <65dd6fd50610101705t3db93a72sc0847cd120aa05d3@mail.gmail.com>
Ollie Wild <aaw@google.com> wrote:
> - I haven't tested this on a NOMMU architecture. Could someone please
> validate this?
There are a number of potential problems with NOMMU:
(1) The argument data is copied twice (once into kernel memory and once out
of kernel memory).
(2) The permitted amount of argument data is governed by the stack size of
the program to be exec'd. You should assume that NOMMU stacks cannot
grow.
(3) VMAs on NOMMU are a shared resource.
However, we might be able to extend your idea to improve things. If we work
out the stack size required earlier, we can allocate the VMA and the memory
for the stack *before* we reach the point of no return. We can then fill in
the stack and load up all the parameters *before* releasing the original
executable. That would eliminate one of the copied mentioned in (1). Working
out the stack size earlier may be difficult though, as we may need to load the
interpreter header before we can do so.
Overall, I don't think there should be too many problems with this for NOMMU.
David
--
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>
prev parent reply other threads:[~2007-01-02 17:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 0:05 Ollie Wild
2006-10-11 8:00 ` Arjan van de Ven
2006-10-11 17:13 ` Ollie Wild
2006-10-11 13:14 ` Peter Zijlstra
2006-10-11 21:48 ` Ollie Wild
2006-10-24 17:48 ` Ollie Wild
2006-12-29 20:03 ` [patch] remove MAX_ARG_PAGES Ingo Molnar
2006-12-29 20:49 ` Russell King
2006-12-29 21:23 ` Linus Torvalds
2006-12-29 22:20 ` Ingo Molnar
2006-12-29 21:57 ` Ingo Molnar
2007-01-01 6:51 ` Ollie Wild
2007-01-01 6:58 ` Ollie Wild
2007-01-01 17:28 ` Pavel Machek
2007-01-02 18:18 ` David Howells
2007-01-02 17:52 ` David Howells [this message]
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=22336.1167760334@redhat.com \
--to=dhowells@redhat.com \
--cc=aaw@google.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.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 \
--cc=torvalds@osdl.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