From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [RFC][PATCH] memcg soft limit (yet another new design) v1
Date: Tue, 31 Mar 2009 11:40:10 +0530 [thread overview]
Message-ID: <20090331061010.GJ16497@balbir.in.ibm.com> (raw)
In-Reply-To: <20090331140502.813993cc.kamezawa.hiroyu@jp.fujitsu.com>
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-03-31 14:05:02]:
> On Tue, 31 Mar 2009 10:30:55 +0530
> Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
> > * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-03-31 08:55:38]:
> >
> > > On Sat, 28 Mar 2009 23:57:47 +0530
> > > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > >
> > > > * Balbir Singh <balbir@linux.vnet.ibm.com> [2009-03-28 23:41:00]:
> > > >
> > > > > * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-03-27 13:59:33]:
> > > > >
> > > > > > ==brief test result==
> > > > > > On 2CPU/1.6GB bytes machine. create group A and B
> > > > > > A. soft limit=300M
> > > > > > B. no soft limit
> > > > > >
> > > > > > Run a malloc() program on B and allcoate 1G of memory. The program just
> > > > > > sleeps after allocating memory and no memory refernce after it.
> > > > > > Run make -j 6 and compile the kernel.
> > > > > >
> > > > > > When vm.swappiness = 60 => 60MB of memory are swapped out from B.
> > > > > > When vm.swappiness = 10 => 1MB of memory are swapped out from B
> > > > > >
> > > > > > If no soft limit, 350MB of swap out will happen from B.(swapiness=60)
> > > > > >
> > > > >
> > > > > I ran the same tests, booted the machine with mem=1700M and maxcpus=2
> > > > >
> > > > > Here is what I see with
> > > >
> > > > I meant to say, Here is what I see with my patches (v7)
> > > >
> > > Hmm, I saw 250MB of swap out ;) As I reported before.
> >
> > Swapout for A? For A it is expected, but for B it is not. How many
> > nodes do you have on your machine? Any fake numa nodes?
> >
> Of course, from B.
>
I asked because I see A have a swapout of 350 MB, which is expected
since it is way over its soft limit.
> Nothing special boot options. My test was on VMware 2cpus/1.6GB memory.
>
> I wonder why swapout can be 0 on your test. Do you add some extra hooks to
> kswapd ?
>
Nope.. no special hooks to kswapd. B never enters the RB-Tree and thus
never hits the memcg soft limit reclaim path. kswapd can reclaim from
it, but it grows back quickly. At some point, memcg soft limit reclaim
hits A and reclaims memory from it, allowing B to run without any
problems. I am talking about the state at the end of the experiment.
--
Balbir
--
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:[~2009-03-31 6:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 4:59 KAMEZAWA Hiroyuki
2009-03-27 5:01 ` [RFC][PATCH 1/8] soft limit support in res_counter KAMEZAWA Hiroyuki
2009-03-27 5:03 ` [RFC][PATCH 2/8] soft limit framework in memcg KAMEZAWA Hiroyuki
2009-03-27 8:01 ` KAMEZAWA Hiroyuki
2009-03-29 17:22 ` Balbir Singh
2009-03-27 5:05 ` [RFC][PATCH 3/8] trigger for updating soft limit information KAMEZAWA Hiroyuki
2009-03-27 5:06 ` [RFC][PATCH 4/8] memcg soft limit priority array queue KAMEZAWA Hiroyuki
2009-03-29 16:56 ` Balbir Singh
2009-03-30 23:58 ` KAMEZAWA Hiroyuki
2009-03-27 5:09 ` [RFC][PATCH 5/8] memcg soft limit (yet another new design) v1 KAMEZAWA Hiroyuki
2009-03-27 5:14 ` KAMEZAWA Hiroyuki
2009-03-31 8:18 ` KAMEZAWA Hiroyuki
2009-03-27 5:11 ` [RFC][PATCH 6/8] soft limit victim select KAMEZAWA Hiroyuki
2009-03-27 5:12 ` [RFC][PATCH 7/8] memcg soft limit LRU reorder KAMEZAWA Hiroyuki
2009-03-30 7:52 ` Balbir Singh
2009-03-31 0:00 ` KAMEZAWA Hiroyuki
2009-03-31 6:06 ` Balbir Singh
2009-03-31 6:19 ` KAMEZAWA Hiroyuki
2009-03-27 5:13 ` [RFC][PATCH 8/8] extends soft limit event filter KAMEZAWA Hiroyuki
2009-03-28 8:23 ` [RFC][PATCH] memcg soft limit (yet another new design) v1 Balbir Singh
2009-03-28 16:10 ` KAMEZAWA Hiroyuki
2009-03-28 18:11 ` Balbir Singh
2009-03-28 18:27 ` Balbir Singh
2009-03-30 23:55 ` KAMEZAWA Hiroyuki
2009-03-31 5:00 ` Balbir Singh
2009-03-31 5:05 ` KAMEZAWA Hiroyuki
2009-03-31 5:18 ` KAMEZAWA Hiroyuki
2009-03-31 6:10 ` Balbir Singh [this message]
2009-03-31 6:28 ` KAMEZAWA Hiroyuki
2009-03-31 6:49 ` Balbir Singh
2009-03-31 6:56 ` KAMEZAWA Hiroyuki
2009-03-31 6:58 ` KAMEZAWA Hiroyuki
2009-03-31 0:06 ` KAMEZAWA Hiroyuki
2009-03-31 5:01 ` Balbir Singh
2009-03-31 5:11 ` KAMEZAWA Hiroyuki
2009-03-31 6:07 ` Balbir Singh
2009-03-30 23:54 ` KAMEZAWA Hiroyuki
2009-03-29 13:01 ` Balbir Singh
2009-03-30 23:57 ` KAMEZAWA Hiroyuki
2009-04-01 14:42 ` Balbir Singh
2009-04-01 15:11 ` KAMEZAWA Hiroyuki
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=20090331061010.GJ16497@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.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