From: Jonathan Corbet <corbet-T1hC0tSOHrs@public.gmane.org>
To: Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Benjamin Berg <benjamin-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
Subject: Re: Memory reclaim protection and cgroup nesting (desktop use)
Date: Wed, 4 Mar 2020 10:02:31 -0700 [thread overview]
Message-ID: <20200304100231.2213a982@lwn.net> (raw)
In-Reply-To: <20200304163044.GF189690-146+VewaZzwNjtGbbfXrCEEOCMrvLtNR@public.gmane.org>
On Wed, 4 Mar 2020 11:30:44 -0500
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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/
jon
next prev parent reply other threads:[~2020-03-04 17:02 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
[not found] ` <d4826b9e568f1ab7df19f94c409df11956a8e262.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2020-03-04 16:30 ` Tejun Heo
[not found] ` <20200304163044.GF189690-146+VewaZzwNjtGbbfXrCEEOCMrvLtNR@public.gmane.org>
2020-03-04 17:02 ` Jonathan Corbet [this message]
[not found] ` <20200304100231.2213a982-T1hC0tSOHrs@public.gmane.org>
2020-03-04 17:10 ` Tejun Heo
[not found] ` <20200304171051.GK189690-146+VewaZzwNjtGbbfXrCEEOCMrvLtNR@public.gmane.org>
2020-03-05 1:29 ` Daniel Xu
2020-03-05 13:13 ` Benjamin Berg
[not found] ` <4d3e00457bba40b25f3ac4fd376ba7306ffc4e68.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2020-03-05 14:55 ` Tejun Heo
[not found] ` <20200305145554.GA5897-146+VewaZzwNjtGbbfXrCEEOCMrvLtNR@public.gmane.org>
2020-03-05 15:12 ` Tejun Heo
2020-03-05 15:27 ` Benjamin Berg
[not found] ` <7ce3aa9cf6f7501ce2ce6057a03a40cd5e126efd.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
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=20200304100231.2213a982@lwn.net \
--to=corbet-t1hc0tsohrs@public.gmane.org \
--cc=benjamin-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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