From: Pasha Tatashin <pasha.tatashin@soleen.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.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, linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Fixes for memmap accounting
Date: Thu, 8 Aug 2024 11:23:30 -0400 [thread overview]
Message-ID: <CA+CK2bCrXqnGPvQP86FpFFfEiCpBSyq_DzdP1deyK8vQ_ZYjzg@mail.gmail.com> (raw)
In-Reply-To: <66b3fc8d39391_2657d52945e@dwillia2-xfh.jf.intel.com.notmuch>
On Wed, Aug 7, 2024 at 7:00 PM Dan Williams <dan.j.williams@intel.com> wrote:
>
> [ add linux-cxl ]
>
> 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.
> >
> > v1: https://lore.kernel.org/all/20240806221454.1971755-1-pasha.tatashin@soleen.com
> > Changes:
> > - Added patch "mm: don't account memmap on failure"
> > - Changed from using nid in hot-remove functions to non-pernode
> > system-wide accounting for memmap data.
> >
> > Pasha Tatashin (3):
> > mm: update the memmap stat before page is freed
> > mm: don't account memmap on failure
> > mm: don't account memmap per node
>
> Hi Pasha,
>
> Thanks for jumping on this debug!
>
> We almost missed these. Can you update your scripts to auto-cc folks on the
> Reported-by line, and optionally include the lists where the report originated
> next time?
Thank you, I will add them.
>
> This is looking good from my tests, you can add:
>
> Tested-by: Dan Williams <dan.j.williams@intel.com>
Thank you for testing
>
> ...but I still want to take a look at some of the implementation choices.
I am about to send v3.
Pasha
parent reply other threads:[~2024-08-08 15:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <66b3fc8d39391_2657d52945e@dwillia2-xfh.jf.intel.com.notmuch>]
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=CA+CK2bCrXqnGPvQP86FpFFfEiCpBSyq_DzdP1deyK8vQ_ZYjzg@mail.gmail.com \
--to=pasha.tatashin@soleen.com \
--cc=akpm@linux-foundation.org \
--cc=cerasuolodomenico@gmail.com \
--cc=dan.j.williams@intel.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=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=souravpanda@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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