From: Matthew Wilcox <willy@infradead.org>
To: Yu Zhao <yuzhao@google.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
page-reclaim@google.com
Subject: Re: Augmented Page Reclaim
Date: Tue, 2 Feb 2021 12:17:08 +0000 [thread overview]
Message-ID: <20210202121708.GT308988@casper.infradead.org> (raw)
In-Reply-To: <YBkT6175GmMWBvw3@google.com>
It's hard to know which 'note' refers to which reference. Here's
my attempt to figure that out.
On Tue, Feb 02, 2021 at 01:57:15AM -0700, Yu Zhao wrote:
> Versatility
> ===========
> Userspace can trigger aging and eviction independently via the
> ``debugfs`` interface [note]_ for working set estimation, proactive
1. `Long-term SLOs for reclaimed cloud computing resources
<https://research.google/pubs/pub43017/>`_
> reclaim, far memory tiering, NUMA-aware job scheduling, etc. The
> metrics from the interface are easily interpretable, which allows
> intuitive provisioning and discoveries like the Borg example above.
> For a warehouse-scale computer, the interface is intended to be a
> building block of a closed-loop control system, with a machine
> learning algorithm being the controller.
>
> Simplicity
> ==========
> The workflow [note]_ is well defined and each step in it has a clear
2. `Profiling a warehouse-scale computer
<https://research.google/pubs/pub44271/>`_
> meaning. There are no magic numbers or heuristics involved but a few
> basic data structures that have negligible memory footprint. This
> simplicity has served us well as the scale and the diversity of our
> workloads constantly grow.
[...]
> FAQ
> ===
> What is the motivation for this work?
> -------------------------------------
> In our case, DRAM is a major factor in total cost of ownership, and
> improving memory overcommit brings a high return on investment.
> Moreover, Google-Wide Profiling has been observing the high CPU
> overhead [note]_ from page reclaim.
3. `Evaluation of NUMA-Aware Scheduling in Warehouse-Scale Clusters
<https://research.google/pubs/pub48329/>`_
> Why not try to improve the existing code?
> -----------------------------------------
> We have tried but concluded the two limiting factors [note]_ in the
4. `Software-defined far memory in warehouse-scale computers
<https://research.google/pubs/pub48551/>`_
> existing code are fundamental, and therefore changes made atop them
> will not result in substantial gains on any of the aspects above.
>
> What particular workloads does it help?
> ---------------------------------------
> This work optimizes page reclaim for workloads that are not IO bound,
> because we find they are the norm on servers and clients in the cloud
> era. It would most likely help any workloads that share the common
> characteristics [note]_ we observed.
5. `Borg: the Next Generation
<https://research.google/pubs/pub49065/>`_
next prev parent reply other threads:[~2021-02-02 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 8:57 Augmented Page Reclaim Yu Zhao
2021-02-02 12:17 ` Matthew Wilcox [this message]
2021-02-02 19:38 ` Yu Zhao
2021-02-09 21:32 ` [page-reclaim] " Jesse Barnes
2021-02-10 7:12 ` Yu Zhao
2021-02-10 13:22 ` Michal Hocko
2021-02-10 9:55 ` Hillf Danton
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=20210202121708.GT308988@casper.infradead.org \
--to=willy@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=page-reclaim@google.com \
--cc=yuzhao@google.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).