From: Andrew Morton <akpm@linux-foundation.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
yang.shi@linux.alibaba.com, rientjes@google.com,
dan.j.williams@intel.com, david@redhat.com, osalvador@suse.de,
weixugc@google.com, Michal Hocko <mhocko@suse.com>,
Yang Shi <shy828301@gmail.com>, Zi Yan <ziy@nvidia.com>
Subject: Re: [PATCH -V10 0/9] Migrate Pages in lieu of discard
Date: Thu, 15 Jul 2021 20:54:15 -0700 [thread overview]
Message-ID: <20210715205415.2d6842be57032fbdb2cd2a82@linux-foundation.org> (raw)
In-Reply-To: <87k0lrndc6.fsf@yhuang6-desk2.ccr.corp.intel.com>
On Fri, 16 Jul 2021 11:32:09 +0800 "Huang, Ying" <ying.huang@intel.com> wrote:
> Andrew Morton <akpm@linux-foundation.org> writes:
>
> > On Thu, 15 Jul 2021 13:51:36 +0800 Huang Ying <ying.huang@intel.com> wrote:
> >
> > The [0/n] description talks a lot about PMEM, but the patches
> > themselves are all about NUMA nodes. I assume that what ties this
> > together is that the PMEM tends to be organized as a NUMA node on its
> > own, and that by enabling migrate-to-remote-node-during-reclaim, we get
> > this PMEM behaviour as a desired side-effect?
> >
> > IOW, perhaps this [0/n] description could explain the linkage between
> > PMEM and NUMA nodes more explicitly.
>
> Hi, Andrew,
>
> I have added some words in the [0/9] description to link PMEM and NUMA
> nodes. The updated description is as below. Can you take a look at it?
>
> ...
>
> With that, the DRAM and PMEM in each socket will be represented as 2
> separate NUMA nodes, with the CPUs sit in the DRAM node. So the
> general inter-NUMA demotion mechanism introduced in the patchset can
> migrate the cold DRAM pages to the PMEM node.
>
Bingo, thanks.
prev parent reply other threads:[~2021-07-16 3:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 5:51 [PATCH -V10 0/9] Migrate Pages in lieu of discard Huang Ying
2021-07-15 5:51 ` [PATCH -V10 1/9] mm/numa: automatically generate node migration order Huang Ying
2021-07-15 17:52 ` Zi Yan
2021-07-15 5:51 ` [PATCH -V10 2/9] mm/migrate: update node demotion order on hotplug events Huang Ying
2021-07-15 18:00 ` Zi Yan
2021-07-15 5:51 ` [PATCH -V10 3/9] mm/migrate: enable returning precise migrate_pages() success count Huang Ying
2021-07-15 18:02 ` Zi Yan
2021-07-15 5:51 ` [PATCH -V10 4/9] mm/migrate: demote pages during reclaim Huang Ying
2021-07-15 5:51 ` [PATCH -V10 5/9] mm/vmscan: add page demotion counter Huang Ying
2021-07-15 5:51 ` [PATCH -V10 6/9] mm/vmscan: add helper for querying ability to age anonymous pages Huang Ying
2021-07-15 5:51 ` [PATCH -V10 7/9] mm/vmscan: Consider anonymous pages without swap Huang Ying
2021-07-15 5:51 ` [PATCH -V10 8/9] mm/vmscan: never demote for memcg reclaim Huang Ying
2021-07-15 5:51 ` [PATCH -V10 9/9] mm/migrate: add sysfs interface to enable reclaim migration Huang Ying
2021-07-15 19:38 ` [PATCH -V10 0/9] Migrate Pages in lieu of discard Andrew Morton
2021-07-15 21:42 ` Dave Hansen
2021-07-16 1:10 ` Matthew Wilcox
2021-07-16 3:32 ` Huang, Ying
2021-07-16 3:54 ` Andrew Morton [this message]
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=20210715205415.2d6842be57032fbdb2cd2a82@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=rientjes@google.com \
--cc=shy828301@gmail.com \
--cc=weixugc@google.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).