On Mon, Jul 13, 2009 at 8:53 PM, KAMEZAWA Hiroyuki<kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote: > Hmm, ok...then, if too much pids, you hit vmalloc()/vfree() problem again. > So, it's not good idea to use vmalloc/vfree here after all. > Agreed, using vmalloc()/vfree() isn't a perfect solution, but at least the approach of kmalloc() for small allocations and vmalloc() for larger allocations solves the current problem (reading tasks/procs files can fail due to lack of contiguous kmalloc memory) without introducing overhead in the typical case. Paul _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
