From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Paul Menage <menage@google.com>,
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
Linux Containers <containers@lists.osdl.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2] Make res_counter hierarchical
Date: Tue, 11 Mar 2008 18:07:46 +0900 [thread overview]
Message-ID: <20080311180746.6d665013.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <47D6451A.7090807@openvz.org>
On Tue, 11 Mar 2008 11:38:50 +0300
Pavel Emelyanov <xemul@openvz.org> wrote:
> >> <mem_couter_0>
> >> + -- <swap_counter_0>
> >> + -- <mem_counter_1>
> >> | + -- <swap_counter_1>
> >> | + -- <mem_counter_11>
> >> | | + -- <swap_counter_11>
> >> | + -- <mem_counter_12>
> >> | + -- <swap_counter_12>
> >> + -- <mem_counter_2>
> >> | + -- <swap_counter_2>
> >> | + -- <mem_counter_21>
> >> | | + -- <swap_counter_21>
> >> | + -- <mem_counter_22>
> >> | + -- <swap_counter_22>
> >> + -- <mem_counter_N>
> >> + -- <swap_counter_N>
> >> + -- <mem_counter_N1>
> >> | + -- <swap_counter_N1>
> >> + -- <mem_counter_N2>
> >> + -- <swap_counter_N2>
> >>
> > please let me confirm.
> >
> > - swap_counter_X.limit can be defined independent from mem_counter_X.limit ?
> > - swap_conter_N1's limit and swap_counter_N's have some relationship ?
>
> No. The mem_counter_N_limit is the limit for all the memory, that the
> Nth group consumes. This includes the RSS, page cache and swap for this
> group and all the child groups. Since RSS and page cache are accounted
> together, this limit tracks the sum of (memory + swap) values over the
> subtree started at the given group.
>
Hmm, how should I set limit to allow "tons of swap but small limit to memory".
Thanks,
-Kame
--
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-11 9:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 15:32 Pavel Emelyanov
2008-03-08 4:45 ` KAMEZAWA Hiroyuki
2008-03-11 8:15 ` Pavel Emelyanov
2008-03-11 8:32 ` KAMEZAWA Hiroyuki
2008-03-11 8:38 ` Pavel Emelyanov
2008-03-11 9:03 ` Daisuke Nishimura
2008-03-11 9:07 ` KAMEZAWA Hiroyuki [this message]
2008-03-11 8:57 ` Paul Menage
2008-03-11 9:13 ` KAMEZAWA Hiroyuki
2008-03-11 9:11 ` Paul Menage
2008-03-11 9:16 ` Balbir Singh
2008-03-11 9:39 ` KAMEZAWA Hiroyuki
2008-03-11 9:53 ` Balbir Singh
2008-03-11 10:03 ` KAMEZAWA Hiroyuki
2008-03-11 15:56 ` Paul Menage
2008-03-11 15:59 ` Balbir Singh
2008-03-08 19:06 ` Balbir Singh
2008-03-11 8:17 ` Pavel Emelyanov
2008-03-11 8:24 ` Balbir Singh
2008-03-11 8:40 ` Pavel Emelyanov
2008-03-12 23:05 ` YAMAMOTO Takashi
2008-03-12 23:36 ` YAMAMOTO Takashi
2008-03-13 8:56 ` Pavel Emelyanov
[not found] ` <47D16004.7050204-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-04-02 15:26 ` Balbir Singh
[not found] ` <47F3A5BF.1080301-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-04-03 12:26 ` Pavel Emelyanov
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=20080311180746.6d665013.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=xemul@openvz.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