From: Christoph Hellwig <hch@infradead.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Nick Piggin <npiggin@suse.de>,
akpm@linux-foundation.org, hugh@veritas.com,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [RFC/PATCH] prepare_unmapped_area
Date: Tue, 6 Feb 2007 09:55:09 +0000 [thread overview]
Message-ID: <20070206095509.GA8714@infradead.org> (raw)
In-Reply-To: <1170738296.2620.220.camel@localhost.localdomain>
On Tue, Feb 06, 2007 at 04:04:56PM +1100, Benjamin Herrenschmidt wrote:
> Hi folks !
>
> On Cell, I have, for performance reasons, a need to create special
> mappings of SPEs that use a different page size as the system base page
> size _and_ as the huge page size.
>
> Due to the way the PowerPC memory management works, however, I can only
> have one page size per "segment" of 256MB (or 1T) and thus after such a
> mapping have been created in its own segment, I need to constraint
> -other- vma's to stay out of that area.
>
> This currently cannot be done with the existing arch hooks (because of
> MAP_FIXED). However, the hugetlbfs code already has a hack in there to
> do the exact same thing for huge pages. Thus, this patch moves that hack
> into something that can be overriden by the architectures. This approach
> was choosen as the less ugly of the uglies after discussing with Nick
> Piggin. If somebody has a better idea, I'd love to hear it.
>
> If it doesn't shoke anybody to death, I'd like to see that in -mm (and
> possibly upstream, I don't know yet if my code using that will make
> 2.6.21 or not, but it would be nice if the list of "dependent" patches
> wasn't 3 pages long anyway :-)
Eeek, this is more than fugly. Dave Hansen suggested to move these
checks into a file operation in response to Adam Litke's hugetlb cleanups,
and this patch shows he was right :)
--
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-02-06 9:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200702060405.l1645R7G009668@shell0.pdx.osdl.net>
[not found] ` <1170736938.2620.213.camel@localhost.localdomain>
[not found] ` <20070206044516.GA16647@wotan.suse.de>
2007-02-06 5:04 ` [RFC/PATCH] prepare_unmapped_area Benjamin Herrenschmidt
2007-02-06 5:31 ` Andrew Morton
2007-02-06 5:46 ` Benjamin Herrenschmidt
2007-02-06 5:58 ` Andrew Morton
2007-02-06 6:02 ` Benjamin Herrenschmidt
2007-02-06 6:08 ` Andrew Morton
2007-02-06 6:12 ` Nick Piggin
2007-02-06 6:37 ` Andrew Morton
2007-02-06 6:40 ` Nick Piggin
2007-02-06 6:54 ` Andrew Morton
2007-02-06 9:55 ` Christoph Hellwig [this message]
2007-02-06 10:07 ` Benjamin Herrenschmidt
2007-02-06 10:23 ` Christoph Hellwig
2007-02-06 15:56 ` Adam Litke
2007-02-06 20:12 ` Benjamin Herrenschmidt
2007-02-06 20:52 ` Adam Litke
2007-02-06 21:02 ` Benjamin Herrenschmidt
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=20070206095509.GA8714@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).