From: Zach O'Keefe <zokeefe@google.com>
To: Yang Shi <shy828301@gmail.com>
Cc: vbabka@suse.cz, kirill.shutemov@linux.intel.com,
willy@infradead.org, linmiaohe@huawei.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [mm-unstable v5 PATCH 0/7] Cleanup transhuge_xxx helpers
Date: Thu, 16 Jun 2022 16:08:39 -0700 [thread overview]
Message-ID: <Yqu392qcUSp1imEi@google.com> (raw)
In-Reply-To: <20220616174840.1202070-1-shy828301@gmail.com>
On 16 Jun 10:48, Yang Shi wrote:
>
> v5: * Removed transparent_hugepage_active() for !THP, per Zach.
> Patch 4/7 and 5/7 were updated accordingly.
> * Collected review tags.
> v4: * Consolidated the transhuge_vma_size_ok() helper proposed in the
> earlier versions into transhuge_vma_suitable(), per Zach.
> * Fixed the regression introduced by patch 3/7, per Zach and Miaohe.
> * Reworded the comment for transhuge_vma_suitable(), per Zach.
> * Removed khugepaged_enter() per Miaohe.
> * More comments for hugepage_vma_check(), per Zach.
> * Squashed patch 4/7 (mm: khugepaged: use transhuge_vma_suitable replace open-code)
> in the earlier version into patch 2/7 of this version.
> * Minor correction to the doc about THPeligible (patch 7/7), so the
> total number of patches is kept 7.
> v3: * Fixed the comment from Willy
> v2: * Rebased to the latest mm-unstable
> * Fixed potential regression for smaps's THPeligible
>
> This series is the follow-up of the discussion about cleaning up transhuge_xxx
> helpers at https://lore.kernel.org/linux-mm/627a71f8-e879-69a5-ceb3-fc8d29d2f7f1@suse.cz/.
>
> THP has a bunch of helpers that do VMA sanity check for different paths, they
> do the similar checks for the most callsites and have a lot duplicate codes.
> And it is confusing what helpers should be used at what conditions.
>
> This series reorganized and cleaned up the code so that we could consolidate
> all the checks into hugepage_vma_check().
>
> The transhuge_vma_enabled(), transparent_hugepage_active() and
> __transparent_hugepage_enabled() are killed by this series.
>
>
> Yang Shi (7):
> mm: khugepaged: check THP flag in hugepage_vma_check()
> mm: thp: consolidate vma size check to transhuge_vma_suitable
> mm: khugepaged: better comments for anon vma check in hugepage_vma_revalidate
> mm: thp: kill transparent_hugepage_active()
> mm: thp: kill __transhuge_page_enabled()
> mm: khugepaged: reorg some khugepaged helpers
> doc: proc: fix the description to THPeligible
>
> Documentation/filesystems/proc.rst | 4 ++-
> fs/proc/task_mmu.c | 2 +-
> include/linux/huge_mm.h | 80 +++++++++++++++++++----------------------------------------
> include/linux/khugepaged.h | 30 ----------------------
> mm/huge_memory.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++--------
> mm/khugepaged.c | 84 +++++++++++++++++++-------------------------------------------
> mm/memory.c | 7 ++++--
> 7 files changed, 130 insertions(+), 158 deletions(-)
>
Series LGTM. Thanks for these cleanups, Yang!
Best,
Zach
next prev parent reply other threads:[~2022-06-16 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 17:48 Yang Shi
2022-06-16 17:48 ` [v5 PATCH 1/7] mm: khugepaged: check THP flag in hugepage_vma_check() Yang Shi
2022-06-16 17:48 ` [v5 PATCH 2/7] mm: thp: consolidate vma size check to transhuge_vma_suitable Yang Shi
2022-06-16 17:48 ` [v5 PATCH 3/7] mm: khugepaged: better comments for anon vma check in hugepage_vma_revalidate Yang Shi
2022-06-16 17:48 ` [v5 PATCH 4/7] mm: thp: kill transparent_hugepage_active() Yang Shi
2022-06-21 18:58 ` Zach O'Keefe
2022-06-22 0:54 ` Andrew Morton
2022-06-22 17:52 ` Zach O'Keefe
2022-06-16 17:48 ` [v5 PATCH 5/7] mm: thp: kill __transhuge_page_enabled() Yang Shi
2022-06-16 17:48 ` [v5 PATCH 6/7] mm: khugepaged: reorg some khugepaged helpers Yang Shi
2022-06-16 17:48 ` [v5 PATCH 7/7] doc: proc: fix the description to THPeligible Yang Shi
2022-06-16 23:08 ` Zach O'Keefe [this message]
2022-06-17 17:54 ` [mm-unstable v5 PATCH 0/7] Cleanup transhuge_xxx helpers Yang Shi
2022-06-21 21:07 ` Mike Kravetz
2022-06-21 22:43 ` Zach O'Keefe
2022-07-03 23:14 ` Andrew Morton
2022-07-05 19:45 ` Yang Shi
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=Yqu392qcUSp1imEi@google.com \
--to=zokeefe@google.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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