From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Paul Menage <menage@google.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
containers@lists.osdl.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC][-mm] Memory controller hierarchy support (v1)
Date: Sun, 20 Apr 2008 13:13:57 +0530 [thread overview]
Message-ID: <480AF43D.1090405@linux.vnet.ibm.com> (raw)
In-Reply-To: <4809CDB7.3000105@openvz.org>
Pavel Emelyanov wrote:
>
> Are you going to split this patch? As is it looks rather huge :)
>
Sure
>> TODO's/Open Questions
>>
>> 1. We need to hold cgroup_mutex while walking through the children
>> in reclaim. We need to figure out the best way to do so. Should
>> cgroups provide a helper function/macro for it?
>> 2. Do not allow children to have a limit greater than their parents.
>> 3. Allow the user to select if hierarchial support is required
>> 4. Fine tune reclaim from children logic
>>
>
> I though about it recently. Can we have a cgroup file, which will
> control whether to attach a res_counter to the parent? This will
> address the YEMEMOTO's question about the performance.
>
It's one of the TODOS
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
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-04-20 7:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 5:35 Balbir Singh
2008-04-19 6:56 ` YAMAMOTO Takashi
2008-04-19 8:34 ` Balbir Singh
2008-04-21 0:41 ` KAMEZAWA Hiroyuki
2008-04-19 10:47 ` Pavel Emelyanov
2008-04-20 7:43 ` Balbir Singh [this message]
2008-04-19 15:49 ` Paul Menage
2008-04-20 8:16 ` Balbir Singh
2008-04-21 6:33 ` Paul Jackson
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=480AF43D.1090405@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox