From: Kaiyang Zhao <kaiyang2@cs.cmu.edu>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Yu Zhao <yuzhao@google.com>,
lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
Jonathan Corbet <corbet@lwn.net>,
kaiyang2@cs.cmu.edu, dskarlat@cs.cmu.edu
Subject: Re: [LSF/MM/BPF TOPIC] TAO: THP Allocator Optimizations
Date: Wed, 13 Mar 2024 22:09:17 +0000 [thread overview]
Message-ID: <ZfIkDWdEsvQMeBR9@box> (raw)
In-Reply-To: <20240306155110.GB891917@cmpxchg.org>
On Wed, Mar 06, 2024 at 10:51:10AM -0500, Johannes Weiner wrote:
> This is a very interesting topic to me. Meta has collaborated with CMU
> to research this as well, the results of which are typed up here:
> https://dl.acm.org/doi/pdf/10.1145/3579371.3589079
>
>
> I would like to be part of it, and would also suggest to have Kaiyang
> (CC'd) in the room, who is the primary researcher on the Contiguitas
> paper referenced above.
Thanks for bringing up Contiguitas, Johannes. Providing a large amount
of physical memory contiguity and managing it as a first-class resource
is very important for bringing a lot of research in virtual memory into
reality.
Johannes has already touched upon many parts of the kernel changes we
made in the Contiguitas project. To summarize, we want to confine the
unmovable allocations in a separate region in the physical address space
so that later memory contiguity can be obtained by successfully doing
compaction, and provide the ability to dynamically size the unmovable
region to adapt to changing workload characteristics and avoid static
sizing.
I will send an RFC with patches soon. Dimitrios (cc’d) and I are
interested in joining this effort and finding the best approach to
achieve our shared goal of more and easier-to-manage physical
contiguity.
next prev parent reply other threads:[~2024-03-13 22:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 18:34 [LSF/MM/BPF TOPIC] TAO: THP Allocator Optimizations Yu Zhao
2024-02-29 18:34 ` [Chapter One] THP zones: the use cases of policy zones Yu Zhao
2024-02-29 20:28 ` Matthew Wilcox
2024-03-06 3:51 ` Yu Zhao
2024-03-06 4:33 ` Matthew Wilcox
2024-02-29 23:31 ` Yang Shi
2024-03-03 2:47 ` Yu Zhao
2024-03-04 15:19 ` Matthew Wilcox
2024-03-05 17:22 ` Matthew Wilcox
2024-03-05 8:41 ` Barry Song
2024-03-05 10:07 ` Vlastimil Babka
2024-03-05 21:04 ` Barry Song
2024-03-06 3:05 ` Yu Zhao
2024-05-24 8:38 ` Barry Song
2024-11-01 2:35 ` Charan Teja Kalla
2024-11-01 16:55 ` Yu Zhao
2024-02-29 18:34 ` [Chapter Two] THP shattering: the reverse of collapsing Yu Zhao
2024-02-29 21:55 ` Zi Yan
2024-03-03 1:17 ` Yu Zhao
2024-03-03 1:21 ` Zi Yan
2024-06-11 8:32 ` Barry Song
2024-02-29 18:34 ` [Chapter Three] THP HVO: bring the hugeTLB feature to THP Yu Zhao
2024-02-29 22:54 ` Yang Shi
2024-03-01 15:42 ` David Hildenbrand
2024-03-03 1:46 ` Yu Zhao
2024-02-29 18:34 ` [Epilogue] Profile-Guided Heap Optimization and THP fungibility Yu Zhao
2024-03-05 8:37 ` [LSF/MM/BPF TOPIC] TAO: THP Allocator Optimizations Barry Song
2024-03-06 15:51 ` Johannes Weiner
2024-03-06 16:40 ` Zi Yan
2024-03-13 22:09 ` Kaiyang Zhao [this message]
2024-05-15 21:17 ` Yu Zhao
2024-05-15 21:52 ` Yu Zhao
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=ZfIkDWdEsvQMeBR9@box \
--to=kaiyang2@cs.cmu.edu \
--cc=corbet@lwn.net \
--cc=dskarlat@cs.cmu.edu \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=yuzhao@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;
as well as URLs for NNTP newsgroup(s).