From: Yang Shi <shy828301@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [LSF/MM TOPIC] memory reclaim with NUMA rebalancing
Date: Wed, 30 Jan 2019 15:53:13 -0800 [thread overview]
Message-ID: <CAHbLzkpbWEVpeH9YsbBNy-Etfe0Pza5rPAe3b50sXq4rV4C+xQ@mail.gmail.com> (raw)
In-Reply-To: <20190130174847.GD18811@dhcp22.suse.cz>
On Wed, Jan 30, 2019 at 9:48 AM Michal Hocko <mhocko@kernel.org> wrote:
>
> Hi,
> I would like to propose the following topic for the MM track. Different
> group of people would like to use NVIDMMs as a low cost & slower memory
> which is presented to the system as a NUMA node. We do have a NUMA API
> but it doesn't really fit to "balance the memory between nodes" needs.
> People would like to have hot pages in the regular RAM while cold pages
> might be at lower speed NUMA nodes. We do have NUMA balancing for
> promotion path but there is notIhing for the other direction. Can we
> start considering memory reclaim to move pages to more distant and idle
> NUMA nodes rather than reclaim them? There are certainly details that
> will get quite complicated but I guess it is time to start discussing
> this at least.
I would be interested in this topic too. We (Alibaba) do have some
usecases with using NVDIMM as NUMA node. The node balancing (or
cold/hot data migration) is one of our needs to achieve optimal
performance for some workloads. I also proposed a related topic.
Regards,
Yang
> --
> Michal Hocko
> SUSE Labs
>
next prev parent reply other threads:[~2019-01-30 23:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 17:48 Michal Hocko
2019-01-30 18:12 ` Keith Busch
2019-01-30 23:53 ` Yang Shi [this message]
2019-01-31 6:49 ` [LSF/MM ATTEND ] " Aneesh Kumar K.V
2019-02-06 19:03 ` Christopher Lameter
2019-02-22 13:48 ` Jonathan Cameron
2019-02-22 14:12 ` Larry Woodman
2019-02-23 13:27 ` Fengguang Wu
2019-02-23 13:42 ` Fengguang Wu
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=CAHbLzkpbWEVpeH9YsbBNy-Etfe0Pza5rPAe3b50sXq4rV4C+xQ@mail.gmail.com \
--to=shy828301@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvme@lists.infradead.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@kernel.org \
/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