linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
Cc: SeongJae Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Bijan Tabatabai <bijan311@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	damon@lists.linux.dev, kernel-team@meta.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: [RFC PATCH v2 0/6] mm/damon: add DAMOS_MIGRATE_{HOT,COLD} destination nodes and weights
Date: Tue,  1 Jul 2025 22:15:52 -0700	[thread overview]
Message-ID: <20250702051558.54138-1-sj@kernel.org> (raw)

DAMOS_MIGRATE_{HOT,COLD} action can migrate pages to only single node.
It could be useful to allow it migrates pages to multiple nodes with
different weights.  A work for dynamic interleaving[1], which is in
progress, is an expected case.  We also discussed this could be useful
for memory tiering, e.g., when we want to move pages to multiple noes of
same tier.

Extend the API and ABI for specifying the multiple destination nodes and
their weights.

Note that this RFC is a prototype of the interface change for Bijan's
interleaving work[1].  Hence this patch series is only implementing the
interface part, not the real implementation of the migration behavior.

[1] https://lore.kernel.org/20250620180458.5041-1-bijan311@gmail.com
[2] https://lore.kernel.org/20240408175228.91414-1-sj@kernel.org

Changes from RFC
(https://lore.kernel.org/20250621173131.23917-1-sj@kernel.org)
- Add documentation patches
- Wordsmith commit messages
- Rebase on latest mm-new

SeongJae Park (6):
  mm/damon: add struct damos_migrate_dest
  mm/damon/core: add damos->migrate_dest field
  mm/damon/sysfs-schemes: implement DAMOS action destinations directory
  mm/damon/sysfs-schemes: set damos->migrate_dest
  Docs/ABI/damon: document schemes dests directory
  Docs/admin-guide/mm/damon/usage: document dests directory

 .../ABI/testing/sysfs-kernel-mm-damon         |  22 ++
 Documentation/admin-guide/mm/damon/usage.rst  |  33 ++-
 include/linux/damon.h                         |  29 +-
 mm/damon/core.c                               |   4 +
 mm/damon/sysfs-schemes.c                      | 253 +++++++++++++++++-
 5 files changed, 333 insertions(+), 8 deletions(-)


base-commit: 8a6d44984fa3076b444a6ddd8a8898b6ba254d25
-- 
2.39.5


             reply	other threads:[~2025-07-02  5:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02  5:15 SeongJae Park [this message]
2025-07-02  5:15 ` [RFC PATCH v2 1/6] mm/damon: add struct damos_migrate_dest SeongJae Park
2025-07-02  5:15 ` [RFC PATCH v2 2/6] mm/damon/core: add damos->migrate_dest field SeongJae Park
2025-07-02  5:15 ` [RFC PATCH v2 3/6] mm/damon/sysfs-schemes: implement DAMOS action destinations directory SeongJae Park
2025-07-02  5:15 ` [RFC PATCH v2 4/6] mm/damon/sysfs-schemes: set damos->migrate_dest SeongJae Park
2025-07-02  5:15 ` [RFC PATCH v2 5/6] Docs/ABI/damon: document schemes dests directory SeongJae Park
2025-07-02  5:15 ` [RFC PATCH v2 6/6] Docs/admin-guide/mm/damon/usage: document " SeongJae Park

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=20250702051558.54138-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bijan311@gmail.com \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=kernel-team@meta.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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