From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org, npiggin@gmail.com,
christophe.leroy@csgroup.eu
Cc: mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
Oscar Salvador <osalvador@suse.de>,
Mike Kravetz <mike.kravetz@oracle.com>,
Dan Williams <dan.j.williams@intel.com>,
Joao Martins <joao.m.martins@oracle.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Muchun Song <muchun.song@linux.dev>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH 00/16] Add support for DAX vmemmap optimization for ppc64
Date: Wed, 14 Jun 2023 09:41:02 +0530 [thread overview]
Message-ID: <87fs6u65ux.fsf@linux.ibm.com> (raw)
In-Reply-To: <20230606045608.55127-1-aneesh.kumar@linux.ibm.com>
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
> This patch series implements changes required to support DAX vmemmap
> optimization for ppc64. The vmemmap optimization is only enabled with radix MMU
> translation and 1GB PUD mapping with 64K page size. The patch series also split
> hugetlb vmemmap optimization as a separate Kconfig variable so that
> architectures can enable DAX vmemmap optimization without enabling hugetlb
> vmemmap optimization. This should enable architectures like arm64 to enable DAX
> vmemmap optimization while they can't enable hugetlb vmemmap optimization. More
> details of the same are in patch "mm/vmemmap optimization: Split hugetlb and
> d
>
> Aneesh Kumar K.V (16):
> powerpc/mm/book3s64: Use pmdp_ptep helper instead of typecasting.
> powerpc/book3s64/mm: mmu_vmemmap_psize is used by radix
> powerpc/book3s64/mm: Fix DirectMap stats in /proc/meminfo
> powerpc/book3s64/mm: Use PAGE_KERNEL instead of opencoding
> powerpc/mm/dax: Fix the condition when checking if altmap vmemap can
> cross-boundary
> mm/hugepage pud: Allow arch-specific helper function to check huge
> page pud support
> mm: Change pudp_huge_get_and_clear_full take vm_area_struct as arg
> mm/vmemmap: Improve vmemmap_can_optimize and allow architectures to
> override
> mm/vmemmap: Allow architectures to override how vmemmap optimization
> works
> mm: Add __HAVE_ARCH_PUD_SAME similar to __HAVE_ARCH_P4D_SAME
> mm/huge pud: Use transparent huge pud helpers only with
> CONFIG_TRANSPARENT_HUGEPAGE
> mm/vmemmap optimization: Split hugetlb and devdax vmemmap optimization
> powerpc/book3s64/mm: Enable transparent pud hugepage
> powerpc/book3s64/vmemmap: Switch radix to use a different vmemmap
> handling function
> powerpc/book3s64/radix: Add support for vmemmap optimization for radix
> powerpc/book3s64/radix: Remove mmu_vmemmap_psize
Gentle ping. Any objections for this series?
-aneesh
next parent reply other threads:[~2023-06-14 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230606045608.55127-1-aneesh.kumar@linux.ibm.com>
2023-06-14 4:11 ` Aneesh Kumar K.V [this message]
[not found] ` <20230606045608.55127-15-aneesh.kumar@linux.ibm.com>
2023-06-14 10:50 ` [PATCH 14/16] powerpc/book3s64/vmemmap: Switch radix to use a different vmemmap handling function Sachin Sant
2023-06-15 2:23 ` Aneesh Kumar K.V
[not found] ` <20230606045608.55127-3-aneesh.kumar@linux.ibm.com>
2023-06-21 4:08 ` [PATCH 02/16] powerpc/book3s64/mm: mmu_vmemmap_psize is used by radix Michael Ellerman
2023-06-21 5:59 ` 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=87fs6u65ux.fsf@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=christophe.leroy@csgroup.eu \
--cc=dan.j.williams@intel.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mike.kravetz@oracle.com \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=npiggin@gmail.com \
--cc=osalvador@suse.de \
--cc=will@kernel.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