From: Paul Mackerras <paulus@samba.org>
To: Liu Ping Fan <kernelfans@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc: mm: change pgtable index size for 64K page
Date: Fri, 22 Nov 2013 09:11:50 +1100 [thread overview]
Message-ID: <20131121221150.GB26359@iris.ozlabs.ibm.com> (raw)
In-Reply-To: <1385000275-5988-2-git-send-email-pingfank@linux.vnet.ibm.com>
On Thu, Nov 21, 2013 at 10:17:55AM +0800, Liu Ping Fan wrote:
> For 64K page, we waste half of the pte_t page. With this patch, after
> changing PGD_INDEX_SIZE from 12 to 11, PTE_INDEX_SIZE from 8 to 9,
> we can improve the usage of pte_t page and shrink the continuous phys
> size for pgd_t.
>
> Signed-off-by: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
> ---
> arch/powerpc/include/asm/pgtable-ppc64-64k.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/pgtable-ppc64-64k.h b/arch/powerpc/include/asm/pgtable-ppc64-64k.h
> index a56b82f..f6955ff 100644
> --- a/arch/powerpc/include/asm/pgtable-ppc64-64k.h
> +++ b/arch/powerpc/include/asm/pgtable-ppc64-64k.h
> @@ -4,10 +4,10 @@
> #include <asm-generic/pgtable-nopud.h>
>
>
> -#define PTE_INDEX_SIZE 8
> +#define PTE_INDEX_SIZE 9
> #define PMD_INDEX_SIZE 10
> #define PUD_INDEX_SIZE 0
> -#define PGD_INDEX_SIZE 12
> +#define PGD_INDEX_SIZE 11
Nack. Those definitions are the way they are in order to have the PMD
map 16MB, which is our large page size, so that transparent huge pages
work.
Paul.
next prev parent reply other threads:[~2013-11-21 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 2:17 [PATCH 1/2] powerpc: mm: use macro PGTABLE_EADDR_SIZE instead of digital Liu Ping Fan
2013-11-21 2:17 ` [PATCH 2/2] powerpc: mm: change pgtable index size for 64K page Liu Ping Fan
2013-11-21 22:11 ` Paul Mackerras [this message]
2013-11-21 23:46 ` Benjamin Herrenschmidt
2013-11-22 2:06 ` Michael Ellerman
2014-04-30 5:30 ` [PATCH 1/2] powerpc: mm: use macro PGTABLE_EADDR_SIZE instead of digital Aneesh Kumar K.V
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=20131121221150.GB26359@iris.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=kernelfans@gmail.com \
--cc=linuxppc-dev@lists.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).