From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Glauber Costa <glommer@parallels.com>
Cc: linux-kernel@vger.kernel.org, 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, avagin@parallels.com
Subject: Re: [PATCH v4 2/8] socket: initial cgroup code.
Date: Mon, 3 Oct 2011 14:02:30 +0300 [thread overview]
Message-ID: <20111003110230.GC29312@shutemov.name> (raw)
In-Reply-To: <4E8992EF.30001@parallels.com>
On Mon, Oct 03, 2011 at 02:48:15PM +0400, Glauber Costa wrote:
> On 10/03/2011 02:47 PM, Kirill A. Shutemov wrote:
> > On Mon, Oct 03, 2011 at 02:18:37PM +0400, Glauber Costa wrote:
> >> We aim to control the amount of kernel memory pinned at any
> >> time by tcp sockets. To lay the foundations for this work,
> >> this patch adds a pointer to the kmem_cgroup to the socket
> >> structure.
> >>
> >> 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>
> >> ---
> >> include/linux/memcontrol.h | 15 +++++++++++++++
> >> include/net/sock.h | 2 ++
> >> mm/memcontrol.c | 33 +++++++++++++++++++++++++++++++++
> >> net/core/sock.c | 3 +++
> >> 4 files changed, 53 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> >> index 3b535db..2cb9226 100644
> >> --- a/include/linux/memcontrol.h
> >> +++ b/include/linux/memcontrol.h
> >> @@ -395,5 +395,20 @@ mem_cgroup_print_bad_page(struct page *page)
> >> }
> >> #endif
> >>
> >> +#ifdef CONFIG_INET
> >> +struct sock;
> >> +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM
> >> +void sock_update_memcg(struct sock *sk);
> >> +void sock_release_memcg(struct sock *sk);
> >> +
> >> +#else
> >> +static inline void sock_update_memcg(struct sock *sk)
> >> +{
> >> +}
> >> +static inline void sock_release_memcg(struct sock *sk)
> >> +{
> >> +}
> >> +#endif /* CONFIG_CGROUP_MEM_RES_CTLR_KMEM */
> >> +#endif /* CONFIG_INET */
> >> #endif /* _LINUX_MEMCONTROL_H */
> >>
> >> diff --git a/include/net/sock.h b/include/net/sock.h
> >> index 8e4062f..afe1467 100644
> >> --- a/include/net/sock.h
> >> +++ b/include/net/sock.h
> >> @@ -228,6 +228,7 @@ struct sock_common {
> >> * @sk_security: used by security modules
> >> * @sk_mark: generic packet mark
> >> * @sk_classid: this socket's cgroup classid
> >> + * @sk_cgrp: this socket's kernel memory (kmem) cgroup
> >> * @sk_write_pending: a write to stream socket waits to start
> >> * @sk_state_change: callback to indicate change in the state of the sock
> >> * @sk_data_ready: callback to indicate there is data to be processed
> >> @@ -339,6 +340,7 @@ struct sock {
> >> #endif
> >> __u32 sk_mark;
> >> u32 sk_classid;
> >> + struct mem_cgroup *sk_cgrp;
> >> void (*sk_state_change)(struct sock *sk);
> >> void (*sk_data_ready)(struct sock *sk, int bytes);
> >> void (*sk_write_space)(struct sock *sk);
> >> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> >> index 8aaf4ce..08a520e 100644
> >> --- a/mm/memcontrol.c
> >> +++ b/mm/memcontrol.c
> >> @@ -339,6 +339,39 @@ struct mem_cgroup {
> >> spinlock_t pcp_counter_lock;
> >> };
> >>
> >> +/* Writing them here to avoid exposing memcg's inner layout */
> >> +#ifdef CONFIG_CGROUP_MEM_RES_CTLR_KMEM
> >> +#ifdef CONFIG_INET
> >> +#include<net/sock.h>
> >> +
> >> +void sock_update_memcg(struct sock *sk)
> >> +{
> >> + /* right now a socket spends its whole life in the same cgroup */
> >> + BUG_ON(sk->sk_cgrp);
> >
> > Do we really want to panic in this case?
> >
> > What about WARN() + return?
>
> Kirill,
>
> I am keeping this code just to have something workable in between.
> If you take a look at the last patch, this hunk is going away anyway.
>
> So if you don't oppose it, I'll just keep it to avoid rebasing it.
Sorry, but I don't see where you remove BUG_ON().
You remove only cgroup_exclude_rmdir().
--
Kirill A. Shutemov
--
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>
next prev parent reply other threads:[~2011-10-03 11:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 10:18 [PATCH v4 0/8] per-cgroup tcp buffer pressure settings Glauber Costa
2011-10-03 10:18 ` [PATCH v4 1/8] Basic kernel memory functionality for the Memory Controller Glauber Costa
2011-10-03 10:41 ` Kirill A. Shutemov
2011-10-03 10:41 ` Glauber Costa
2011-10-04 0:38 ` KAMEZAWA Hiroyuki
2011-10-03 10:18 ` [PATCH v4 2/8] socket: initial cgroup code Glauber Costa
2011-10-03 10:47 ` Kirill A. Shutemov
2011-10-03 10:48 ` Glauber Costa
2011-10-03 11:02 ` Kirill A. Shutemov [this message]
2011-10-03 11:03 ` Glauber Costa
2011-10-04 0:41 ` KAMEZAWA Hiroyuki
2011-10-03 10:18 ` [PATCH v4 3/8] foundations of per-cgroup memory pressure controlling Glauber Costa
2011-10-03 15:13 ` Andrew Vagin
2011-10-04 0:57 ` KAMEZAWA Hiroyuki
2011-10-04 6:32 ` Glauber Costa
2011-10-04 7:13 ` Glauber Costa
2011-10-03 10:18 ` [PATCH v4 4/8] per-cgroup tcp buffers control Glauber Costa
2011-10-04 1:16 ` KAMEZAWA Hiroyuki
2011-10-04 5:43 ` Glauber Costa
2011-10-03 10:18 ` [PATCH v4 5/8] per-netns ipv4 sysctl_tcp_mem Glauber Costa
2011-10-04 1:18 ` KAMEZAWA Hiroyuki
2011-10-03 10:18 ` [PATCH v4 6/8] tcp buffer limitation: per-cgroup limit Glauber Costa
2011-10-04 1:21 ` KAMEZAWA Hiroyuki
2011-10-04 6:22 ` Glauber Costa
2011-10-03 10:18 ` [PATCH v4 7/8] Display current tcp memory allocation in kmem cgroup Glauber Costa
2011-10-03 12:14 ` Kirill A. Shutemov
2011-10-03 12:19 ` Glauber Costa
2011-10-03 12:25 ` Kirill A. Shutemov
2011-10-03 12:26 ` Glauber Costa
2011-10-03 12:36 ` Kirill A. Shutemov
2011-10-03 12:36 ` Glauber Costa
2011-10-04 9:10 ` Glauber Costa
2011-10-06 8:46 ` Kirill A. Shutemov
2011-10-03 10:18 ` [PATCH v4 8/8] Disable task moving when using kernel memory accounting 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=20111003110230.GC29312@shutemov.name \
--to=kirill@shutemov.name \
--cc=avagin@parallels.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=glommer@parallels.com \
--cc=gthelen@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).