From: "Huang\, Ying" <ying.huang@intel.com>
To: <lsf-pc@lists.linux-foundation.org>, <linux-mm@kvack.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Tim C Chen <tim.c.chen@intel.com>,
Feng Tang <feng.tang@intel.com>
Subject: [LSF/MM/BPF TOPIC] AutoNUMA enhancements to optimize Tiered Memory
Date: Thu, 13 Feb 2020 17:08:59 +0800 [thread overview]
Message-ID: <87mu9mhn10.fsf@yhuang-dev.intel.com> (raw)
Topic: AutoNUMA enhancements to optimize Tiered Memory
Traditionally, all RAM is DRAM. Some DRAM might be closer/faster than
others, but a byte of media has about the same cost whether it is close
or far. But, with new memory tiers such as High-Bandwidth Memory or
Persistent Memory, there is a choice between fast/expensive and
slow/cheap.
The existing reclaim mechanisms work wonderfully for moving cold data
out of fast/expensive tiers. However, reclaim does not work well for
moving hot data which might be stuck in a slow tier since the pages near
the top of the LRU are the most recently accessed only if there’s
regular memory pressure on the slow/cheap tiers.
Fortunately, AutoNUMA *can* find recently-accessed pages regardless of
memory pressure. We have repurposed it from being used for
location-based optimization to being used for tier-based optimization.
We have also optimized it for better hot data identification, such as to
find frequently-accessed pages instead of recently-accessed pages, etc.
We will show our findings so far, and discuss the remaining problems,
potential solutions, and alternatives.
reply other threads:[~2020-02-13 9:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87mu9mhn10.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=feng.tang@intel.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tim.c.chen@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 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).