[PATCH -mm 0/5] swapcgroup (v3)
kamezawa.hiroyu at jp.fujitsu.com
Fri Jul 4 02:40:33 PDT 2008
On Fri, 4 Jul 2008 15:15:36 +0900
Daisuke Nishimura <nishimura at mxp.nes.nec.co.jp> wrote:
> This is new version of swapcgroup.
> Major changes from previous version
> - Rebased on 2.6.26-rc5-mm3.
> The new -mm has been released, but these patches
> can be applied on 2.6.26-rc8-mm1 too with only some offset warnings.
> I tested these patches on 2.6.26-rc5-mm3 with some fixes about memory,
> and it seems to work fine.
> - (NEW) Implemented force_empty.
> Currently, it simply uncharges all the charges from the group.
> - [1/5] add cgroup files
> - [2/5] add a member to swap_info_struct
> - [3/5] implement charge and uncharge
> - [4/5] modify vm_swap_full()
> - [5/5] implement force_empty
> ToDo(in my thought. Feel free to add some others here.)
> - need some documentation
> Add to memory.txt? or create a new documentation file?
Maybe new documentation file is better.
> - add option to disable only this feature
> I'm wondering if this option is needed.
> memcg has already the boot option to disable it.
> Is there any case where memory should be accounted but swap should not?
On x86-32, area for vmalloc() is very small and array of swap_info_struct
will use much amount of it. If vmalloc() area is too small, the kernel cannot
> - hierarchy support
> - move charges along with task
> Both of them need more discussion.
> Daisuke Nishimura.
More information about the Containers