From: Wanpeng Li <liwp.linux@gmail.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wanpeng Li <liwp.linux@gmail.com>
Subject: Re: [PATCH] mm/memcg: return -EBUSY when oom-kill-disable modified and memcg use_hierarchy, has children
Date: Mon, 9 Jul 2012 13:10:55 +0800 [thread overview]
Message-ID: <20120709051036.GA8304@kernel> (raw)
In-Reply-To: <4FFA616B.4000608@jp.fujitsu.com>
On Mon, Jul 09, 2012 at 01:43:23PM +0900, Kamezawa Hiroyuki wrote:
>(2012/07/05 19:55), Wanpeng Li wrote:
>> From: Wanpeng Li <liwp@linux.vnet.ibm.com>
>>
>> When oom-kill-disable modified by the user and current memcg use_hierarchy,
>> the change can occur, provided the current memcg has no children. If it
>> has children, return -EBUSY is enough.
>>
>> Signed-off-by: Wanpeng Li <liwp.linux@gmail.com>
>
>I'm sorry what is the point ? You think -EBUSY should be returned in this case
>rather than -EINVAl ? Then, why ?
just like in function cmem_cgroup_hierarchy_write:
if((!parent_memcg || !parent_memcg->use_hierarchy) &&
(val == 1 || val == 0) {
if (list_empty(&cont->children))
memcg->use_hierarchy = val;
else
return -EBUSY;
} else
return = -EINVAL;
If memcg->use_hierarchy && has children memcg, the user can try again
if children memcg disappear. Or I miss something ....
Regards,
Wanpeng Li
>
>
>> ---
>> mm/memcontrol.c | 7 +++++--
>> 1 files changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index 63e36e7..4b64fe0 100644
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -4521,11 +4521,14 @@ static int mem_cgroup_oom_control_write(struct cgroup *cgrp,
>>
>> cgroup_lock();
>> /* oom-kill-disable is a flag for subhierarchy. */
>> - if ((parent->use_hierarchy) ||
>> - (memcg->use_hierarchy && !list_empty(&cgrp->children))) {
>> + if (parent->use_hierarchy) {
>> cgroup_unlock();
>> return -EINVAL;
>> + } else if (memcg->use_hierarchy && !list_empty(&cgrp->children)) {
>> + cgroup_unlock();
>> + return -EBUSY;
>> }
>> +
>> memcg->oom_kill_disable = val;
>> if (!val)
>> memcg_oom_recover(memcg);
>>
>
>
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Wanpeng Li <liwp.linux@gmail.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wanpeng Li <liwp.linux@gmail.com>
Subject: Re: [PATCH] mm/memcg: return -EBUSY when oom-kill-disable modified and memcg use_hierarchy, has children
Date: Mon, 9 Jul 2012 13:10:55 +0800 [thread overview]
Message-ID: <20120709051036.GA8304@kernel> (raw)
In-Reply-To: <4FFA616B.4000608@jp.fujitsu.com>
On Mon, Jul 09, 2012 at 01:43:23PM +0900, Kamezawa Hiroyuki wrote:
>(2012/07/05 19:55), Wanpeng Li wrote:
>> From: Wanpeng Li <liwp@linux.vnet.ibm.com>
>>
>> When oom-kill-disable modified by the user and current memcg use_hierarchy,
>> the change can occur, provided the current memcg has no children. If it
>> has children, return -EBUSY is enough.
>>
>> Signed-off-by: Wanpeng Li <liwp.linux@gmail.com>
>
>I'm sorry what is the point ? You think -EBUSY should be returned in this case
>rather than -EINVAl ? Then, why ?
just like in function cmem_cgroup_hierarchy_write:
if((!parent_memcg || !parent_memcg->use_hierarchy) &&
(val == 1 || val == 0) {
if (list_empty(&cont->children))
memcg->use_hierarchy = val;
else
return -EBUSY;
} else
return = -EINVAL;
If memcg->use_hierarchy && has children memcg, the user can try again
if children memcg disappear. Or I miss something ....
Regards,
Wanpeng Li
>
>
>> ---
>> mm/memcontrol.c | 7 +++++--
>> 1 files changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index 63e36e7..4b64fe0 100644
>> --- a/mm/memcontrol.c
>> +++ b/mm/memcontrol.c
>> @@ -4521,11 +4521,14 @@ static int mem_cgroup_oom_control_write(struct cgroup *cgrp,
>>
>> cgroup_lock();
>> /* oom-kill-disable is a flag for subhierarchy. */
>> - if ((parent->use_hierarchy) ||
>> - (memcg->use_hierarchy && !list_empty(&cgrp->children))) {
>> + if (parent->use_hierarchy) {
>> cgroup_unlock();
>> return -EINVAL;
>> + } else if (memcg->use_hierarchy && !list_empty(&cgrp->children)) {
>> + cgroup_unlock();
>> + return -EBUSY;
>> }
>> +
>> memcg->oom_kill_disable = val;
>> if (!val)
>> memcg_oom_recover(memcg);
>>
>
>
next prev parent reply other threads:[~2012-07-09 5:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 10:55 [PATCH] mm/memcg: return -EBUSY when oom-kill-disable modified and memcg use_hierarchy, has children Wanpeng Li
2012-07-05 10:55 ` Wanpeng Li
2012-07-09 4:43 ` Kamezawa Hiroyuki
2012-07-09 4:43 ` Kamezawa Hiroyuki
2012-07-09 5:10 ` Wanpeng Li [this message]
2012-07-09 5:10 ` Wanpeng Li
2012-07-09 12:01 ` Michal Hocko
2012-07-09 12:01 ` Michal Hocko
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=20120709051036.GA8304@kernel \
--to=liwp.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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.