From: David Hildenbrand <david@redhat.com>
To: Xin Hao <xhao@linux.alibaba.com>, sj@kernel.org
Cc: rongwei.wang@linux.alibaba.com, akpm@linux-foundation.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support
Date: Wed, 16 Mar 2022 16:09:02 +0100 [thread overview]
Message-ID: <a1e0a9e9-07ef-8d1c-a409-2b4fb12ed553@redhat.com> (raw)
In-Reply-To: <cover.1647378112.git.xhao@linux.alibaba.com>
On 15.03.22 17:37, Xin Hao wrote:
s/minotor/monitor/
> 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.
I'm sorry, but it's hard to figure out what the target use case should
be. Who will release CMA memory and how? Who will monitor that? What are
the "some memory tight scenarios"? What's the overall design goal?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-03-16 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 16:37 [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support Xin Hao
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 ` David Hildenbrand [this message]
2022-03-17 7:03 ` [RFC PATCH V1 0/3] mm/damon: Add CMA minotor support 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=a1e0a9e9-07ef-8d1c-a409-2b4fb12ed553@redhat.com \
--to=david@redhat.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 \
--cc=xhao@linux.alibaba.com \
/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).