memrlimit controller merge to mainline

Daisuke Nishimura nishimura at mxp.nes.nec.co.jp
Tue Jul 29 22:41:40 PDT 2008


On Wed, 30 Jul 2008 14:11:47 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
> On Wed, 30 Jul 2008 13:58:03 +0900
> Daisuke Nishimura <nishimura at mxp.nes.nec.co.jp> wrote:
> 
> > On Wed, 30 Jul 2008 13:14:07 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
> > > On Wed, 30 Jul 2008 12:11:15 +0900
> > > KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
> > > 
> > > > On Wed, 30 Jul 2008 11:52:26 +0900
> > > > KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
> > > > > mem+swap controller means a shrink to memory resource controller 
> > > > > (try_to_free_mem_cgroup_pages()) should drop only file caches.
> > > > > (Because kick-out-to-swap will never changes the usage.)
> > > > > 
> > > > > right ? only global-lru can make a swap.
> > > > > maybe I can add optimization to do this. Hmm. I should see how OOM works
> > > > > under some situation.
> > > > > 
> > I'm thinking mem+swap controller in a different way: an add-on to
> > mem controller, just as current swap controller.
> > I mean adding "memory.(mem+swap)_limit".
> > 
> Hmm ? adding a control file other than
>  - memory.limit_in_bytes
> ?
> 
Yes.

I just thought:
- memory.rss_limit_in_bytes (same as current limit_in_bytes)
- memory.total_limit_in_bytes (rss + swap)


Thanks,
Daisuke Nishimura.


More information about the Containers mailing list