From: David Hildenbrand <david@redhat.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: Wei Xu <weixugc@google.com>,
Sourav Panda <souravpanda@google.com>,
corbet@lwn.net, gregkh@linuxfoundation.org, rafael@kernel.org,
akpm@linux-foundation.org, mike.kravetz@oracle.com,
muchun.song@linux.dev, rppt@kernel.org, rdunlap@infradead.org,
chenlinxuan@uniontech.com, yang.yang29@zte.com.cn,
tomas.mudrunka@gmail.com, bhelgaas@google.com,
ivan@cloudflare.com, yosryahmed@google.com, hannes@cmpxchg.org,
shakeelb@google.com, kirill.shutemov@linux.intel.com,
wangkefeng.wang@huawei.com, adobriyan@gmail.com, vbabka@suse.cz,
Liam.Howlett@oracle.com, surenb@google.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-mm@kvack.org,
willy@infradead.org, Greg Thelen <gthelen@google.com>
Subject: Re: [PATCH v5 1/1] mm: report per-page metadata information
Date: Thu, 2 Nov 2023 16:53:04 +0100 [thread overview]
Message-ID: <025ef794-91a9-4f0c-9eb6-b0a4856fa10a@redhat.com> (raw)
In-Reply-To: <CA+CK2bDo6an35R8Nu-d99pbNQMEAw_t0yUm0Q+mJNwOJ1EdqQg@mail.gmail.com>
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
next prev parent reply other threads:[~2023-11-02 15:53 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 23:08 [PATCH v5 0/1] mm: report per-page metadata information Sourav Panda
2023-11-01 23:08 ` [PATCH v5 1/1] " Sourav Panda
2023-11-01 23:40 ` Wei Xu
2023-11-02 2:57 ` Pasha Tatashin
2023-11-02 15:43 ` Wei Xu
2023-11-02 15:47 ` David Hildenbrand
2023-11-02 15:50 ` Pasha Tatashin
2023-11-02 15:53 ` David Hildenbrand [this message]
2023-11-02 16:02 ` Pasha Tatashin
2023-11-02 16:09 ` David Hildenbrand
2023-11-02 16:43 ` Pasha Tatashin
2023-11-02 16:58 ` David Hildenbrand
2023-11-02 17:11 ` Pasha Tatashin
2023-11-02 18:06 ` Wei Xu
2023-11-02 18:33 ` Pasha Tatashin
2023-11-02 20:22 ` Wei Xu
2023-11-03 1:06 ` Pasha Tatashin
2023-11-03 4:27 ` Wei Xu
2023-11-03 15:18 ` Pasha Tatashin
2023-11-02 20:28 ` David Hildenbrand
2023-11-02 5:42 ` Greg KH
2023-11-02 14:24 ` Pasha Tatashin
2023-11-02 14:28 ` Greg KH
2023-11-02 15:11 ` Pasha Tatashin
2023-11-02 10:19 ` Alexey Dobriyan
2023-11-17 2:42 ` kernel test robot
2023-11-20 21:47 ` Sourav Panda
2023-11-02 18:13 ` [PATCH v5 0/1] " Matthew Wilcox
2023-11-03 4:53 ` Sourav Panda
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=025ef794-91a9-4f0c-9eb6-b0a4856fa10a@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhelgaas@google.com \
--cc=chenlinxuan@uniontech.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=ivan@cloudflare.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=souravpanda@google.com \
--cc=surenb@google.com \
--cc=tomas.mudrunka@gmail.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=yang.yang29@zte.com.cn \
--cc=yosryahmed@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.