Hello, Li. On Mon, Mar 09, 2015 at 09:49:45AM +0800, Zefan Li wrote: > Seems we are going to accept this feature. Is it because kmemcg won't be able > to fullfill this requirement? And that's because kmemcg can only and will only Yeah, pretty much. > be able to control global kernel memory usage? I'm not sure what you mean by global kernel memory usage. > I thought there will be some control file like kmem.pids.max, which will > translate the number of processes to the kernel memory needed, and fail memory > allocation if we reach the limit, for example make task_struct slab return > NULL. Hmm... I don't think so. memcg will only be concerned with actual memory in bytes. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
