All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: Jason Baron <jbaron@redhat.com>
Cc: davem@davemloft.net, linux-kernel@vger.kernel.org,
	paul@paulmenage.org, lizf@cn.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, ebiederm@xmission.com,
	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
Subject: Re: [PATCH v9 3/9] socket: initial cgroup code.
Date: Fri, 23 Dec 2011 12:57:49 +0400	[thread overview]
Message-ID: <4EF4428D.6010103@parallels.com> (raw)
In-Reply-To: <20111222211028.GB3916@redhat.com>

On 12/23/2011 01:10 AM, Jason Baron wrote:
> On Mon, Dec 12, 2011 at 11:47:03AM +0400, Glauber Costa wrote:
>> +
>> +static bool mem_cgroup_is_root(struct mem_cgroup *memcg);
>> +void sock_update_memcg(struct sock *sk)
>> +{
>> +	/* A socket spends its whole life in the same cgroup */
>> +	if (sk->sk_cgrp) {
>> +		WARN_ON(1);
>> +		return;
>> +	}
>> +	if (static_branch(&memcg_socket_limit_enabled)) {
>> +		struct mem_cgroup *memcg;
>> +
>> +		BUG_ON(!sk->sk_prot->proto_cgroup);
>> +
>> +		rcu_read_lock();
>> +		memcg = mem_cgroup_from_task(current);
>> +		if (!mem_cgroup_is_root(memcg)) {
>> +			mem_cgroup_get(memcg);
>> +			sk->sk_cgrp = sk->sk_prot->proto_cgroup(memcg);
>> +		}
>> +		rcu_read_unlock();
>> +	}
>> +}
>> +EXPORT_SYMBOL(sock_update_memcg);
>> +
>> +void sock_release_memcg(struct sock *sk)
>> +{
>> +	if (static_branch(&memcg_socket_limit_enabled)&&  sk->sk_cgrp) {
>> +		struct mem_cgroup *memcg;
>> +		WARN_ON(!sk->sk_cgrp->memcg);
>> +		memcg = sk->sk_cgrp->memcg;
>> +		mem_cgroup_put(memcg);
>> +	}
>> +}
>
> Hi Glauber,
>
> I think for 'sock_release_memcg()', you want:
>
> static inline sock_release_memcg(sk)
> {
> 	if (static_branch())
> 		__sock_release_memcg();
> }
>
> And then re-define the current sock_release_memcg ->  __sock_release_memcg().
> In that way the straight line path is a single no-op. As currently
> written, there is function call and then an immediate return.
>

Hello Jason,

Thanks for the tip. I may be wrong here, but I don't think that the 
release performance matters to that level. But your suggestion seems 
good nevertheless. Since this is already sitting on a tree, would you 
like to send a patch for that?

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: Jason Baron <jbaron@redhat.com>
Cc: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
	<paul@paulmenage.org>, <lizf@cn.fujitsu.com>,
	<kamezawa.hiroyu@jp.fujitsu.com>, <ebiederm@xmission.com>,
	<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>
Subject: Re: [PATCH v9 3/9] socket: initial cgroup code.
Date: Fri, 23 Dec 2011 12:57:49 +0400	[thread overview]
Message-ID: <4EF4428D.6010103@parallels.com> (raw)
In-Reply-To: <20111222211028.GB3916@redhat.com>

