All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: sj@kernel.org, ying.huang@intel.com, dave.hansen@linux.intel.com,
	ziy@nvidia.com, shy828301@gmail.com,
	zhongjiang-ali@linux.alibaba.com, xlpang@linux.alibaba.com,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add a new scheme to support demotion on tiered memory system
Date: Thu, 23 Dec 2021 09:01:05 +0800	[thread overview]
Message-ID: <362fb4fe-34c8-d83d-b8be-a4140e19b244@linux.alibaba.com> (raw)
In-Reply-To: <20211222160105.a267eaacefae77ae094c050e@linux-foundation.org>



On 12/23/2021 8:01 AM, Andrew Morton wrote:
> On Wed, 22 Dec 2021 19:14:39 +0800 Baolin Wang <baolin.wang@linux.alibaba.com> wrote:
> 
>> Now on tiered memory system with different memory types, the reclaim path in
>> shrink_page_list() already support demoting pages to slow memory node instead
>> of discarding the pages. However, at that time the fast memory node memory
>> wartermark is already tense, which will increase the memory allocation latency
>> during page demotion. So a new method from user space demoting cold pages
>> proactively will be more helpful.
>>
>> We can rely on the DAMON in user space to help to monitor the cold memory on
>> fast memory node, and demote the cold pages to slow memory node proactively to
>> keep the fast memory node in a healthy state.
>>
>> This patch set introduces a new scheme named DAMOS_DEMOTE to support this feature,
>> and works well from my testing. Any comments are welcome. Thanks.
> 
> This is interesting.
> 
> I think it would be helpful if we could have some example scenarios in
> this changelog, help people understand how to use DAMOS_DEMOTE and what
> effects it has.

Sure.

> 
> Documentation/admin-guide/mm/damon/usage.rst would like an update?

Ah, I missed updating de Doc, and will do in v3.

> And the DAMON user space tool?

Yes. Thanks for your comments.


  reply	other threads:[~2021-12-23  1:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 11:14 [PATCH v2 0/2] Add a new scheme to support demotion on tiered memory system Baolin Wang
2021-12-22 11:14 ` [PATCH v2 1/2] mm: Export the demote_page_list() function Baolin Wang
2021-12-22 11:14 ` [PATCH v2 2/2] mm/damon: Add a new scheme to support demotion on tiered memory system Baolin Wang
2021-12-23  0:01 ` [PATCH v2 0/2] " Andrew Morton
2021-12-23  1:01   ` Baolin Wang [this message]
2021-12-23  1:07 ` Huang, Ying
2021-12-23  1:21   ` Baolin Wang
2021-12-23  3:22     ` Huang, Ying
2021-12-23  6:35       ` Baolin Wang
2021-12-23  7:51         ` Huang, Ying
2021-12-23 11:31           ` SeongJae Park
2021-12-27  3:09             ` Huang, Ying
2021-12-28  8:44               ` SeongJae Park
2021-12-29  1:33                 ` Huang, Ying
2021-12-29 10:34                   ` SeongJae Park
2021-12-30  3:16                     ` Huang, Ying
2021-12-30  8:03                       ` SeongJae Park
2021-12-30  9:31                 ` Baolin Wang

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=362fb4fe-34c8-d83d-b8be-a4140e19b244@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shy828301@gmail.com \
    --cc=sj@kernel.org \
    --cc=xlpang@linux.alibaba.com \
    --cc=ying.huang@intel.com \
    --cc=zhongjiang-ali@linux.alibaba.com \
    --cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.