From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
David Hildenbrand <david@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Michal Hocko <mhocko@suse.com>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>,
damon@lists.linux.dev, kernel-team@meta.com,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: [PATCH v2 0/5] mm/damon: misc fixups and improvements for 6.18
Date: Mon, 15 Sep 2025 20:23:34 -0700 [thread overview]
Message-ID: <20250916032339.115817-1-sj@kernel.org> (raw)
Misc fixes and improvements for DAMON that are not critical and
therefore aims to be merged into Linux 6.18-rc1.
The first patch improves DAMON's age counting for nr_accesses zero
to/from non-zero changes.
The second patch fixes an initial DAMOS apply interval delay issue that
is not realistic but still could happen on an odd setup.
The third and the fourth patches update DAMON community meetup
description and DAMON user-space tool example command for DAMOS usage,
respectively.
Finally, the fifth patch updates MAINTAINERS section name for DAMON to
just DAMON.
Changes from v1
(https://lore.kernel.org/20250915015807.101505-1-sj@kernel.org)
- Separate [1] damon_attrs param_ctx usage as a hotfix patch
- Make nr_accesses reset condition easy to read
- Collect Joshua's Reviewed-by tags
Changes from RFC
(https://lore.kernel.org/20250909034353.7064-1-sj@kernel.org)
- The RFC was only for the first patch
- Rebase and wordsmith the first patch
- Add a few misc fixes and improvements for 6.18 to the series
[1] https://lore.kernel.org/20250916031549.115326-1-sj@kernel.org
SeongJae Park (5):
mm/damon/core: reset age if nr_accesses changes between non-zero and
zero
mm/damon/core: set effective quota on first charge window
Docs/mm/damon/maintainer-profile: update community meetup for
reservation requirements
Docs/admin-guide/mm/damon/start: add --target_pid to DAMOS example
command
MAINTAINERS: rename DAMON section
Documentation/admin-guide/mm/damon/start.rst | 2 +-
Documentation/mm/damon/maintainer-profile.rst | 17 ++++++-----------
MAINTAINERS | 2 +-
mm/damon/core.c | 6 +++++-
4 files changed, 13 insertions(+), 14 deletions(-)
base-commit: 4178fb3b4a5145053746caab556b1c5f5538bf3f
--
2.39.5
next reply other threads:[~2025-09-16 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 3:23 SeongJae Park [this message]
2025-09-16 3:23 ` [PATCH v2 1/5] mm/damon/core: reset age if nr_accesses changes between non-zero and zero SeongJae Park
2025-09-16 3:23 ` [PATCH v2 2/5] mm/damon/core: set effective quota on first charge window SeongJae Park
2025-09-16 3:23 ` [PATCH v2 3/5] Docs/mm/damon/maintainer-profile: update community meetup for reservation requirements SeongJae Park
2025-09-16 3:23 ` [PATCH v2 4/5] Docs/admin-guide/mm/damon/start: add --target_pid to DAMOS example command SeongJae Park
2025-09-16 3:23 ` [PATCH v2 5/5] MAINTAINERS: rename DAMON section 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=20250916032339.115817-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--cc=david@redhat.com \
--cc=kernel-team@meta.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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