From: Mike Kravetz <mike.kravetz@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, James Houghton <jthoughton@google.com>,
Peter Xu <peterx@redhat.com>
Subject: [LSF/MM/BPF TOPIC] HGM for hugetlbfs
Date: Mon, 6 Mar 2023 11:19:44 -0800 [thread overview]
Message-ID: <20230306191944.GA15773@monkey> (raw)
This is past the deadline, so feel free to ignore. However, ...
James Houghton has been working on the concept of HugeTLB High Granularity
Mapping (HGM) as discussed here:
https://lore.kernel.org/linux-mm/20230218002819.1486479-1-jthoughton@google.com/
The primary motivation for this work is post-copy live migration of VMs backed
by hugetlb pages via userfaultfd. A followup use case is more gracefully
handling memory errors/poison on hugetlb pages.
As can be seen by the size of James's patch set, the required changes for
HGM are a bit complex and involved. This is also complicated the need
choosing a 'mapcount strategy' as the previous scheme used by hugetlb
will no longer work.
A HGM for hugetlbfs session would present the current approach and challenges.
While much of the work is confined to hugetlb, there is a bit spill over to
other mm areas: specifically page table walking. A discussion on ways to
move forward with this effort would be appreciated.
--
Mike Kravetz
next reply other threads:[~2023-03-06 19:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 19:19 Mike Kravetz [this message]
2023-03-14 15:37 ` James Houghton
2023-04-12 1:44 ` David Rientjes
2023-05-24 20:26 ` James Houghton
2023-05-26 3:00 ` David Rientjes
[not found] ` <20230602172723.GA3941@monkey>
2023-06-06 22:40 ` David Rientjes
2023-06-07 7:38 ` David Hildenbrand
2023-06-07 7:51 ` Yosry Ahmed
2023-06-07 8:13 ` David Hildenbrand
2023-06-07 22:06 ` Mike Kravetz
2023-06-08 0:02 ` David Rientjes
2023-06-08 6:34 ` David Hildenbrand
2023-06-08 18:50 ` Yang Shi
2023-06-08 21:23 ` Mike Kravetz
2023-06-09 1:57 ` Zi Yan
2023-06-09 15:17 ` Pasha Tatashin
2023-06-09 19:04 ` Ankur Arora
2023-06-09 19:57 ` Matthew Wilcox
2023-06-08 20:10 ` Matthew Wilcox
2023-06-09 2:59 ` David Rientjes
2023-06-13 14:59 ` Jason Gunthorpe
2023-06-13 15:15 ` David Hildenbrand
2023-06-13 15:45 ` Peter Xu
2023-06-08 21:54 ` [Lsf-pc] " Dan Williams
2023-06-08 22:35 ` Mike Kravetz
2023-06-09 3:36 ` Dan Williams
2023-06-09 20:20 ` James Houghton
2023-06-13 15:17 ` Jason Gunthorpe
2023-06-07 14:40 ` Matthew Wilcox
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=20230306191944.GA15773@monkey \
--to=mike.kravetz@oracle.com \
--cc=jthoughton@google.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=peterx@redhat.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