On Thu, 14 Apr 2011 15:54:27 -0700 Ying Han <yinghan@xxxxxxxxxx> wrote: > By default the per-memcg background reclaim is disabled when the limit_in_bytes > is set the maximum. The kswapd_run() is called when the memcg is being resized, > and kswapd_stop() is called when the memcg is being deleted. > > The per-memcg kswapd is waked up based on the usage and low_wmark, which is > checked once per 1024 increments per cpu. The memcg's kswapd is waked up if the > usage is larger than the low_wmark. > > changelog v4..v3: > 1. move kswapd_stop to mem_cgroup_destroy based on comments from KAMAZAWA > 2. move kswapd_run to setup_mem_cgroup_wmark, since the actual watermarks > determines whether or not enabling per-memcg background reclaim. > > changelog v3..v2: > 1. some clean-ups > > changelog v2..v1: > 1. start/stop the per-cgroup kswapd at create/delete cgroup stage. > 2. remove checking the wmark from per-page charging. now it checks the wmark > periodically based on the event counter. > > Signed-off-by: Ying Han <yinghan@xxxxxxxxxx> Ok, seems nice. For now, Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> I'll ack on later version. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>