From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with ESMTP id 29C9C6B016B for ; Wed, 7 Sep 2011 00:25:33 -0400 (EDT) From: Glauber Costa Subject: [PATCH v2 9/9] Add documentation about kmem_cgroup Date: Wed, 7 Sep 2011 01:23:19 -0300 Message-Id: <1315369399-3073-10-git-send-email-glommer@parallels.com> In-Reply-To: <1315369399-3073-1-git-send-email-glommer@parallels.com> References: <1315369399-3073-1-git-send-email-glommer@parallels.com> Sender: owner-linux-mm@kvack.org List-ID: To: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org, containers@lists.osdl.org, netdev@vger.kernel.org, xemul@parallels.com, Glauber Costa , "David S. Miller" , Hiroyouki Kamezawa , "Eric W. Biederman" , Randy Dunlap Signed-off-by: Glauber Costa CC: David S. Miller CC: Hiroyouki Kamezawa CC: Eric W. Biederman CC: Randy Dunlap --- Documentation/cgroups/kmem_cgroups.txt | 27 +++++++++++++++++++++++++++ 1 files changed, 27 insertions(+), 0 deletions(-) create mode 100644 Documentation/cgroups/kmem_cgroups.txt diff --git a/Documentation/cgroups/kmem_cgroups.txt b/Documentation/cgroups/kmem_cgroups.txt new file mode 100644 index 0000000..930e069 --- /dev/null +++ b/Documentation/cgroups/kmem_cgroups.txt @@ -0,0 +1,27 @@ +Kernel Memory Cgroup +==================== + +This document briefly describes the kernel memory cgroup, or "kmem cgroup". +Unlike user memory, kernel memory cannot be swapped. This effectively means +that rogue processes can start operations that pin kernel objects permanently +into memory, exhausting resources of all other processes in the system. + +kmem_cgroup main goal is to control the amount of memory a group of processes +can pin at any given point in time. Other uses of this infrastructure are +expected to come up with time. Right now, the only resource effectively limited +are tcp send and receive buffers. + +TCP network buffers +=================== + +TCP network buffers, both on the send and receive sides, can be controlled +by the kmem cgroup. Once a socket is created, it is attached to the cgroup of +the controller process, where it stays until the end of its lifetime. + +Files +===== + kmem.tcp_maxmem: control the maximum amount in bytes that can be used by + tcp sockets inside the cgroup. + + kmem.tcp_current_memory: current amount in bytes used by all sockets in + this cgroup -- 1.7.6 -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org