From: "Huang, Ying" <ying.huang@intel.com>
To: Oscar Salvador <osalvador@suse.de>
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, 01 Mar 2022 09:16:18 +0800 [thread overview]
Message-ID: <87czj6321p.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <YhzwO/lw1xx7EjNb@localhost.localdomain> (Oscar Salvador's message of "Mon, 28 Feb 2022 16:54:35 +0100")
Hi, Oscar,
Oscar Salvador <osalvador@suse.de> writes:
> On Mon, Feb 21, 2022 at 04:45:28PM +0800, Huang Ying wrote:
>> 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). Then, if the free pages of the fast memory node reaches
>> high watermark, and some hot pages need to be promoted, kswapd of the
>> fast memory node will be waken up to demote more cold pages in the
>> fast memory node to the slow memory node. 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.
>
> The patch looks good to me, but I think I might be confused by the wording
> here.
>
> IIUC, we define a new wmark (wmark_promo) which is higher than
> wmark_high.
> When we cannot migrate a page to another numa node because it has less
> than wmark_high free pages, we wake up kswapd, and we keep reclaiming
> until we either have mark_promo pages free when
> NUMA_BALANCING_MEMORY_TIERING, or mark_high pages free. Is that right?
Yes. And we only wake up kswapd for promotion when
NUMA_BALANCING_MEMORY_TIERING.
> Because above you say "Then, if the free pages of the fast memory node reaches
> high watermark, and some hot pages need to be promoted..."
What I wanted to say is that
If the free pages of the fast memory will become lower than the high
watermark, and some hot pages need to be promoted...
That is, "reach high watermark" here is from "free pages more than high
watermark" to "free pages lower or equal high watermark". This appears
confusing.
> but that should read promo watermark instead? Am I missing something?
Sorry for confusing. How about the following?
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.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2022-03-01 1:16 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 [this message]
2022-03-01 6:18 ` Oscar Salvador
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=87czj6321p.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--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=osalvador@suse.de \
--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=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