On Mon, 18 Apr 2011 20:57:36 -0700 Ying Han <yinghan@xxxxxxxxxx> wrote: > 1. there are one kswapd thread per cgroup. the thread is created when the > cgroup changes its limit_in_bytes and is deleted when the cgroup is being > removed. In some enviroment when thousand of cgroups are being configured on > a single host, we will have thousand of kswapd threads. The memory consumption > would be 8k*100 = 8M. We don't see a big issue for now if the host can host > that many of cgroups. > I don't think no-fix to this is ok. Here is a thread pool patch on your set. (and includes some more). 3 patches in following e-mails. Any comments are welocme, but my response may be delayed. Thanks, -Kame -- 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>