On 12/23/2011 01:10 AM, Jason Baron wrote:
> On Mon, Dec 12, 2011 at 11:47:03AM +0400, Glauber Costa wrote:
>> +
>> +static bool mem_cgroup_is_root(struct mem_cgroup *memcg);
>> +void sock_update_memcg(struct sock *sk)
>> +{
>> +	/* A socket spends its whole life in the same cgroup */
>> +	if (sk->sk_cgrp) {
>> +		WARN_ON(1);
>> +		return;
>> +	}
>> +	if (static_branch(&memcg_socket_limit_enabled)) {
>> +		struct mem_cgroup *memcg;
>> +
>> +		BUG_ON(!sk->sk_prot->proto_cgroup);
>> +
>> +		rcu_read_lock();
>> +		memcg = mem_cgroup_from_task(current);
>> +		if (!mem_cgroup_is_root(memcg)) {
>> +			mem_cgroup_get(memcg);
>> +			sk->sk_cgrp = sk->sk_prot->proto_cgroup(memcg);
>> +		}
>> +		rcu_read_unlock();
>> +	}
>> +}
>> +EXPORT_SYMBOL(sock_update_memcg);
>> +
>> +void sock_release_memcg(struct sock *sk)
>> +{
>> +	if (static_branch(&memcg_socket_limit_enabled)&&  sk->sk_cgrp) {
>> +		struct mem_cgroup *memcg;
>> +		WARN_ON(!sk->sk_cgrp->memcg);
>> +		memcg = sk->sk_cgrp->memcg;
>> +		mem_cgroup_put(memcg);
>> +	}
>> +}
>
> Hi Glauber,
>
> I think for 'sock_release_memcg()', you want:
>
> static inline sock_release_memcg(sk)
> {
> 	if (static_branch())
> 		__sock_release_memcg();
> }
>
> And then re-define the current sock_release_memcg ->  __sock_release_memcg().
> In that way the straight line path is a single no-op. As currently
> written, there is function call and then an immediate return.
>

Hello Jason,

Thanks for the tip. I may be wrong here, but I don't think that the 
release performance matters to that level. But your suggestion seems 
good nevertheless. Since this is already sitting on a tree, would you 
like to send a patch for that?


WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: Jason Baron <jbaron@redhat.com>
Cc: <davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
	<paul@paulmenage.org>, <lizf@cn.fujitsu.com>,
	<kamezawa.hiroyu@jp.fujitsu.com>, <ebiederm@xmission.com>,
	<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>
Subject: Re: [PATCH v9 3/9] socket: initial cgroup code.
Date: Fri, 23 Dec 2011 12:57:49 +0400	[thread overview]
Message-ID: <4EF4428D.6010103@parallels.com> (raw)
In-Reply-To: <20111222211028.GB3916@redhat.com>

On 12/23/2011 01:10 AM, Jason Baron wrote:
> On Mon, Dec 12, 2011 at 11:47:03AM +0400, Glauber Costa wrote:
>> +
>> +static bool mem_cgroup_is_root(struct mem_cgroup *memcg);
>> +void sock_update_memcg(struct sock *sk)
>> +{
>> +	/* A socket spends its whole life in the same cgroup */
>> +	if (sk->sk_cgrp) {
>> +		WARN_ON(1);
>> +		return;
>> +	}
>> +	if (static_branch(&memcg_socket_limit_enabled)) {
>> +		struct mem_cgroup *memcg;
>> +
>> +		BUG_ON(!sk->sk_prot->proto_cgroup);
>> +
>> +		rcu_read_lock();
>> +		memcg = mem_cgroup_from_task(current);
>> +		if (!mem_cgroup_is_root(memcg)) {
>> +			mem_cgroup_get(memcg);
>> +			sk->sk_cgrp = sk->sk_prot->proto_cgroup(memcg);
>> +		}
>> +		rcu_read_unlock();
>> +	}
>> +}
>> +EXPORT_SYMBOL(sock_update_memcg);
>> +
>> +void sock_release_memcg(struct sock *sk)
>> +{
>> +	if (static_branch(&memcg_socket_limit_enabled)&&  sk->sk_cgrp) {
>> +		struct mem_cgroup *memcg;
>> +		WARN_ON(!sk->sk_cgrp->memcg);
>> +		memcg = sk->sk_cgrp->memcg;
>> +		mem_cgroup_put(memcg);
>> +	}
>> +}
>
> Hi Glauber,
>
> I think for 'sock_release_memcg()', you want:
>
> static inline sock_release_memcg(sk)
> {
> 	if (static_branch())
> 		__sock_release_memcg();
> }
>
> And then re-define the current sock_release_memcg ->  __sock_release_memcg().
> In that way the straight line path is a single no-op. As currently
> written, there is function call and then an immediate return.
>

