linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
	linux-mm@kvack.org,
	Asier Gutierrez <gutierrez.asier@huawei-partners.com>,
	damon@lists.linux.dev, linux-kernel@vger.kernel.org,
	lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM/BPF TOPIC] Data Access-aware Transparent Hugepages
Date: Tue, 10 Feb 2026 21:07:28 -0800	[thread overview]
Message-ID: <20260211050729.69719-1-sj@kernel.org> (raw)
In-Reply-To: <20260211044533.69515-1-sj@kernel.org>

On Tue, 10 Feb 2026 20:45:33 -0800 SeongJae Park <sj@kernel.org> wrote:

> Forgot Cc-ing damon@ and linux-kernel@.  Adding those.  Sorry for noise.

And lsf-pc@ ...

> 
> On Tue, 10 Feb 2026 18:28:55 SeongJae Park <sj@kernel.org> wrote:
> 
> > Hello,
> > 
> > 
> > Transparent Huge Pages (THP) could be more efficient if those are used only for
> > frequently accessed data.  DAMON is one of the ways for fidning such hot data,
> > and hence there were interests in utilizing DAMON for access-aware THP.  A
> > simple experiment leveraging MADV_[NO]HUGEPAGE based on DAMON-identifed hot and
> > cold memory regions was conducted as a proof of the concept.  The experiment
> > demonstrated [1] an 80% reduction in memory overhead while retaining 46% of THP
> > performance gains.
> > 
> > Multiple discussions for further developing production level access-aware THP
> > solutions have followed.  Most of the discussions were made in private, though
> > Asier recently proposed yet another approach [2] on the mailing list.  As a
> > result, we collected interesting challenges and ideas for the production level
> > data access-aware THP.  Some of the ideas are not yet public, could be
> > controversial, and missing important things that more eyeballs can find.  I
> > want to discuss those in LSF/MM/BPF to get more ideas and make high level
> > community alignments for next steps.
> > 
> > [1] https://assets.amazon.science/b7/2b/ce53222247739b174f2b54498d1a/daos-data-access-aware-operating-system.pdf
> > [2] https://lore.kernel.org/20260202145650.1795854-1-gutierrez.asier@huawei-partners.com
> > 
> > 
> > Thanks,
> > SJ
> > 
> 
> Sent using hkml (https://github.com/sjp38/hackermail)

Sent using hkml (https://github.com/sjp38/hackermail)


      reply	other threads:[~2026-02-11  5:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  2:28 SeongJae Park
2026-02-11  4:45 ` SeongJae Park
2026-02-11  5:07   ` SeongJae Park [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=20260211050729.69719-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=gutierrez.asier@huawei-partners.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.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