From: Yang Shi <shy828301@gmail.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: Mel Gorman <mgorman@techsingularity.net>,
lsf-pc@lists.linux-foundation.org, Linux MM <linux-mm@kvack.org>,
Michal Hocko <mhocko@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Rik van Riel <riel@surriel.com>, Roman Gushchin <guro@fb.com>
Subject: Re: [LSF/MM TOPIC] Proactive Memory Reclaim
Date: Tue, 23 Apr 2019 11:26:40 -0700 [thread overview]
Message-ID: <CAHbLzkoLKs32u3_6a9XgtN3nrH-VVVv7pokFg60d2yG6XXi=9A@mail.gmail.com> (raw)
In-Reply-To: <CALvZod5X7d38BO4byaWaKScibsJJPEj8KZx6t5Od1EXRvn_aOg@mail.gmail.com>
On Tue, Apr 23, 2019 at 10:12 AM Shakeel Butt <shakeelb@google.com> wrote:
>
> On Tue, Apr 23, 2019 at 9:50 AM Yang Shi <shy828301@gmail.com> wrote:
> >
> > Hi Shakeel,
> >
> > This sounds interesting. Actually, we have something similar designed
> > in-house (called "cold" page reclaim). But, we mainly targeted to cold
> > page cache rather than anonymous page for the time being, and it does
> > in cgroup scope. We are extending it to anonymous page now.
> >
> > Look forward to discussing with you.
> >
>
> Hi Yang,
>
> Thanks for the info. Is this per-cgroup "cold page reclaim" is
> triggered by the job themselves? Are the jobs trying to avoid memcg
No, it is triggered by admin or cluster management.
> limit reclaim by proactively reclaiming their own memory?
Yes, kind of. And, it also helps to avoid global direct reclaim.
>
> Shakeel
next prev parent reply other threads:[~2019-04-23 18:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 15:30 Shakeel Butt
2019-04-23 15:58 ` Mel Gorman
2019-04-23 16:33 ` Shakeel Butt
2019-04-23 16:49 ` Yang Shi
2019-04-23 17:12 ` Shakeel Butt
2019-04-23 18:26 ` Yang Shi [this message]
2019-04-23 16:08 ` Rik van Riel
2019-04-23 17:04 ` Shakeel Butt
2019-04-23 17:49 ` Johannes Weiner
2019-04-23 17:34 ` Suren Baghdasaryan
2019-04-23 17:31 ` Johannes Weiner
2019-04-24 16:28 ` Christopher Lameter
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='CAHbLzkoLKs32u3_6a9XgtN3nrH-VVVv7pokFg60d2yG6XXi=9A@mail.gmail.com' \
--to=shy828301@gmail.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=riel@surriel.com \
--cc=shakeelb@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