[ATTEND][LSF/MM TOPIC] the memory controller

[Lord Glauber Costa of Sealand <glommer@parallels.com>]

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>