On Sat, Jul 23, 2011 at 12:45:02PM +0400, Pavel Emelyanov wrote: > OK I see. Then my answer is - typically a container looks like an > init task with everybody else growing from that point. Having a > machine with 1000 of containers building the whole /proc tree in > memory to dump a single container would be MUCH more expensive that > having this small like in proc. This isn't a major point, so let's leave it alone for now. If it's necessary, adding it isn't a big deal; however, I think it would probably be better solved by per-ns procfs. If walking /proc becomes a huge overhead, CR wouldn't be the only one suffering and it calls for a better solution. Thanks. -- tejun _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
