All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lord Glauber Costa of Sealand <glommer@parallels.com>
To: <lsf-pc@lists.linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	<linux-fsdevel@vger.kernel.org>
Subject: [ATTEND][LSF/MM TOPIC] the memory controller
Date: Mon, 28 Jan 2013 12:11:41 +0400	[thread overview]
Message-ID: <510632BD.3010702@parallels.com> (raw)

Hi,

I've been working actively over the past year with the memory
controller, in particular its usage to track special bits of interest in
kernel memory land. As this work progress, I'd like to propose and
participate in the following discussions in the upcoming LSF/MM:

* memcg kmem shrinking: as memory pressure appears within memcg, we need
to shrink some of the slab objects attributed to the group, maintaining
isolation as much as possible. The scheme also needs to allow for global
reclaim to keep working reliably, and of course, be memory efficient.

* 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.

I also believe I will be able to help with general discussions
concerning the memory controller in general, since pursuing ways to
improve it - specially efficiency-wise - seems to be a recurring (and
thankfully fruitful) topic.


WARNING: multiple messages have this Message-ID (diff)
From: Lord Glauber Costa of Sealand <glommer@parallels.com>
To: lsf-pc@lists.linux-foundation.org,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	linux-fsdevel@vger.kernel.org
Subject: [ATTEND][LSF/MM TOPIC] the memory controller
Date: Mon, 28 Jan 2013 12:11:41 +0400	[thread overview]
Message-ID: <510632BD.3010702@parallels.com> (raw)

Hi,

I've been working actively over the past year with the memory
controller, in particular its usage to track special bits of interest in
kernel memory land. As this work progress, I'd like to propose and
participate in the following discussions in the upcoming LSF/MM:

* memcg kmem shrinking: as memory pressure appears within memcg, we need
to shrink some of the slab objects attributed to the group, maintaining
isolation as much as possible. The scheme also needs to allow for global
reclaim to keep working reliably, and of course, be memory efficient.

* 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.

I also believe I will be able to help with general discussions
concerning the memory controller in general, since pursuing ways to
improve it - specially efficiency-wise - seems to be a recurring (and
thankfully fruitful) topic.

--
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>

             reply	other threads:[~2013-01-28  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28  8:11 Lord Glauber Costa of Sealand [this message]
2013-01-28  8:11 ` [ATTEND][LSF/MM TOPIC] the memory controller Lord Glauber Costa of Sealand
2013-02-09  5:25 ` Michel Lespinasse
2013-04-11  3:27 ` Glauber Costa
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=510632BD.3010702@parallels.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.