[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20220507140508.38c9e211eae4715134f9fa31@linux-foundation.org>
Date: Sat, 7 May 2022 14:05:08 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Muchun Song <songmuchun@...edance.com>
Cc: Mike Kravetz <mike.kravetz@...cle.com>, corbet@....net,
mcgrof@...nel.org, keescook@...omium.org, yzaikin@...gle.com,
osalvador@...e.de, david@...hat.com, masahiroy@...nel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, duanxiongchun@...edance.com, smuchun@...il.com
Subject: Re: [PATCH v9 2/4] mm: memory_hotplug: override memmap_on_memory
when hugetlb_free_vmemmap=on
On Wed, 4 May 2022 11:37:43 +0800 Muchun Song <songmuchun@...edance.com> wrote:
> > Freeing HugeTLB vmemmap pages is not compatible with allocating memmap on
> > hot added memory. If "hugetlb_free_vmemmap=on" and
> > memory_hotplug.memmap_on_memory" are both passed on the kernel command line,
> > freeing hugetlb pages takes precedence. However, the global variable
> > memmap_on_memory will still be set to 1, even though we will not try to
> > allocate memmap on hot added memory.
> >
> > Not sure if that is more clear or not.
> >
>
> Clearer than mine.
I updated, thanks.
Powered by blists - more mailing lists