Hello Jason,

Thanks for the tip. I may be wrong here, but I don't think that the 
release performance matters to that level. But your suggestion seems 
good nevertheless. Since this is already sitting on a tree, would you 
like to send a patch for that?

--
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>

  reply	other threads:[~2011-12-23  8:57 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-12  7:47 [PATCH v9 0/9] Request for inclusion: per-cgroup tcp memory pressure controls Glauber Costa
2011-12-12  7:47 ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 1/9] Basic kernel memory functionality for the Memory Controller Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-14 17:04   ` Michal Hocko
2011-12-14 17:04     ` Michal Hocko
     [not found]     ` <20111214170447.GB4856-VqjxzfR4DlwKmadIfiO5sKVXKuFTiq87@public.gmane.org>
2011-12-15 12:29       ` Glauber Costa
2011-12-15 12:29         ` Glauber Costa
2011-12-15 12:29         ` Glauber Costa
2011-12-15 12:29         ` Glauber Costa
2011-12-16 12:32         ` Michal Hocko
2011-12-16 12:32           ` Michal Hocko
2011-12-16 13:02           ` Glauber Costa
2011-12-16 13:02             ` Glauber Costa
2011-12-16 13:02             ` Glauber Costa
     [not found]             ` <4EEB417B.8000508-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-16 13:30               ` Michal Hocko
2011-12-16 13:30                 ` Michal Hocko
2011-12-16 13:30                 ` Michal Hocko
     [not found]   ` <1323676029-5890-2-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-16  6:20     ` Greg Thelen
2011-12-16  6:20       ` Greg Thelen
2011-12-16  6:20       ` Greg Thelen
2011-12-12  7:47 ` [PATCH v9 2/9] foundations of per-cgroup memory pressure controlling Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 3/9] socket: initial cgroup code Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-22 21:10   ` Jason Baron
2011-12-22 21:10     ` Jason Baron
2011-12-23  8:57     ` Glauber Costa [this message]
2011-12-23  8:57       ` Glauber Costa
2011-12-23  8:57       ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 4/9] tcp memory pressure controls Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 5/9] per-netns ipv4 sysctl_tcp_mem Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 6/9] tcp buffer limitation: per-cgroup limit Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 7/9] Display current tcp memory allocation in kmem cgroup Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 8/9] Display current tcp failcnt " Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-12  7:47 ` [PATCH v9 9/9] Display maximum tcp memory allocation " Glauber Costa
2011-12-12  7:47   ` Glauber Costa
2011-12-13  0:07 ` [PATCH v9 0/9] Request for inclusion: per-cgroup tcp memory pressure controls David Miller
2011-12-13  0:07   ` David Miller
2011-12-13 13:49   ` Christoph Paasch
2011-12-13 13:49     ` Christoph Paasch
2011-12-13 13:49     ` Christoph Paasch
2011-12-13 13:59     ` Eric Dumazet
2011-12-13 13:59       ` Eric Dumazet
2011-12-13 13:59       ` Eric Dumazet
2011-12-13 18:45       ` David Miller
2011-12-13 18:45         ` David Miller
2011-12-13 20:11       ` Glauber Costa
2011-12-13 20:11         ` Glauber Costa
2011-12-13 20:11         ` Glauber Costa
2011-12-15  5:40 ` KAMEZAWA Hiroyuki
2011-12-15  5:40   ` KAMEZAWA Hiroyuki
2011-12-15  5:40   ` KAMEZAWA Hiroyuki
2011-12-15  5:48   ` David Miller
2011-12-15  5:48     ` David Miller
2011-12-15  6:48     ` Glauber Costa
2011-12-15  6:48       ` Glauber Costa
2011-12-15  6:48       ` 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=4EF4428D.6010103@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=jbaron@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.