From: Pavel Emelyanov <xemul@openvz.org>
To: Paul Menage <menage@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
balbir@linux.vnet.ibm.com, containers@lists.osdl.org,
Hugh Dickins <hugh@veritas.com>,
linux-mm@kvack.org
Subject: Re: [Devel] Re: [RFC/PATCH] cgroup swap subsystem
Date: Thu, 06 Mar 2008 11:50:45 +0300 [thread overview]
Message-ID: <47CFB065.3080200@openvz.org> (raw)
In-Reply-To: <6599ad830803060048sb39735an765a62e6b928657e@mail.gmail.com>
Paul Menage wrote:
> On Thu, Mar 6, 2008 at 12:38 AM, Pavel Emelyanov <xemul@openvz.org> wrote:
>> > Hierarchical res_counter makes sense.
>> > Making it in simple/reasonable style will be our challenge.
>>
>> I have this in my TODO list. Since this is not so urgent, then if you
>> don't mind I can prepare the patches next week - after I set the git
>> tree up. This change doesn't seem that big.
>>
>
> The change that you're referring to is allowing a cgroup to have a
> total memory limit for itself and all its children, and then giving
> that cgroup's children separate memory limits within that overall
> limit?
Yup. Isn't this reasonable?
Without this, if I'm a task in a 1GB limited cgroup, I can create a new
one, set 2GB limit and spawn a kid into it (or move there myself) and be
happy with 2GB of memory... With the proposed change, even if I set a 2GB
for a subgroup it will not pass _my_ (1GB) limit.
> Paul
>
--
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-03-06 8:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 5:59 [RFC/PATCH] cgroup swap subsystem Daisuke Nishimura
2008-03-05 6:36 ` Paul Menage
2008-03-06 12:20 ` Daisuke Nishimura
2008-03-05 6:53 ` KAMEZAWA Hiroyuki
2008-03-05 21:51 ` Hirokazu Takahashi
2008-03-06 11:45 ` Daisuke Nishimura
2008-03-06 12:25 ` Pavel Emelyanov
2008-03-06 12:56 ` kamezawa.hiroyu
2008-03-07 8:22 ` Daisuke Nishimura
2008-03-12 22:57 ` YAMAMOTO Takashi
2008-03-05 7:03 ` KAMEZAWA Hiroyuki
2008-03-05 7:28 ` Balbir Singh
2008-03-07 4:23 ` Daisuke Nishimura
2008-03-05 8:33 ` Pavel Emelyanov
2008-03-05 8:51 ` Daisuke Nishimura
2008-03-05 14:07 ` Hugh Dickins
2008-03-05 14:14 ` Pavel Emelyanov
2008-03-06 0:33 ` KAMEZAWA Hiroyuki
2008-03-06 0:35 ` Paul Menage
2008-03-06 8:20 ` Pavel Emelyanov
2008-03-06 8:33 ` KAMEZAWA Hiroyuki
2008-03-06 8:38 ` Pavel Emelyanov
2008-03-06 8:48 ` [Devel] " Paul Menage
2008-03-06 8:50 ` Pavel Emelyanov [this message]
2008-03-06 8:52 ` Paul Menage
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=47CFB065.3080200@openvz.org \
--to=xemul@openvz.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
/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;
as well as URLs for NNTP newsgroup(s).