From: Michel Lespinasse <walken@google.com>
To: Lord Glauber Costa of Sealand <glommer@parallels.com>
Cc: lsf-pc@lists.linux-foundation.org,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [ATTEND][LSF/MM TOPIC] the memory controller
Date: Fri, 8 Feb 2013 21:25:32 -0800 [thread overview]
Message-ID: <CANN689FNsmFfHX6zqnefE9yzHBed1tXi6ppPzOkcxBZgCLYg2A@mail.gmail.com> (raw)
In-Reply-To: <510632BD.3010702@parallels.com>
On Mon, Jan 28, 2013 at 12:11 AM, Lord Glauber Costa of Sealand
<glommer@parallels.com> wrote:
> * memcg/global oom handling: I believe that the OOM killer could be
> significantly improved to allow for more deterministic killing of tasks,
> specially in containers scenarios where memcg is heavily deployed. In
> some situations, a group encompasses a whole service, and under
> pressure, it would be better to shut down the group altogether with all
> its tasks, while in others it would be better to keep the current
> behavior of shooting down a single task.
We at Google have some OOM wish-list as well:
- having an option to kill the entire cgroup when a contained task is
selected to die;
- recursive setting of OOM kill priorities in a cgroup hierarchy
I am frankly not the best person to talk about this; however if this
topic was selected I could plan for it and bring on a few notes :)
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-02-09 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 8:11 [ATTEND][LSF/MM TOPIC] the memory controller Lord Glauber Costa of Sealand
2013-02-09 5:25 ` Michel Lespinasse [this message]
2013-04-11 3:27 ` Glauber Costa
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=CANN689FNsmFfHX6zqnefE9yzHBed1tXi6ppPzOkcxBZgCLYg2A@mail.gmail.com \
--to=walken@google.com \
--cc=glommer@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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).