mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: linux-kernel@vger.kernel.org
Cc: lizf@cn.fujitsu.com, kamezawa.hiroyu@jp.fujitsu.com,
	ebiederm@xmission.com, davem@davemloft.net, paul@paulmenage.org,
	gthelen@google.com, netdev@vger.kernel.org, linux-mm@kvack.org,
	kirill@shutemov.name, avagin@parallels.com, devel@openvz.org,
	eric.dumazet@gmail.com, cgroups@vger.kernel.org,
	Glauber Costa <glommer@parallels.com>
Subject: [PATCH v6 07/10] Display current tcp memory allocation in kmem cgroup
Date: Fri, 25 Nov 2011 15:38:13 -0200	[thread overview]
Message-ID: <1322242696-27682-8-git-send-email-glommer@parallels.com> (raw)
In-Reply-To: <1322242696-27682-1-git-send-email-glommer@parallels.com>

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 <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 +
 net/ipv4/tcp_memcg.c             |   21 +++++++++++++++++++++
 2 files changed, 22 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/net/ipv4/tcp_memcg.c b/net/ipv4/tcp_memcg.c
index b3721c3..a1ab613 100644
--- a/net/ipv4/tcp_memcg.c
+++ b/net/ipv4/tcp_memcg.c
@@ -16,6 +16,11 @@ static struct cftype tcp_files[] = {
 		.read_u64 = tcp_cgroup_read,
 		.private = RES_LIMIT,
 	},
+	{
+		.name = "kmem.tcp.usage_in_bytes",
+		.read_u64 = tcp_cgroup_read,
+		.private = RES_USAGE,
+	},
 };
 
 static inline struct tcp_memcontrol *tcp_from_cgproto(struct cg_proto *cg_proto)
@@ -158,6 +163,19 @@ static u64 tcp_read_stat(struct mem_cgroup *memcg, int type, u64 default_val)
 	return res_counter_read_u64(&tcp->tcp_memory_allocated, type);
 }
 
+static u64 tcp_read_usage(struct mem_cgroup *memcg)
+{
+	struct tcp_memcontrol *tcp;
+	struct cg_proto *cg_proto;
+
+	cg_proto = tcp_prot.proto_cgroup(memcg);
+	if (!cg_proto)
+		return atomic_long_read(&tcp_memory_allocated) << PAGE_SHIFT;
+
+	tcp = tcp_from_cgproto(cg_proto);
+	return res_counter_read_u64(&tcp->tcp_memory_allocated, RES_USAGE);
+}
+
 static u64 tcp_cgroup_read(struct cgroup *cont, struct cftype *cft)
 {
 	struct mem_cgroup *memcg = mem_cgroup_from_cont(cont);
@@ -167,6 +185,9 @@ static u64 tcp_cgroup_read(struct cgroup *cont, struct cftype *cft)
 	case RES_LIMIT:
 		val = tcp_read_stat(memcg, RES_LIMIT, RESOURCE_MAX);
 		break;
+	case RES_USAGE:
+		val = tcp_read_usage(memcg);
+		break;
 	default:
 		BUG();
 	}
-- 
1.7.6.4


  parent reply	other threads:[~2011-11-25 17:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-25 17:38 [PATCH v6 00/10] Request for inclusion: per-cgroup tcp memory pressure controls Glauber Costa
2011-11-25 17:38 ` [PATCH v6 01/10] Basic kernel memory functionality for the Memory Controller Glauber Costa
2011-11-28  2:24   ` KAMEZAWA Hiroyuki
2011-11-28 11:03     ` Glauber Costa
2011-11-28 23:55       ` KAMEZAWA Hiroyuki
2011-12-14 16:38   ` Michal Hocko
2011-12-14 16:45     ` Michal Hocko
2011-11-25 17:38 ` [PATCH v6 02/10] foundations of per-cgroup memory pressure controlling Glauber Costa
2011-11-28  2:55   ` KAMEZAWA Hiroyuki
2011-11-29  9:19     ` Glauber Costa
2011-11-25 17:38 ` [PATCH v6 03/10] socket: initial cgroup code Glauber Costa
2011-11-25 17:38 ` [PATCH v6 04/10] Account tcp memory as kernel memory Glauber Costa
2011-11-28  3:14   ` KAMEZAWA Hiroyuki
2011-11-25 17:38 ` [PATCH v6 05/10] per-netns ipv4 sysctl_tcp_mem Glauber Costa
2011-11-25 17:38 ` [PATCH v6 06/10] tcp buffer limitation: per-cgroup limit Glauber Costa
2011-11-28  3:24   ` KAMEZAWA Hiroyuki
2011-11-25 17:38 ` Glauber Costa [this message]
2011-11-28  4:20   ` [PATCH v6 07/10] Display current tcp memory allocation in kmem cgroup KAMEZAWA Hiroyuki
2011-11-25 17:38 ` [PATCH v6 08/10] Display current tcp failcnt " Glauber Costa
2011-11-28  4:21   ` KAMEZAWA Hiroyuki
2011-11-25 17:38 ` [PATCH v6 09/10] Display maximum tcp memory allocation " Glauber Costa
2011-11-28  4:22   ` KAMEZAWA Hiroyuki
2011-11-25 17:38 ` [PATCH v6 10/10] Disable task moving when using kernel memory accounting Glauber Costa
2011-11-28  4:32   ` KAMEZAWA Hiroyuki
2011-11-28 11:00     ` 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=1322242696-27682-8-git-send-email-glommer@parallels.com \
    --to=glommer@parallels.com \
    --cc=avagin@parallels.com \
    --cc=cgroups@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=devel@openvz.org \
    --cc=ebiederm@xmission.com \
    --cc=eric.dumazet@gmail.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

all inboxes | Powered by JetHome®