From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jimi Xenidis <jimix@watson.ibm.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
"cbe-oss-dev@ozlabs.org" <cbe-oss-dev@ozlabs.org>,
"Hollis R. Blanchard" <hollisb@us.ibm.com>
Subject: Re: [PATCH] powerpc: Introduce address space "slices"
Date: Tue, 20 Feb 2007 06:42:37 +1100 [thread overview]
Message-ID: <1171914157.18571.38.camel@localhost.localdomain> (raw)
In-Reply-To: <934E7F45-153D-4558-A774-FA5B6AB69E3C@watson.ibm.com>
On Mon, 2007-02-19 at 08:23 -0500, Jimi Xenidis wrote:
> Hey Ben,
> is it your intention to eventually support "/memory@x/
> ibm,expected#pages" and will these rules effect the kernel's linear map?
> My interest is with hypervisors that would like to restrict certain
> LMBs to 4k so we can do our nasty memory tricks, but still have most
> of the memory use large pages.
The slices mecanism is strictly a mecanism for dealing with segment
constraints on userland VMA layout, so I don't think it will have any
impact either negative or positive on you.
Limiting physical memory to different page sizes is a whole different
problem that I haven't though about (damn, that would be hard).
Ben.
next prev parent reply other threads:[~2007-02-19 19:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 6:43 [PATCH] powerpc: Introduce address space "slices" Benjamin Herrenschmidt
2007-02-19 13:23 ` Jimi Xenidis
2007-02-19 19:42 ` Benjamin Herrenschmidt [this message]
2007-02-19 19:57 ` Jimi Xenidis
2007-02-19 15:33 ` Olof Johansson
2007-02-19 16:49 ` [Cbe-oss-dev] " Arnd Bergmann
2007-02-19 19:39 ` Benjamin Herrenschmidt
2007-02-19 20:15 ` Olof Johansson
2007-02-19 18:54 ` Adam Litke
2007-02-19 19:40 ` Benjamin Herrenschmidt
2007-02-19 20:35 ` Adam Litke
2007-02-19 20:47 ` Benjamin Herrenschmidt
2007-02-19 21:15 ` Adam Litke
2007-02-20 19:45 ` Adam Litke
2007-02-20 19:51 ` Benjamin Herrenschmidt
2007-02-20 20:07 ` Adam Litke
2007-02-21 0:29 ` David Gibson
2007-02-21 0:40 ` 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=1171914157.18571.38.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=cbe-oss-dev@ozlabs.org \
--cc=hollisb@us.ibm.com \
--cc=jimix@watson.ibm.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).