From: Vladimir Davydov <vdavydov-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
Cc: Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
Greg Thelen <gthelen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch 2/2] mm: memcontrol: default hierarchy interface for memory
Date: Wed, 14 Jan 2015 17:28:41 +0300 [thread overview]
Message-ID: <20150114142841.GE11264@esperanza> (raw)
In-Reply-To: <1420776904-8559-2-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
On Thu, Jan 08, 2015 at 11:15:04PM -0500, Johannes Weiner wrote:
> - memory.low configures the lower end of the cgroup's expected
> memory consumption range. The kernel considers memory below that
> boundary to be a reserve - the minimum that the workload needs in
> order to make forward progress - and generally avoids reclaiming
> it, unless there is an imminent risk of entering an OOM situation.
AFAICS, if a cgroup cannot be shrunk back to its low limit (e.g.
because it consumes anon memory, and there's no swap), it will get on
with it. Is it considered to be a problem? Are there any plans to fix
it, e.g. by invoking OOM-killer in a cgroup that is above its low limit
if we fail to reclaim from it?
Thanks,
Vladimir
next prev parent reply other threads:[~2015-01-14 14:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 4:15 [patch 1/2] mm: page_counter: pull "-1" handling out of page_counter_memparse() Johannes Weiner
2015-01-09 4:15 ` [patch 2/2] mm: memcontrol: default hierarchy interface for memory Johannes Weiner
[not found] ` <1420776904-8559-1-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2015-01-09 4:15 ` Johannes Weiner
2015-01-13 15:59 ` [patch 1/2] mm: page_counter: pull "-1" handling out of page_counter_memparse() Vladimir Davydov
[not found] ` <1420776904-8559-2-git-send-email-hannes@cmpxchg.org>
2015-01-12 23:37 ` [patch 2/2] mm: memcontrol: default hierarchy interface for memory Andrew Morton
2015-01-13 15:50 ` Johannes Weiner
[not found] ` <20150112153716.d54e90c634b70d49e8bb8688-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2015-01-13 15:50 ` Johannes Weiner
[not found] ` <20150113155040.GC8180@phnom.home.cmpxchg.org>
[not found] ` <20150113155040.GC8180-HTCKtW7iVlxqnrmGgq4/JMIURNUf+fel@public.gmane.org>
2015-01-13 20:52 ` Andrew Morton
2015-01-13 21:44 ` Johannes Weiner
[not found] ` <20150113125258.0d7d3da2920234fc9461ef69-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2015-01-13 21:44 ` Johannes Weiner
2015-01-13 23:20 ` Greg Thelen
[not found] ` <xr93a91mz2s7.fsf-aSPv4SP+Du0KgorLzL7FmE7CuiCeIGUxQQ4Iyu8u01E@public.gmane.org>
2015-01-14 16:01 ` Johannes Weiner
2015-01-14 16:01 ` Johannes Weiner
[not found] ` <1420776904-8559-2-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2015-01-14 14:28 ` Vladimir Davydov [this message]
2015-01-14 15:34 ` Michal Hocko
[not found] ` <20150114153425.GF4706-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2015-01-14 17:19 ` Johannes Weiner
2015-01-14 17:19 ` Johannes Weiner
[not found] ` <20150114171944.GB32040@phnom.home.cmpxchg.org>
2015-01-15 17:08 ` Michal Hocko
2015-01-14 16:17 ` Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2015-01-20 15:31 [patch 0/2] mm: memcontrol: default hierarchy interface for memory v2 Johannes Weiner
2015-01-20 15:31 ` [patch 2/2] mm: memcontrol: default hierarchy interface for memory Johannes Weiner
2015-01-20 16:31 ` Michal Hocko
[not found] ` <1421767915-14232-3-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2015-02-23 11:13 ` Sasha Levin
[not found] ` <54EB0B70.2040902-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2015-02-23 14:28 ` Michal Hocko
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=20150114142841.GE11264@esperanza \
--to=vdavydov-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=gthelen-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@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