linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: linux-kernel@vger.kernel.org
Cc: paul@paulmenage.org, lizf@cn.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, ebiederm@xmission.com,
	davem@davemloft.net, gthelen@google.com, netdev@vger.kernel.org,
	linux-mm@kvack.org, kirill@shutemov.name, avagin@parallels.com,
	devel@openvz.org, Glauber Costa <glommer@parallels.com>
Subject: [PATCH v6 7/8] Display current tcp memory allocation in kmem cgroup
Date: Mon, 10 Oct 2011 14:24:27 +0400	[thread overview]
Message-ID: <1318242268-2234-8-git-send-email-glommer@parallels.com> (raw)
In-Reply-To: <1318242268-2234-1-git-send-email-glommer@parallels.com>

This patch introduces kmem.tcp_current_memory 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 <glommer@parallels.com>
CC: David S. Miller <davem@davemloft.net>
CC: Hiroyouki Kamezawa <kamezawa.hiroyu@jp.fujitsu.com>
CC: Eric W. Biederman <ebiederm@xmission.com>
---
 Documentation/cgroups/memory.txt |    1 +
 mm/memcontrol.c                  |    5 +++++
 2 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
index c1db134..00f1a88 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -79,6 +79,7 @@ Brief summary of control files.
  memory.independent_kmem_limit	 # select whether or not kernel memory limits are
 				   independent of user limits
  memory.kmem.tcp.limit_in_bytes  # set/show hard limit for tcp buf memory
+ memory.kmem.tcp.usage_in_bytes  # show current tcp buf memory allocation
 
 1. History
 
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 60e0ec0..ca08be2 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -543,6 +543,11 @@ static struct cftype tcp_files[] = {
 		.read_u64 = mem_cgroup_read,
 		.private = MEMFILE_PRIVATE(_KMEM_TCP, RES_LIMIT),
 	},
+	{
+		.name = "kmem.tcp.usage_in_bytes",
+		.read_u64 = mem_cgroup_read,
+		.private = MEMFILE_PRIVATE(_KMEM_TCP, RES_USAGE),
+	},
 };
 
 static void tcp_create_cgroup(struct mem_cgroup *cg, struct cgroup_subsys *ss)
-- 
1.7.6.4

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2011-10-10 10:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 10:24 [PATCH v6 0/8] per-cgroup tcp memory pressure handling Glauber Costa
2011-10-10 10:24 ` [PATCH v6 1/8] Basic kernel memory functionality for the Memory Controller Glauber Costa
2011-10-13  5:44   ` KAMEZAWA Hiroyuki
2011-10-13  7:18   ` Greg Thelen
2011-10-13  8:19     ` Glauber Costa
2011-10-10 10:24 ` [PATCH v6 2/8] socket: initial cgroup code Glauber Costa
2011-10-10 10:24 ` [PATCH v6 3/8] foundations of per-cgroup memory pressure controlling Glauber Costa
2011-10-13  5:53   ` KAMEZAWA Hiroyuki
2011-10-13  8:25     ` Glauber Costa
2011-10-10 10:24 ` [PATCH v6 4/8] per-cgroup tcp buffers control Glauber Costa
2011-10-13  5:56   ` KAMEZAWA Hiroyuki
2011-10-10 10:24 ` [PATCH v6 5/8] per-netns ipv4 sysctl_tcp_mem Glauber Costa
2011-10-10 10:24 ` [PATCH v6 6/8] tcp buffer limitation: per-cgroup limit Glauber Costa
2011-10-13  5:58   ` KAMEZAWA Hiroyuki
2011-10-10 10:24 ` Glauber Costa [this message]
2011-10-13  5:59   ` [PATCH v6 7/8] Display current tcp memory allocation in kmem cgroup KAMEZAWA Hiroyuki
2011-10-10 10:24 ` [PATCH v6 8/8] Disable task moving when using kernel memory accounting Glauber Costa
2011-10-13  6:00   ` KAMEZAWA Hiroyuki

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=1318242268-2234-8-git-send-email-glommer@parallels.com \
    --to=glommer@parallels.com \
    --cc=avagin@parallels.com \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=gthelen@google.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul@paulmenage.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