[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YqetbhnddbAzTnHJ@monkey>
Date: Mon, 13 Jun 2022 14:34:38 -0700
From: Mike Kravetz <mike.kravetz@...cle.com>
To: Muchun Song <songmuchun@...edance.com>
Cc: david@...hat.com, akpm@...ux-foundation.org, corbet@....net,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [PATCH 4/6] mm: hugetlb_vmemmap: move vmemmap code related to
HugeTLB to hugetlb_vmemmap.c
On Mon, Jun 13, 2022 at 02:35:10PM +0800”, Muchun Song wrote:
> When I first introduced vmemmap manipulation functions related to HugeTLB,
> I thought those functions may be reused by other modules (e.g. using
> similar approach to optimize vmemmap pages, unfortunately, the DAX used the
> same approach but does not use those functions). After two years, we didn't
> see any other users. So move those functions to hugetlb_vmemmap.c.
>
> Signed-off-by: Muchun Song <songmuchun@...edance.com>
> ---
> include/linux/mm.h | 7 -
> mm/hugetlb_vmemmap.c | 391 ++++++++++++++++++++++++++++++++++++++++++++++++++-
> mm/sparse-vmemmap.c | 391 ---------------------------------------------------
> 3 files changed, 390 insertions(+), 399 deletions(-)
Code movement without any functional change.
Reviewed-by: Mike Kravetz <mike.kravetz@...cle.com>
--
Mike Kravetz
Powered by blists - more mailing lists