From: Alex Rusuf <yorha.op@gmail.com>
To: damon@lists.linux.dev
Cc: sj@kernel.org
Subject: [RFC PATCH v1 0/7] DAMON multiple contexts support
Date: Wed, 15 May 2024 18:24:50 +0300 [thread overview]
Message-ID: <20240515152457.603724-1-yorha.op@gmail.com> (raw)
Currently kdamond uses only one context per kthread
and most of its time it sleeps, so utilizing several
contexts can scale kdamond and allow it to use
another set of operations.
This patch-set implements support for multiple contexts
per kdamond.
In pseudo code previous versions worked like
the following:
while (!kdamond_should_stop()) {
/* prepare accesses for only 1 context */
prepare_accesses(damon_context);
sleep(sample_interval);
/* check accesses for only 1 context */
check_accesses(damon_context);
...
}
With this patch kdamond workflow will look
like the following:
while (!kdamond_shoule_stop()) {
/* prepare accesses for all contexts in kdamond */
damon_for_each_context(ctx, kdamond)
prepare_accesses(ctx);
sleep(sample_interval);
/* check_accesses for all contexts in kdamond */
damon_for_each_context(ctx, kdamond)
check_accesses(ctx);
...
}
To try this you can use modified kernel[1] and
damo[2]. I also have written few simple shell scripts[3]
to collect data for damo.
[1] https://github.com/onlyoneofme/damon-multi-contexts.git
[2] https://github.com/onlyoneofme/damo/tree/multi-contexts
[3] https://github.com/onlyoneofme/damon-multi-contexts-tests.git
Alex Rusuf (7):
mm/damon/core: kdamond_struct abstraction layer
mm/damon/core: list-based contexts organization
mm/damon/lru_sort: kdamond_struct abstraction layer
mm/damon/reclaim: kdamon_struct abstraction layer
mm/damon/core: rename nr_running_ctxs -> nr_running_kdamonds
mm/damon/core: multi-context support
mm/damon/core: multi-context awarness for trace events
include/linux/damon.h | 48 +++-
include/trace/events/damon.h | 14 +-
mm/damon/core.c | 497 +++++++++++++++++++++--------------
mm/damon/lru_sort.c | 31 ++-
mm/damon/modules-common.c | 35 ++-
mm/damon/modules-common.h | 3 +-
mm/damon/reclaim.c | 30 ++-
mm/damon/sysfs.c | 306 +++++++++++++--------
8 files changed, 629 insertions(+), 335 deletions(-)
--
2.42.0
next reply other threads:[~2024-05-15 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 15:24 Alex Rusuf [this message]
2024-05-15 15:24 ` [RFC PATCH v1 1/7] mm/damon/core: kdamond_struct abstraction layer Alex Rusuf
2024-05-15 15:24 ` [RFC PATCH v1 2/7] mm/damon/core: list-based contexts organization Alex Rusuf
2024-05-15 15:24 ` [RFC PATCH v1 3/7] mm/damon/lru_sort: kdamond_struct abstraction layer Alex Rusuf
2024-05-15 15:24 ` [RFC PATCH v1 4/7] mm/damon/reclaim: kdamon_struct " Alex Rusuf
2024-05-15 15:24 ` [RFC PATCH v1 5/7] mm/damon/core: rename nr_running_ctxs -> nr_running_kdamonds Alex Rusuf
2024-05-15 15:24 ` [RFC PATCH v1 6/7] mm/damon/core: multi-context support Alex Rusuf
2024-05-15 15:24 ` [RFC PATCH v1 7/7] mm/damon/core: multi-context awarness for trace events Alex Rusuf
2024-05-16 22:17 ` [RFC PATCH v1 0/7] DAMON multiple contexts support SeongJae Park
2024-05-17 8:51 ` Alex Rusuf
2024-05-17 22:59 ` 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=20240515152457.603724-1-yorha.op@gmail.com \
--to=yorha.op@gmail.com \
--cc=damon@lists.linux.dev \
--cc=sj@kernel.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).