On Wed, Apr 20, 2011 at 9:22 PM, Ying Han <yinghan@xxxxxxxxxx> wrote:
On Wed, Apr 20, 2011 at 8:40 PM, KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote:
On Mon, 18 Apr 2011 20:57:36 -0700I don't think no-fix to this is ok.
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.
>
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.
Thank you for making up the patch, and I will take a look. Do I apply the 3 patches on top of my patchset or they comes separately?
Sorry, please ignore my last question. Looks like the patch are based on my existing per-memcg kswapd patchset. I will try to apply it.
--Ying
--YingThanks,
-Kame