On Wed, 30 May 2012, Tejun Heo wrote: > Yeah, I prefer your per-cg cache approach but do hope that it stays as > far from actual allocator code as possible. Christoph, would it be > acceptable if the cg logic is better separated? Certainly anything that would allow this to be separated out would be appreciated. I do not anticipate to ever run cgroup in my environment and that is due to the additional latency created in key OS paths. Memory we have enough. The increased cache footprint is killing performance. -- 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
