[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <025ef794-91a9-4f0c-9eb6-b0a4856fa10a@redhat.com>
Date: Thu, 2 Nov 2023 16:53:04 +0100
From: David Hildenbrand <david@...hat.com>
To: Pasha Tatashin <pasha.tatashin@...een.com>
Cc: Wei Xu <weixugc@...gle.com>, Sourav Panda <souravpanda@...gle.com>,
corbet@....net, gregkh@...uxfoundation.org, rafael@...nel.org,
akpm@...ux-foundation.org, mike.kravetz@...cle.com,
muchun.song@...ux.dev, rppt@...nel.org, rdunlap@...radead.org,
chenlinxuan@...ontech.com, yang.yang29@....com.cn,
tomas.mudrunka@...il.com, bhelgaas@...gle.com, ivan@...udflare.com,
yosryahmed@...gle.com, hannes@...xchg.org, shakeelb@...gle.com,
kirill.shutemov@...ux.intel.com, wangkefeng.wang@...wei.com,
adobriyan@...il.com, vbabka@...e.cz, Liam.Howlett@...cle.com,
surenb@...gle.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-doc@...r.kernel.org,
linux-mm@...ck.org, willy@...radead.org,
Greg Thelen <gthelen@...gle.com>
Subject: Re: [PATCH v5 1/1] mm: report per-page metadata information
On 02.11.23 16:50, Pasha Tatashin wrote:
>>> Adding reserved memory to MemTotal is a cleaner approach IMO as well.
>>> But it changes the semantics of MemTotal, which may have compatibility
>>> issues.
>>
>> I object.
>
> Could you please elaborate what you object (and why): you object that
> it will have compatibility issues, or you object to include memblock
> reserves into MemTotal?
Sorry, I object to changing the semantics of MemTotal. MemTotal is
traditionally the memory managed by the buddy, not all memory in the
system. I know people/scripts that are relying on that [although it's
been source of confusion a couple of times].
--
Cheers,
David / dhildenb
Powered by blists - more mailing lists