From: Xin Hao <xhao@linux.alibaba.com>
To: sj@kernel.org
Cc: xhao@linux.alibaba.com, rongwei.wang@linux.alibaba.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support
Date: Wed, 16 Mar 2022 00:37:04 +0800 [thread overview]
Message-ID: <cover.1647378112.git.xhao@linux.alibaba.com> (raw)
The purpose of these patches is to add CMA memory monitoring function.
In some memory tight scenarios, it will be a good choice to release more
memory by monitoring the CMA memory.
These patches is only preliminarily for monitoring function, About the
reclaim, it need to do some fixes base on "reclaim.c" and more tests,
I will implement it in the next patch series.
Xin Hao (3):
mm/damon: rename damon_evenly_split_region()
mm/damon/paddr: Move "paddr" relative func to ops-common.c file
mm/damon/sysfs: Add CMA memory monitoring
include/linux/damon.h | 1 +
mm/damon/Makefile | 2 +-
mm/damon/ops-common.c | 286 ++++++++++++++++++++++++++++++++++++++++++
mm/damon/ops-common.h | 18 +++
mm/damon/paddr-cma.c | 104 +++++++++++++++
mm/damon/paddr.c | 246 ------------------------------------
mm/damon/sysfs.c | 1 +
mm/damon/vaddr-test.h | 6 +-
mm/damon/vaddr.c | 41 +-----
9 files changed, 415 insertions(+), 290 deletions(-)
create mode 100644 mm/damon/paddr-cma.c
--
2.27.0
next reply other threads:[~2022-03-15 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 16:37 Xin Hao [this message]
2022-03-15 16:37 ` [RFC PATCH V1 1/3] mm/damon: rename damon_evenly_split_region() Xin Hao
2022-03-15 16:37 ` [RFC PATCH V1 2/3] mm/damon/paddr: Move "paddr" relative func to ops-common.c file Xin Hao
2022-03-15 16:37 ` [RFC PATCH V1 3/3] mm/damon/sysfs: Add CMA memory monitoring Xin Hao
2022-03-16 15:09 ` [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support David Hildenbrand
2022-03-17 7:03 ` Xin Hao
2022-03-17 16:42 ` David Hildenbrand
2022-03-18 5:13 ` xhao
2022-03-18 8:29 ` David Hildenbrand
2022-03-18 8:40 ` sj
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=cover.1647378112.git.xhao@linux.alibaba.com \
--to=xhao@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rongwei.wang@linux.alibaba.com \
--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 NNTP newsgroup(s).