From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: [RFC PATCH 0/7] Remove 4k subpage tracking with hash 64K config
Date: Wed, 21 Oct 2015 01:42:26 +0530 [thread overview]
Message-ID: <1445371953-9627-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com> (raw)
Hi,
This patch series is on top of the series posted at
https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-October/135299.html
"[PATCH V4 00/31] powerpc/mm: Update page table format for book3s 64". In this
series we remove 4k subpage tracking with 64K config. Instead we do a hash
table lookup to get the slot information of 4k hash ptes. This also allow us
to remove real_pte_t. Side effect of the change is that a specific 4k slot
lookup can result in multiple H_READ hcalls. But that should only impact
when we are using 4K subpages which should be rare.
NOTE: I only tested this on systemsim. Wanted to get this out to get early
feedback.
Aneesh Kumar K.V (7):
powerpc/mm: Don't hardcode page table size
powerpc/mm: Don't hardcode the hash pte slot shift
powerpc/nohash: Update 64K nohash config to have 32 pte fragement
powerpc/mm: Don't track 4k subpage information with 64k linux page
size
powerpc/mm: update frag size
powerpc/mm: Update pte_iterate_hashed_subpaes args
powerpc/mm: getrid of real_pte_t
arch/powerpc/include/asm/book3s/64/hash-64k.h | 75 +++++++++---------------
arch/powerpc/include/asm/book3s/64/pgtable.h | 25 +++-----
arch/powerpc/include/asm/machdep.h | 2 +
arch/powerpc/include/asm/nohash/64/pgtable-64k.h | 21 +++++--
arch/powerpc/include/asm/nohash/64/pgtable.h | 24 +++-----
arch/powerpc/include/asm/page.h | 15 -----
arch/powerpc/include/asm/pgalloc-64.h | 10 ----
arch/powerpc/include/asm/tlbflush.h | 4 +-
arch/powerpc/mm/hash64_64k.c | 67 +++++++++++++--------
arch/powerpc/mm/hash_native_64.c | 35 ++++++++---
arch/powerpc/mm/hash_utils_64.c | 13 ++--
arch/powerpc/mm/init_64.c | 7 +--
arch/powerpc/mm/pgtable_64.c | 6 +-
arch/powerpc/mm/tlb_hash64.c | 15 +++--
arch/powerpc/platforms/pseries/lpar.c | 23 ++++++--
15 files changed, 175 insertions(+), 167 deletions(-)
--
2.5.0
next reply other threads:[~2015-10-20 20:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 20:12 Aneesh Kumar K.V [this message]
2015-10-20 20:12 ` [RFC PATCH 1/7] powerpc/mm: Don't hardcode page table size Aneesh Kumar K.V
2015-10-20 20:12 ` [RFC PATCH 2/7] powerpc/mm: Don't hardcode the hash pte slot shift Aneesh Kumar K.V
2015-10-20 20:12 ` [RFC PATCH 3/7] powerpc/nohash: Update 64K nohash config to have 32 pte fragement Aneesh Kumar K.V
2015-10-20 20:12 ` [RFC PATCH 4/7] powerpc/mm: Don't track 4k subpage information with 64k linux page size Aneesh Kumar K.V
2015-10-20 20:12 ` [RFC PATCH 5/7] powerpc/mm: update frag size Aneesh Kumar K.V
2015-10-20 20:12 ` [RFC PATCH 6/7] powerpc/mm: Update pte_iterate_hashed_subpaes args Aneesh Kumar K.V
2015-10-20 20:12 ` [RFC PATCH 7/7] powerpc/mm: getrid of real_pte_t Aneesh Kumar K.V
2015-10-29 3:00 ` [RFC PATCH 0/7] Remove 4k subpage tracking with hash 64K config Paul Mackerras
2015-11-03 5:08 ` Aneesh Kumar K.V
2015-11-03 5:30 ` Benjamin Herrenschmidt
2015-11-03 9:18 ` Michael Ellerman
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=1445371953-9627-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).