From: Andrew Morton <akpm@linux-foundation.org>
To: David Howells <dhowells@redhat.com>
Cc: bryan.wu@analog.com, Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, Hugh Dickins <hugh@veritas.com>
Subject: Re: [PATCH -mm] Revoke core code: fix nommu arch compiling error bug
Date: Mon, 26 Mar 2007 03:50:27 -0800 [thread overview]
Message-ID: <20070326035027.c522cdf5.akpm@linux-foundation.org> (raw)
In-Reply-To: <6017.1174908318@redhat.com>
On Mon, 26 Mar 2007 12:25:18 +0100 David Howells <dhowells@redhat.com> wrote:
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > Offending patch is
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/broken-out/nommu-hide-vm_mm-in-nommu-mode.patch,
> > which seems rather dumb. Or at least, its changelog does a good job of
> > making it look dumb.
>
> vm_mm is always NULL under NOMMU as it currently stands. As far as I know,
> this has been true since the NOMMU mm stuff was first included (I'm not sure
> the VMAs of the first NOMMU mm code *had* a vm_mm). Hugh (I think it was)
> suggested that since this was always NULL, then it should be excised from the
> struct in NOMMU-mode.
>
> The reason is that, at the moment, VMAs are a global *shared* resource in
> NOMMU-mode. Each process has a list of global VMAs that it subscribes to, but
> that's it. This (a) slightly reduces the amount of metadata allocated
> (possibly), and (b) makes sharing of executables and libraries much easier.
whoa. You live and learn. Logical, I guess.
I agree that in that case, we just don't want vm_mm to exist in NOMMU builds - it's
better to fail at compile time.
I'll touch up the changelog for nommu-hide-vm_mm-in-nommu-mode.patch and then
I'll temporarily drop it so the blackfin guys can test their work, I guess.
next prev parent reply other threads:[~2007-03-26 11:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:23 [PATCH -mm] Revoke core code: fix nommu arch compiling error bug Wu, Bryan
2007-03-26 10:37 ` Pekka J Enberg
2007-03-26 10:41 ` Andrew Morton
2007-03-26 11:25 ` David Howells
2007-03-26 11:30 ` Pekka J Enberg
2007-03-26 11:44 ` David Howells
2007-03-26 11:55 ` Pekka J Enberg
2007-03-26 12:22 ` David Howells
2007-03-26 12:37 ` Pekka J Enberg
2007-03-26 13:24 ` David Howells
2007-03-26 20:21 ` Mike Frysinger
2007-03-27 3:29 ` Wu, Bryan
2007-03-27 6:57 ` Pekka J Enberg
2007-03-27 7:20 ` Mike Frysinger
2007-03-27 10:05 ` David Howells
2007-03-27 17:00 ` Mike Frysinger
2007-03-27 19:06 ` David Howells
2007-03-26 13:03 ` Alan Cox
2007-03-26 11:50 ` Andrew Morton [this message]
2007-03-26 11:58 ` David Howells
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=20070326035027.c522cdf5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=dhowells@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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