[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210614181237.5513724624dde3ac930b75d8@linux-foundation.org>
Date: Mon, 14 Jun 2021 18:12:37 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Muchun Song <songmuchun@...edance.com>
Cc: mike.kravetz@...cle.com, osalvador@...e.de, mhocko@...e.com,
song.bao.hua@...ilicon.com, david@...hat.com,
chenhuang5@...wei.com, bodeddub@...zon.com, corbet@....net,
duanxiongchun@...edance.com, fam.zheng@...edance.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: [PATCH v2 0/3] Split huge PMD mapping of vmemmap pages
On Sat, 12 Jun 2021 17:45:52 +0800 Muchun Song <songmuchun@...edance.com> wrote:
> In order to reduce the difficulty of code review in series[1]. We disable
> huge PMD mapping of vmemmap pages when that feature is enabled. In this
> series, we do not disable huge PMD mapping of vmemmap pages anymore. We
> will split huge PMD mapping when needed. When HugeTLB pages are freed from
> the pool we do not attempt coalasce and move back to a PMD mapping because
> it is much more complex.
>
> [1] https://lore.kernel.org/linux-doc/20210510030027.56044-1-songmuchun@bytedance.com/
[1] had a nice [0/n] description but the v2 series lost that. I could
copy/paste the v1 changelogging but I am unsure that it has been
maintained appropriately for the v2 series.
I think I'll pass on this v2 pending additional review input. Please reinstate
the [0/n] overview if/when resending?
Powered by blists - more mailing lists