From: David Woodhouse <dwmw2@infradead.org>
To: Andrew Morton <akpm@osdl.org>
Cc: dhowells <dhowells@redhat.com>,
hch@infradead.org, torvalds@osdl.org, davidm@snapgear.com,
linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH] VM routine fixes
Date: Thu, 11 Nov 2004 01:17:13 +0000 [thread overview]
Message-ID: <1100135833.4631.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20041110110145.3751ae17.akpm@osdl.org>
On Wed, 2004-11-10 at 11:01 -0800, Andrew Morton wrote:
> Why _does_ !CONFIG_MMU futz around with page counts in such weird ways
> anyway? Why does it have requirements for higher-order pages which differ
> from !CONFIG_MMU?
Because in the absence of an MMU, an mmap of a large region (like an
executable) has to be satisfied by a large enough allocation followed by
a read.
> If someone could explain the reasoning behind the current code, and the FRV
> enhancements then perhaps we could work something out.
I think these parts aren't FRV-specific; they're the fixes required to
do proper shared readable mmap with !CONFIG_MMU. That was a prerequisite
for the ELF-FDPIC executable format, which allows real shared libraries
on uClinux.
--
dwmw2
next prev parent reply other threads:[~2004-11-11 1:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 14:32 dhowells
2004-11-09 12:55 ` Christoph Hellwig
2004-11-09 13:53 ` David Howells
2004-11-09 14:01 ` Christoph Hellwig
2004-11-10 13:37 ` David Howells
2004-11-10 19:01 ` Andrew Morton
2004-11-11 1:17 ` David Woodhouse [this message]
2004-11-11 2:26 ` Andrew Morton
2004-11-11 11:29 ` David Howells
2004-11-11 11:43 ` Andrew Morton
2004-11-11 12:03 ` David Howells
2004-11-11 22:31 ` Andrew Morton
2004-11-12 10:33 ` David Howells
2004-11-12 10:38 ` Andrew Morton
2004-11-12 11:05 ` David Howells
2004-11-14 5:07 ` Linus Torvalds
2004-11-15 13:14 ` David Howells
2004-11-15 15:35 ` Linus Torvalds
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=1100135833.4631.10.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--cc=davidm@snapgear.com \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=uclinux-dev@uclinux.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
Powered by JetHome