From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"menage@google.com" <menage@google.com>,
"xemul@openvz.org" <xemul@openvz.org>,
"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>
Subject: Re: [RFC][PATCH 1/2] memcg: res_counter hierarchy
Date: Wed, 04 Jun 2008 14:54:12 +0800 [thread overview]
Message-ID: <48463C14.4000705@cn.fujitsu.com> (raw)
In-Reply-To: <20080604140153.fec6cc99.kamezawa.hiroyu@jp.fujitsu.com>
> Index: temp-2.6.26-rc2-mm1/Documentation/controllers/resource_counter.txt
> ===================================================================
> --- temp-2.6.26-rc2-mm1.orig/Documentation/controllers/resource_counter.txt
> +++ temp-2.6.26-rc2-mm1/Documentation/controllers/resource_counter.txt
> @@ -44,6 +44,13 @@ to work with it.
> Protects changes of the above values.
>
>
> + f. struct res_counter *parent
> +
> + Parent res_counter under hierarchy.
> +
> + g. unsigned long long for_children
> +
> + Resources assigned to children. This is included in usage.
Since parent and for_children are also protected by res_count->lock,
the above text should appear before 'e. spinlock_t lock'.
WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizf@cn.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"menage@google.com" <menage@google.com>,
"xemul@openvz.org" <xemul@openvz.org>,
"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>
Subject: Re: [RFC][PATCH 1/2] memcg: res_counter hierarchy
Date: Wed, 04 Jun 2008 14:54:12 +0800 [thread overview]
Message-ID: <48463C14.4000705@cn.fujitsu.com> (raw)
In-Reply-To: <20080604140153.fec6cc99.kamezawa.hiroyu@jp.fujitsu.com>
> Index: temp-2.6.26-rc2-mm1/Documentation/controllers/resource_counter.txt
> ===================================================================
> --- temp-2.6.26-rc2-mm1.orig/Documentation/controllers/resource_counter.txt
> +++ temp-2.6.26-rc2-mm1/Documentation/controllers/resource_counter.txt
> @@ -44,6 +44,13 @@ to work with it.
> Protects changes of the above values.
>
>
> + f. struct res_counter *parent
> +
> + Parent res_counter under hierarchy.
> +
> + g. unsigned long long for_children
> +
> + Resources assigned to children. This is included in usage.
Since parent and for_children are also protected by res_count->lock,
the above text should appear before 'e. spinlock_t lock'.
--
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>
next prev parent reply other threads:[~2008-06-04 6:56 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-04 4:58 [RFC][PATCH 0/2] memcg: hierarchy support (v3) KAMEZAWA Hiroyuki
2008-06-04 4:58 ` KAMEZAWA Hiroyuki
2008-06-04 5:01 ` [RFC][PATCH 1/2] memcg: res_counter hierarchy KAMEZAWA Hiroyuki
2008-06-04 5:01 ` KAMEZAWA Hiroyuki
2008-06-04 6:54 ` Li Zefan [this message]
2008-06-04 6:54 ` Li Zefan
2008-06-04 7:03 ` KAMEZAWA Hiroyuki
2008-06-04 7:03 ` KAMEZAWA Hiroyuki
2008-06-04 7:20 ` YAMAMOTO Takashi
2008-06-04 7:20 ` YAMAMOTO Takashi
2008-06-04 7:32 ` KAMEZAWA Hiroyuki
2008-06-04 7:32 ` KAMEZAWA Hiroyuki
2008-06-04 8:59 ` Paul Menage
2008-06-04 8:59 ` Paul Menage
2008-06-04 9:18 ` KAMEZAWA Hiroyuki
2008-06-04 9:18 ` KAMEZAWA Hiroyuki
2008-06-09 9:48 ` Balbir Singh
2008-06-09 9:48 ` Balbir Singh
2008-06-09 10:20 ` KAMEZAWA Hiroyuki
2008-06-09 10:20 ` KAMEZAWA Hiroyuki
2008-06-09 10:37 ` Balbir Singh
2008-06-09 10:37 ` Balbir Singh
2008-06-09 12:02 ` kamezawa.hiroyu
2008-06-09 12:02 ` kamezawa.hiroyu
2008-06-11 23:24 ` Randy Dunlap
2008-06-11 23:24 ` Randy Dunlap
2008-06-12 4:59 ` KAMEZAWA Hiroyuki
2008-06-12 4:59 ` KAMEZAWA Hiroyuki
2008-06-04 5:03 ` [RFC][PATCH 2/2] memcg: hardwall hierarhcy for memcg KAMEZAWA Hiroyuki
2008-06-04 5:03 ` KAMEZAWA Hiroyuki
2008-06-04 6:42 ` Li Zefan
2008-06-04 6:42 ` Li Zefan
2008-06-04 6:54 ` KAMEZAWA Hiroyuki
2008-06-04 6:54 ` KAMEZAWA Hiroyuki
2008-06-04 8:59 ` Paul Menage
2008-06-04 8:59 ` Paul Menage
2008-06-04 9:26 ` KAMEZAWA Hiroyuki
2008-06-04 9:26 ` KAMEZAWA Hiroyuki
2008-06-04 12:53 ` Daisuke Nishimura
2008-06-04 12:53 ` Daisuke Nishimura
2008-06-04 12:32 ` Daisuke Nishimura
2008-06-04 12:32 ` Daisuke Nishimura
2008-06-05 0:04 ` KAMEZAWA Hiroyuki
2008-06-05 0:04 ` KAMEZAWA Hiroyuki
2008-06-09 10:56 ` Balbir Singh
2008-06-09 10:56 ` Balbir Singh
2008-06-09 12:09 ` kamezawa.hiroyu
2008-06-09 12:09 ` kamezawa.hiroyu
2008-06-11 23:24 ` Randy Dunlap
2008-06-11 23:24 ` Randy Dunlap
2008-06-12 5:00 ` KAMEZAWA Hiroyuki
2008-06-12 5:00 ` KAMEZAWA Hiroyuki
2008-06-04 8:59 ` [RFC][PATCH 0/2] memcg: hierarchy support (v3) Paul Menage
2008-06-04 8:59 ` Paul Menage
2008-06-04 9:15 ` KAMEZAWA Hiroyuki
2008-06-04 9:15 ` KAMEZAWA Hiroyuki
2008-06-04 9:15 ` Paul Menage
2008-06-04 9:15 ` Paul Menage
2008-06-04 9:31 ` KAMEZAWA Hiroyuki
2008-06-04 9:31 ` KAMEZAWA Hiroyuki
2008-06-09 9:30 ` Balbir Singh
2008-06-09 9:30 ` Balbir Singh
2008-06-09 9:55 ` KAMEZAWA Hiroyuki
2008-06-09 9:55 ` KAMEZAWA Hiroyuki
2008-06-09 10:33 ` Balbir Singh
2008-06-09 10:33 ` Balbir Singh
-- strict thread matches above, loose matches on Subject: below --
2008-05-30 1:43 [RFC][PATCH 0/2] memcg: simple hierarchy (v2) KAMEZAWA Hiroyuki
2008-05-30 1:45 ` [RFC][PATCH 1/2] memcg: res_counter hierarchy KAMEZAWA Hiroyuki
2008-05-30 1:45 ` KAMEZAWA Hiroyuki
2008-05-30 22:20 ` Balbir Singh
2008-05-30 22:20 ` Balbir Singh
2008-05-31 1:59 ` kamezawa.hiroyu
2008-05-31 11:20 ` Balbir Singh
2008-05-31 11:20 ` Balbir Singh
2008-05-31 14:47 ` kamezawa.hiroyu
2008-05-31 17:18 ` Balbir Singh
2008-05-31 17:18 ` Balbir Singh
2008-06-01 0:35 ` kamezawa.hiroyu
2008-06-02 6:16 ` Balbir Singh
2008-06-02 6:16 ` Balbir Singh
2008-06-02 2:15 ` YAMAMOTO Takashi
2008-06-02 2:15 ` YAMAMOTO Takashi
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=48463C14.4000705@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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.