From: Oscar Salvador <osalvador@suse.de>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Mel Gorman <mgorman@techsingularity.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Feng Tang <feng.tang@intel.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Michal Hocko <mhocko@suse.com>, Rik van Riel <riel@surriel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Yang Shi <shy828301@gmail.com>, Zi Yan <ziy@nvidia.com>,
Wei Xu <weixugc@google.com>, Shakeel Butt <shakeelb@google.com>,
zhongjiang-ali <zhongjiang-ali@linux.alibaba.com>,
Randy Dunlap <rdunlap@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH -V13 2/3] NUMA balancing: optimize page placement for memory tiering system
Date: Tue, 1 Mar 2022 07:18:39 +0100 [thread overview]
Message-ID: <Yh26v+4LtnvFnWWz@localhost.localdomain> (raw)
In-Reply-To: <87czj6321p.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Tue, Mar 01, 2022 at 09:16:18AM +0800, Huang, Ying wrote:
> Hi, Oscar,
Hi Huang Ying
> b. Make kswapd of the fast memory node to reclaim pages until the free
> pages are a little more than the high watermark (named as promo
> watermark). If we want to promote some hot pages from the slow
> memory to the fast memory, but the free pages of the fast memory
> node will become lower than the high watermark after promotion, we
> will wake up kswapd of the fast memory node to demote more cold
> pages in the fast memory node to the slow memory node firstly. This
> will free some extra space in the fast memory node, so the hot pages
> in the slow memory node can be promoted to the fast memory node.
What about this? Somehow it sounds clear to me.
"b. Define a new watermark called wmark_promo which is higher than wmark_high,
and have kswapd reclaiming pages until free pages reach such watermark.
The scenario is as follows: when we want to promote hot-pages from a slow
memory to a fast memory, but fast memory's free pages would go lower than
high watermark with such promotion, we wake up kswapd with wmark_promo
watermark in order to demote cold pages and free us up some space.
So, next time we want to promote hot-pages we might have a chance of
doing so."
But I am fine with your updated write up as well, so if you spin a new
version:
Reviewed-by: Oscar Salvador <osalvador@suse.de>
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2022-03-01 6:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 8:45 [PATCH -V13 0/3] NUMA balancing: optimize memory " Huang Ying
2022-02-21 8:45 ` [PATCH -V13 1/3] NUMA Balancing: add page promotion counter Huang Ying
2022-02-21 8:45 ` [PATCH -V13 2/3] NUMA balancing: optimize page placement for memory tiering system Huang Ying
2022-02-22 16:34 ` Johannes Weiner
2022-02-28 15:54 ` Oscar Salvador
2022-03-01 1:16 ` Huang, Ying
2022-03-01 6:18 ` Oscar Salvador [this message]
2022-03-01 6:40 ` Huang, Ying
2022-03-01 6:28 ` Miaohe Lin
2022-03-01 6:47 ` Huang, Ying
2022-03-01 7:51 ` Miaohe Lin
2022-02-21 8:45 ` [PATCH -V13 3/3] memory tiering: skip to scan fast memory Huang Ying
2022-03-01 6:33 ` Oscar Salvador
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=Yh26v+4LtnvFnWWz@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@linux.intel.com \
--cc=feng.tang@intel.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=riel@surriel.com \
--cc=shakeelb@google.com \
--cc=shy828301@gmail.com \
--cc=weixugc@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox