public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
	Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] ppc64: 64K pages support
Date: Wed, 02 Nov 2005 18:23:18 +1100	[thread overview]
Message-ID: <1130916198.20136.17.camel@gaston> (raw)
In-Reply-To: <1130915220.20136.14.camel@gaston>

On Wed, 2005-11-02 at 18:07 +1100, Benjamin Herrenschmidt wrote:
> It took a while, but finally, here is the 64K pages support patch for
> ppc64. This patch adds a new CONFIG_PPC_64K_PAGES which, when enabled,
> changes the kernel base page size to 64K. The resulting kernel still
> boots on any hardware. On current machines with 4K pages support only,
> the kernel will maintain 16 "subpages" for each 64K page
> transparently.
> 
> Note that while real 64K capable HW has been tested, the current patch
> will not enable it yet as such hardware is not released yet, and I'm
> still verifying with the firmware architects the proper to get the
> information from the newer hypervisors.
> 
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

Oh, and since the mailing lists are probably filtering this out due to
the patch size, here's an URL where you can find it too:

http://gate.crashing.org/~benh/ppc64-64k-pages.diff

Ben.



       reply	other threads:[~2005-11-02  7:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1130915220.20136.14.camel@gaston>
2005-11-02  7:23 ` Benjamin Herrenschmidt [this message]
2005-11-03  3:16   ` [PATCH] ppc64: 64K pages support Paul Mackerras
2005-11-03  5:26     ` ppc64: Fix bug in SLB miss handler for hugepages David Gibson
2005-11-05  0:38   ` [PATCH] ppc64: 64K pages support Christoph Hellwig
2005-11-05  0:44     ` Benjamin Herrenschmidt
2005-11-05  6:37       ` Dave Airlie
2005-11-09 17:21   ` Christoph Hellwig
2005-11-09 20:17     ` Mike Kravetz
2005-11-09 20:32       ` Benjamin Herrenschmidt
2005-11-09 21:59         ` Badari Pulavarty
2005-11-09 22:01           ` Benjamin Herrenschmidt
2005-11-09 22:07             ` Badari Pulavarty
2005-11-16 23:08               ` Olaf Hering
2005-11-16 23:16                 ` Badari Pulavarty
2005-11-16 23:27                   ` Olaf Hering
2005-11-17  1:32                     ` Andreas Schwab
     [not found]                   ` <ac0de0c00511161557o379fbc71le6d5c5e2ff9a314b@mail.gmail.com>
2005-11-17  0:33                     ` Badari Pulavarty
2005-11-09 20:36     ` Benjamin Herrenschmidt
2005-11-09 22:15     ` Paul Mackerras
2005-11-09 23:42     ` 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=1130916198.20136.17.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@ozlabs.org \
    --cc=torvalds@osdl.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