From: SeongJae Park <sj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: SeongJae Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
damon@lists.linux.dev, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] mm/damon/sysfs-schemes: Do DAMOS tried regions update for only one apply interval
Date: Thu, 12 Oct 2023 19:22:52 +0000 [thread overview]
Message-ID: <20231012192256.33556-1-sj@kernel.org> (raw)
Changes from RFC
(https://lore.kernel.org/damon/20231010012600.83140-1-sj@kernel.org/)
- Rebase on latest mm-unstable
DAMOS tried regions update feature of DAMON sysfs interface is doing the
update for one aggregation interval after the request is made. Since
the per-scheme apply interval is supported, that behavior makes no much
sense. That is, the tried regions directory will have regions from
multiple DAMON monitoring results snapshots, or no region for apply
intervals that much shorter than, or longer than the aggregation
interval, respectively. Update the behavior to update the regions for
each scheme for only its apply interval, and update the document.
Since DAMOS apply interval is the aggregation by default, this change
makes no visible behavioral difference to old users who don't explicitly
set the apply intervals.
Patches Sequence
----------------
The first two patches makes schemes of apply intervals that much shorter
or longer than the aggregation interval to keep the maximum and minimum
times for continuing the update. After the two patches, the update
aligns with the each scheme's apply interval.
Finally, the third patch updates the document to reflect the behavior.
SeongJae Park (3):
mm/damon/sysfs-schemes: do not update tried regions more than one
DAMON snapshot
mm/damon/sysfs: avoid empty scheme tried regions for large apply
interval
Docs/admin-guide/mm/damon/usage: update for tried regions update time
interval
Documentation/admin-guide/mm/damon/usage.rst | 6 +-
mm/damon/sysfs-common.h | 2 +
mm/damon/sysfs-schemes.c | 93 ++++++++++++++++++++
mm/damon/sysfs.c | 34 ++++++-
4 files changed, 128 insertions(+), 7 deletions(-)
base-commit: 937421b2a4e95c57fddf10477b949fa5693711da
--
2.34.1
next reply other threads:[~2023-10-12 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 19:22 SeongJae Park [this message]
2023-10-12 19:22 ` [PATCH 1/3] mm/damon/sysfs-schemes: do not update tried regions more than one DAMON snapshot SeongJae Park
2023-10-12 19:22 ` [PATCH 2/3] mm/damon/sysfs: avoid empty scheme tried regions for large apply interval SeongJae Park
2023-10-12 19:22 ` [PATCH 3/3] Docs/admin-guide/mm/damon/usage: update for tried regions update time interval 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=20231012192256.33556-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=damon@lists.linux.dev \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).