On Fri, 25 Nov 2011 15:38:07 -0200
Glauber Costa wrote:
> This patch lays down the foundation for the kernel memory component
> of the Memory Controller.
>
> As of today, I am only laying down the following files:
>
> * memory.independent_kmem_limit
> * memory.kmem.limit_in_bytes (currently i
On Fri, 25 Nov 2011 15:38:08 -0200
Glauber Costa wrote:
> This patch replaces all uses of struct sock fields' memory_pressure,
> memory_allocated, sockets_allocated, and sysctl_mem to acessor
> macros. Those macros can either receive a socket argument, or a mem_cgroup
> argument, depending on the
Some nitpicks.
On Fri, 25 Nov 2011 15:38:10 -0200
Glauber Costa wrote:
> Now that we account and control tcp memory buffers memory for pressure
> controlling purposes, display this information as part of the normal memcg
> files and other usages.
>
> +extern struct mem_cgroup *mem_cgroup_fro
some comments.
On Fri, 25 Nov 2011 15:38:12 -0200
Glauber Costa wrote:
> This patch uses the "tcp.limit_in_bytes" field of the kmem_cgroup to
> effectively control the amount of kernel memory pinned by a cgroup.
>
> This value is ignored in the root cgroup, and in all others,
> caps the value
On Fri, 25 Nov 2011 15:38:13 -0200
Glauber Costa wrote:
> This patch introduces kmem.tcp.usage_in_bytes file, living in the
> kmem_cgroup filesystem. It is a simple read-only file that displays the
> amount of kernel memory currently consumed by the cgroup.
>
> Signed-off-by: Glauber Costa
> CC
On Fri, 25 Nov 2011 15:38:14 -0200
Glauber Costa wrote:
> This patch introduces kmem.tcp.failcnt file, living in the
> kmem_cgroup filesystem. Following the pattern in the other
> memcg resources, this files keeps a counter of how many times
> allocation failed due to limits being hit in this cgr
On Fri, 25 Nov 2011 15:38:15 -0200
Glauber Costa wrote:
> This patch introduces kmem.tcp.max_usage_in_bytes file, living in the
> kmem_cgroup filesystem. The root cgroup will display a value equal
> to RESOURCE_MAX. This is to avoid introducing any locking schemes in
> the network paths when cgro
On Fri, 25 Nov 2011 15:38:16 -0200
Glauber Costa wrote:
> Since this code is still experimental, we are leaving the exact
> details of how to move tasks between cgroups when kernel memory
> accounting is used as future work.
>
> For now, we simply disallow movement if there are any pending
> acc
