From: David Hildenbrand <david@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Michal Hocko <mhocko@kernel.org>,
Dan Williams <dan.j.williams@intel.com>
Subject: [LSF/MM/BPF TOPIC] MM: Mapcount Madness
Date: Mon, 29 Jan 2024 13:05:04 +0100 [thread overview]
Message-ID: <049e4674-44b6-4675-b53b-62e11481a7ce@redhat.com> (raw)
As PTE-mapped large folios become more relevant (mTHP [1]) and there is
the desire to shrink the metadata allocated for such large folios as
well (memdesc [2]), how we track folio mappings gets more relevant. Over
the years, we used folio mapping information to answer various
questions: is this folio mapped by somebody else? do we have to COW on
write fault? how do we adjust memory statistics? ...
Let's talk about ongoing work in the mapcount area, get a common
understanding of what the users of the different mapcounts are and what
the implications of removing some would be: which questions could we
answer differently, which questions would we not be able to answer
precisely anymore, and what would be the implications of such changes?
For example, can we tolerate some imprecise memory statistics? How
expressive is the PSS when large folios are only partially mapped? Would
we need a transition period and glue changes to a new CONFIG_ option? Do
we really have to support THP and friends on 32bit?
[1]
https://patchwork.kernel.org/project/linux-mm/cover/20231207161211.2374093-1-ryan.roberts@arm.com/#25628022
[2] https://kernelnewbies.org/MatthewWilcox/Memdescs
--
Cheers,
David / dhildenb
next reply other threads:[~2024-01-29 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 12:05 David Hildenbrand [this message]
2024-01-29 13:49 ` Matthew Wilcox
2024-01-29 14:09 ` David Hildenbrand
2024-02-01 16:17 ` Jason Gunthorpe
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=049e4674-44b6-4675-b53b-62e11481a7ce@redhat.com \
--to=david@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@kernel.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