From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
Hugh Dickins <hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.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-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Paul Menage wrote:
> On Thu, Mar 6, 2008 at 12:38 AM, Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.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
>
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
[not found] ` <47CE36A9.3060204-YQH0OdQVrdy45+QrQBaojngSJqDPrsil@public.gmane.org>
2008-03-05 6:36 ` Paul Menage
[not found] ` <6599ad830803042236x3e5fdf0dmaf4119997025ba40-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-06 12:20 ` Daisuke Nishimura
2008-03-05 6:53 ` KAMEZAWA Hiroyuki
[not found] ` <20080305155329.60e02f48.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-03-05 21:51 ` Hirokazu Takahashi
2008-03-06 11:45 ` Daisuke Nishimura
[not found] ` <47CFD957.3060402-YQH0OdQVrdy45+QrQBaojngSJqDPrsil@public.gmane.org>
2008-03-06 12:25 ` Pavel Emelyanov
2008-03-06 12:56 ` kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A
[not found] ` <6197904.1204808216900.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
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
[not found] ` <47CE4BB6.8050803-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-03-07 4:23 ` Daisuke Nishimura
2008-03-05 8:33 ` Pavel Emelyanov
[not found] ` <47CE5AE2.2050303-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-05 8:51 ` Daisuke Nishimura
2008-03-05 14:07 ` Hugh Dickins
[not found] ` <Pine.LNX.4.64.0803051400000.22243-popGQ1T0qN76K7/ahGyk6A@public.gmane.org>
2008-03-05 14:14 ` Pavel Emelyanov
[not found] ` <47CEAAB4.8070208-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-06 0:33 ` KAMEZAWA Hiroyuki
[not found] ` <20080306093324.77c6d7f4.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-03-06 0:35 ` Paul Menage
2008-03-06 8:20 ` Pavel Emelyanov
[not found] ` <47CFA941.4070507-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-06 8:33 ` KAMEZAWA Hiroyuki
[not found] ` <20080306173347.f6c5c84c.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-03-06 8:38 ` Pavel Emelyanov
[not found] ` <47CFAD69.6000909-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-03-06 8:48 ` [Devel] " Paul Menage
[not found] ` <6599ad830803060048sb39735an765a62e6b928657e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-03-06 8:50 ` Pavel Emelyanov [this message]
[not found] ` <47CFB065.3080200-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
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-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
--cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=hugh-DTz5qymZ9yRBDgjK7y7TUQ@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox