From: Glauber Costa <glommer@parallels.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, lizf@cn.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, eric.dumazet@gmail.com,
cgroups@vger.kernel.org, hannes@cmpxchg.org, mhocko@suse.cz,
Paul Menage <paul@paulmenage.org>
Subject: Re: [PATCH v8 1/9] Basic kernel memory functionality for the Memory Controller
Date: Fri, 9 Dec 2011 12:48:16 -0200 [thread overview]
Message-ID: <4EE21FB0.5090006@parallels.com> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6D8AF0D@saturn3.aculab.com>
On 12/09/2011 12:44 PM, David Laight wrote:
>
>> How about this?
>>
>> val = !!val;
>>
>> /*
>> * This follows the same hierarchy restrictions than
>> * mem_cgroup_hierarchy_write()
>> */
>> if (!parent || !parent->use_hierarchy) {
>> if (list_empty(&cgroup->children))
>> memcg->kmem_independent_accounting = val;
>> else
>> return -EBUSY;
>> }
>> else
>> return -EINVAL;
>>
>> return 0;
>
> Inverting the tests gives easier to read code:
>
> if (parent&& parent->user_hierarchy)
> return -EINVAL;
> if (!list_empty(&cgroup->children))
> return -EBUSY;
> memcg->kmem_independent_accounting = val != 0;
> return 0;
On the other hand, inconsistent with mem_cgroup_hierarchy_write(), which
applies the logic in the same way I did here.
> NFI about the logic...
> On the face of it the tests don't seem related to each other
> or to the assignment!
How so?
If parent's use_hierarchy is set, we can't set this value (we need to
have a parent for that to even matter).
We also can't set it if we already have any children - otherwise all the
on-the-fly adjustments become hell-on-earth.
As for = val != 0, sorry, but I completely disagree this is easier than
!!val. Not to mention the !!val notation is already pretty widespread in
the kernel.
> David
>
>
>
>
> --
> 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=ilto:"dont@kvack.org"> email@kvack.org</a>
--
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: David Laight <David.Laight@ACULAB.COM>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
<linux-kernel@vger.kernel.org>, <lizf@cn.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>,
<eric.dumazet@gmail.com>, <cgroups@vger.kernel.org>,
<hannes@cmpxchg.org>, <mhocko@suse.cz>,
Paul Menage <paul@paulmenage.org>
Subject: Re: [PATCH v8 1/9] Basic kernel memory functionality for the Memory Controller
Date: Fri, 9 Dec 2011 12:48:16 -0200 [thread overview]
Message-ID: <4EE21FB0.5090006@parallels.com> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6D8AF0D@saturn3.aculab.com>
On 12/09/2011 12:44 PM, David Laight wrote:
>
>> How about this?
>>
>> val = !!val;
>>
>> /*
>> * This follows the same hierarchy restrictions than
>> * mem_cgroup_hierarchy_write()
>> */
>> if (!parent || !parent->use_hierarchy) {
>> if (list_empty(&cgroup->children))
>> memcg->kmem_independent_accounting = val;
>> else
>> return -EBUSY;
>> }
>> else
>> return -EINVAL;
>>
>> return 0;
>
> Inverting the tests gives easier to read code:
>
> if (parent&& parent->user_hierarchy)
> return -EINVAL;
> if (!list_empty(&cgroup->children))
> return -EBUSY;
> memcg->kmem_independent_accounting = val != 0;
> return 0;
On the other hand, inconsistent with mem_cgroup_hierarchy_write(), which
applies the logic in the same way I did here.
> NFI about the logic...
> On the face of it the tests don't seem related to each other
> or to the assignment!
How so?
If parent's use_hierarchy is set, we can't set this value (we need to
have a parent for that to even matter).
We also can't set it if we already have any children - otherwise all the
on-the-fly adjustments become hell-on-earth.
As for = val != 0, sorry, but I completely disagree this is easier than
!!val. Not to mention the !!val notation is already pretty widespread in
the kernel.
> David
>
>
>
>
> --
> 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=ilto:"dont@kvack.org"> email@kvack.org</a>
WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
<linux-kernel@vger.kernel.org>, <lizf@cn.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>,
<eric.dumazet@gmail.com>, <cgroups@vger.kernel.org>,
<hannes@cmpxchg.org>, <mhocko@suse.cz>,
Paul Menage <paul@paulmenage.org>
Subject: Re: [PATCH v8 1/9] Basic kernel memory functionality for the Memory Controller
Date: Fri, 9 Dec 2011 12:48:16 -0200 [thread overview]
Message-ID: <4EE21FB0.5090006@parallels.com> (raw)
In-Reply-To: <AE90C24D6B3A694183C094C60CF0A2F6D8AF0D@saturn3.aculab.com>
On 12/09/2011 12:44 PM, David Laight wrote:
>
>> How about this?
>>
>> val = !!val;
>>
>> /*
>> * This follows the same hierarchy restrictions than
>> * mem_cgroup_hierarchy_write()
>> */
>> if (!parent || !parent->use_hierarchy) {
>> if (list_empty(&cgroup->children))
>> memcg->kmem_independent_accounting = val;
>> else
>> return -EBUSY;
>> }
>> else
>> return -EINVAL;
>>
>> return 0;
>
> Inverting the tests gives easier to read code:
>
> if (parent&& parent->user_hierarchy)
> return -EINVAL;
> if (!list_empty(&cgroup->children))
> return -EBUSY;
> memcg->kmem_independent_accounting = val != 0;
> return 0;
On the other hand, inconsistent with mem_cgroup_hierarchy_write(), which
applies the logic in the same way I did here.
> NFI about the logic...
> On the face of it the tests don't seem related to each other
> or to the assignment!
How so?
If parent's use_hierarchy is set, we can't set this value (we need to
have a parent for that to even matter).
We also can't set it if we already have any children - otherwise all the
on-the-fly adjustments become hell-on-earth.
As for = val != 0, sorry, but I completely disagree this is easier than
!!val. Not to mention the !!val notation is already pretty widespread in
the kernel.
> David
>
>
>
>
> --
> 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=ilto:"dont@kvack.org"> email@kvack.org</a>
--
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-12-09 14:48 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 21:34 [PATCH v8 0/9] per-cgroup tcp memory pressure controls Glauber Costa
2011-12-05 21:34 ` Glauber Costa
2011-12-05 21:34 ` [PATCH v8 1/9] Basic kernel memory functionality for the Memory Controller Glauber Costa
2011-12-05 21:34 ` Glauber Costa
2011-12-09 1:21 ` KAMEZAWA Hiroyuki
2011-12-09 1:21 ` KAMEZAWA Hiroyuki
[not found] ` <20111209102113.cdb85da8.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2011-12-09 12:40 ` Glauber Costa
2011-12-09 12:40 ` Glauber Costa
2011-12-09 12:40 ` Glauber Costa
2011-12-09 12:40 ` Glauber Costa
2011-12-09 14:37 ` Glauber Costa
2011-12-09 14:37 ` Glauber Costa
2011-12-09 14:37 ` Glauber Costa
2011-12-09 14:37 ` Glauber Costa
2011-12-09 14:44 ` David Laight
2011-12-09 14:44 ` David Laight
2011-12-09 14:44 ` David Laight
2011-12-09 14:48 ` Glauber Costa [this message]
2011-12-09 14:48 ` Glauber Costa
2011-12-09 14:48 ` Glauber Costa
2011-12-12 0:34 ` KAMEZAWA Hiroyuki
2011-12-12 0:34 ` KAMEZAWA Hiroyuki
2011-12-12 0:34 ` KAMEZAWA Hiroyuki
2011-12-05 21:34 ` [PATCH v8 2/9] foundations of per-cgroup memory pressure controlling Glauber Costa
2011-12-05 21:34 ` Glauber Costa
[not found] ` <1323120903-2831-3-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-09 1:24 ` KAMEZAWA Hiroyuki
2011-12-09 1:24 ` KAMEZAWA Hiroyuki
2011-12-09 1:24 ` KAMEZAWA Hiroyuki
2011-12-09 12:41 ` Glauber Costa
2011-12-09 12:41 ` Glauber Costa
2011-12-09 12:41 ` Glauber Costa
2011-12-05 21:34 ` [PATCH v8 3/9] socket: initial cgroup code Glauber Costa
2011-12-05 21:34 ` Glauber Costa
[not found] ` <1323120903-2831-4-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-09 1:49 ` KAMEZAWA Hiroyuki
2011-12-09 1:49 ` KAMEZAWA Hiroyuki
2011-12-09 1:49 ` KAMEZAWA Hiroyuki
2011-12-09 2:05 ` KAMEZAWA Hiroyuki
2011-12-09 2:05 ` KAMEZAWA Hiroyuki
2011-12-09 2:05 ` KAMEZAWA Hiroyuki
2011-12-09 12:43 ` Glauber Costa
2011-12-09 12:43 ` Glauber Costa
2011-12-09 12:43 ` Glauber Costa
[not found] ` <4EE20254.6000308-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-12 0:33 ` KAMEZAWA Hiroyuki
2011-12-12 0:33 ` KAMEZAWA Hiroyuki
2011-12-12 0:33 ` KAMEZAWA Hiroyuki
2011-12-12 0:33 ` KAMEZAWA Hiroyuki
2011-12-05 21:34 ` [PATCH v8 4/9] tcp memory pressure controls Glauber Costa
2011-12-05 21:34 ` Glauber Costa
2011-12-09 1:51 ` KAMEZAWA Hiroyuki
2011-12-09 1:51 ` KAMEZAWA Hiroyuki
2011-12-05 21:34 ` [PATCH v8 5/9] per-netns ipv4 sysctl_tcp_mem Glauber Costa
2011-12-05 21:34 ` Glauber Costa
[not found] ` <1323120903-2831-6-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-09 1:54 ` KAMEZAWA Hiroyuki
2011-12-09 1:54 ` KAMEZAWA Hiroyuki
2011-12-09 1:54 ` KAMEZAWA Hiroyuki
2011-12-05 21:35 ` [PATCH v8 6/9] tcp buffer limitation: per-cgroup limit Glauber Costa
2011-12-05 21:35 ` Glauber Costa
2011-12-09 1:55 ` KAMEZAWA Hiroyuki
2011-12-09 1:55 ` KAMEZAWA Hiroyuki
2011-12-05 21:35 ` [PATCH v8 7/9] Display current tcp memory allocation in kmem cgroup Glauber Costa
2011-12-05 21:35 ` Glauber Costa
2011-12-09 1:56 ` KAMEZAWA Hiroyuki
2011-12-09 1:56 ` KAMEZAWA Hiroyuki
2011-12-05 21:35 ` [PATCH v8 8/9] Display current tcp failcnt " Glauber Costa
2011-12-05 21:35 ` Glauber Costa
2011-12-05 21:35 ` [PATCH v8 9/9] Display maximum tcp memory allocation " Glauber Costa
2011-12-05 21:35 ` Glauber Costa
[not found] ` <1323120903-2831-10-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-09 1:57 ` KAMEZAWA Hiroyuki
2011-12-09 1:57 ` KAMEZAWA Hiroyuki
2011-12-09 1:57 ` KAMEZAWA Hiroyuki
[not found] ` <1323120903-2831-1-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-12-07 11:06 ` [PATCH v8 0/9] per-cgroup tcp memory pressure controls Glauber Costa
2011-12-07 11:06 ` Glauber Costa
2011-12-07 11:06 ` Glauber Costa
2011-12-07 11:06 ` Glauber Costa
2011-12-09 1:04 ` KAMEZAWA Hiroyuki
2011-12-09 1:04 ` KAMEZAWA Hiroyuki
2011-12-09 1:04 ` 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=4EE21FB0.5090006@parallels.com \
--to=glommer@parallels.com \
--cc=David.Laight@ACULAB.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=hannes@cmpxchg.org \
--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=mhocko@suse.cz \
--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.