linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Will Schmidt <will_schmidt@vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Jon Tollefson <kniht@linux.vnet.ibm.com>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Use 1TB segments
Date: Tue, 2 Oct 2007 21:11:05 -0500	[thread overview]
Message-ID: <20071003021105.GA6553@lixom.net> (raw)
In-Reply-To: <1191350274.18159.279.camel@farscape.rchland.ibm.com>

Hi,

On Tue, Oct 02, 2007 at 01:37:54PM -0500, Will Schmidt wrote:
> [RFC v2] 1TB Segment size support
> 
> From:  <>
> 
> 1TB Segment size support
> 
> This makes the kernel use 1TB segments for all kernel mappings and for
> user addresses of 1TB and above, on machines which support them
> (currently POWER5+ and POWER6).

PA6T supports them as well :)

>                                 We don't currently use 1TB segments
> for user addresses < 1T, since that would effectively prevent 32-bit
> processes from using huge pages unless we also had a way to revert to
> using 256MB segments.

Wouldn't it be possible to stick with 1TB segments for the low range
for 64-bit processes as well, and have them allocate their hugepages
at >1TB?


-Olof

  reply	other threads:[~2007-10-03  2:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  2:04 [PATCH] Use 1TB segments Paul Mackerras
2007-08-02 20:41 ` Will Schmidt
2007-08-02 22:37   ` Benjamin Herrenschmidt
2007-08-02 23:56     ` Will Schmidt
2007-08-03  2:53   ` David Gibson
2007-08-06 22:23 ` Jon Tollefson
2007-08-10  3:53 ` Michael Neuling
2007-10-02 18:37 ` Will Schmidt
2007-10-03  2:11   ` Olof Johansson [this message]
2007-10-03  3:07     ` Paul Mackerras
2007-10-03  3:27       ` Olof Johansson
2007-10-03  3:13   ` Paul Mackerras
2007-10-03 14:22     ` Will Schmidt

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=20071003021105.GA6553@lixom.net \
    --to=olof@lixom.net \
    --cc=kniht@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=will_schmidt@vnet.ibm.com \
    /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).