From: "Daniel Xu" <dxu@dxuuu.xyz>
To: "Tejun Heo" <tj@kernel.org>, "Jonathan Corbet" <corbet@lwn.net>
Cc: "Benjamin Berg" <benjamin@sipsolutions.net>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
"Johannes Weiner" <hannes@cmpxchg.org>
Subject: Re: Memory reclaim protection and cgroup nesting (desktop use)
Date: Wed, 04 Mar 2020 17:29:18 -0800 [thread overview]
Message-ID: <5e0c59bd-ad59-4999-9a41-4239b96b1fc9@www.fastmail.com> (raw)
In-Reply-To: <20200304171051.GK189690@mtj.thefacebook.com>
On Wed, Mar 4, 2020, at 9:10 AM, Tejun Heo wrote:
> On Wed, Mar 04, 2020 at 10:02:31AM -0700, Jonathan Corbet wrote:
> > On Wed, 4 Mar 2020 11:30:44 -0500
> > Tejun Heo <tj@kernel.org> wrote:
> >
> > > > (In a realistic scenario I expect to have swap and then reserving maybe
> > > > a few hundred MiB; DAMON might help with finding good values.)
> > >
> > > What's DAMON?
> >
> > https://lwn.net/Articles/812707/
>
> Ah, thanks a lot for the link. That's neat. For determining workload
> size, we're using senpai:
>
> https://github.com/facebookincubator/senpai
[...]
For reference, senpai is currently deployed as an oomd plugin:
https://github.com/facebookincubator/oomd/blob/master/src/oomd/plugins/Senpai.cpp .
The python version might be a bit out of date -- Johannes probably knows.
next prev parent reply other threads:[~2020-03-05 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 9:44 Memory reclaim protection and cgroup nesting (desktop use) Benjamin Berg
2020-03-04 16:30 ` Tejun Heo
2020-03-04 17:02 ` Jonathan Corbet
2020-03-04 17:10 ` Tejun Heo
2020-03-05 1:29 ` Daniel Xu [this message]
2020-03-05 13:13 ` Benjamin Berg
2020-03-05 14:55 ` Tejun Heo
2020-03-05 15:12 ` Tejun Heo
2020-03-05 15:27 ` Benjamin Berg
2020-03-05 15:39 ` Tejun Heo
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=5e0c59bd-ad59-4999-9a41-4239b96b1fc9@www.fastmail.com \
--to=dxu@dxuuu.xyz \
--cc=benjamin@sipsolutions.net \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).