From: Michal Hocko <mhocko@kernel.org>
To: Fan Du <fan.du@intel.com>
Cc: akpm@linux-foundation.org, fengguang.wu@intel.com,
dan.j.williams@intel.com, dave.hansen@intel.com,
xishi.qiuxishi@alibaba-inc.com, ying.huang@intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/5] New fallback workflow for heterogeneous memory system
Date: Thu, 25 Apr 2019 08:37:27 +0200 [thread overview]
Message-ID: <20190425063727.GJ12751@dhcp22.suse.cz> (raw)
In-Reply-To: <1556155295-77723-1-git-send-email-fan.du@intel.com>
On Thu 25-04-19 09:21:30, Fan Du wrote:
[...]
> However PMEM has different characteristics from DRAM,
> the more reasonable or desirable fallback style would be:
> DRAM node 0 -> DRAM node 1 -> PMEM node 2 -> PMEM node 3.
> When DRAM is exhausted, try PMEM then.
Why and who does care? NUMA is fundamentally about memory nodes with
different access characteristics so why is PMEM any special?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-04-25 7:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 1:21 [RFC PATCH 0/5] New fallback workflow for heterogeneous memory system Fan Du
2019-04-25 1:21 ` [RFC PATCH 1/5] acpi/numa: memorize NUMA node type from SRAT table Fan Du
2019-04-25 1:21 ` [RFC PATCH 2/5] mmzone: new pgdat flags for DRAM and PMEM Fan Du
2019-04-25 1:21 ` [RFC PATCH 3/5] x86,numa: update numa node type Fan Du
2019-04-25 1:21 ` [RFC PATCH 4/5] mm, page alloc: build fallback list on per node type basis Fan Du
2019-04-25 1:21 ` [RFC PATCH 5/5] mm, page_alloc: Introduce ZONELIST_FALLBACK_SAME_TYPE fallback list Fan Du
[not found] ` <a0728518-a067-4f89-a8ae-3fa279f768f2.xishi.qiuxishi@alibaba-inc.com>
2019-04-25 3:26 ` Xishi Qiu
2019-04-25 7:45 ` Du, Fan
2019-04-25 6:38 ` Michal Hocko
2019-04-25 7:43 ` Du, Fan
2019-04-25 7:48 ` Michal Hocko
2019-04-25 7:55 ` Du, Fan
2019-04-25 8:09 ` Michal Hocko
2019-04-25 8:20 ` Du, Fan
2019-04-25 8:43 ` Michal Hocko
2019-04-25 9:18 ` Du, Fan
2019-04-25 6:37 ` Michal Hocko [this message]
2019-04-25 7:41 ` [RFC PATCH 0/5] New fallback workflow for heterogeneous memory system Du, Fan
2019-04-25 7:53 ` Michal Hocko
2019-04-25 8:05 ` Du, Fan
2019-04-25 15:43 ` Dan Williams
2019-04-26 2:40 ` Du, Fan
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=20190425063727.GJ12751@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=fan.du@intel.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=xishi.qiuxishi@alibaba-inc.com \
--cc=ying.huang@intel.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.