From: Alison Schofield <alison.schofield@intel.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-cxl@vger.kernel.org,
cerasuolodomenico@gmail.com, hannes@cmpxchg.org,
j.granados@samsung.com, lizhijian@fujitsu.com,
muchun.song@linux.dev, nphamcs@gmail.com, rientjes@google.com,
rppt@kernel.org, souravpanda@google.com, vbabka@suse.cz,
willy@infradead.org, dan.j.williams@intel.com,
yi.zhang@redhat.com, david@redhat.com, yosryahmed@google.com
Subject: Re: [PATCH v4 0/3] Fixes for memmap accounting
Date: Thu, 8 Aug 2024 15:34:17 -0700 [thread overview]
Message-ID: <ZrVH6Z4CeOAIQ9DS@aschofie-mobl2> (raw)
In-Reply-To: <20240808213437.682006-1-pasha.tatashin@soleen.com>
On Thu, Aug 08, 2024 at 09:34:33PM +0000, Pasha Tatashin wrote:
> Memmap accounting provides us with observability of how much memory is
> used for per-page metadata: i.e. "struct page"'s and "struct page_ext".
> It also provides with information of how much was allocated using
> boot allocator (i.e. not part of MemTotal), and how much was allocated
> using buddy allocated (i.e. part of MemTotal).
>
> This small series fixes a few problems that were discovered with the
> original patch.
Thanks Pasha!
These fixups unblock the unit tests for dax, nvdimm, cxl.
Tested-by: Alison Schofield <alison.schofield@intel.com>
snip
>
prev parent reply other threads:[~2024-08-08 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 21:34 Pasha Tatashin
2024-08-08 21:34 ` [PATCH v4 1/3] mm: don't account memmap on failure Pasha Tatashin
2024-08-08 21:34 ` [PATCH v4 2/3] mm: add system wide stats items category Pasha Tatashin
2024-08-09 7:24 ` David Hildenbrand
2024-08-08 21:34 ` [PATCH v4 3/3] mm: don't account memmap per-node Pasha Tatashin
2024-08-09 7:31 ` David Hildenbrand
2024-08-09 18:09 ` Pasha Tatashin
2024-08-08 22:34 ` Alison Schofield [this message]
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=ZrVH6Z4CeOAIQ9DS@aschofie-mobl2 \
--to=alison.schofield@intel.com \
--cc=akpm@linux-foundation.org \
--cc=cerasuolodomenico@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=j.granados@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhijian@fujitsu.com \
--cc=muchun.song@linux.dev \
--cc=nphamcs@gmail.com \
--cc=pasha.tatashin@soleen.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=souravpanda@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yi.zhang@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox