Paul Menage wrote: > On Tue, Aug 26, 2008 at 9:29 PM, Lai Jiangshan <laijs@xxxxxxxxxxxxxx> wrote: >> And vmalloc can malloc larger memory than kmalloc, is vmalloc() enough? >> If not, I think using an array of pages is the best choice. > > vmalloc would be simpler, certainly, but it has a higher overhead. And > since we're dealing with arrays of integers here, it's not too hard to > manage multiple arrays. Oh, except for sorting them, which would be > more of a pain. So yes, maybe vmalloc() would be a better choice at > first. > Yep, these are hard. Which method is your favorite? My original purpose was to fix a bug as I described. This bug and the problem that offering big enough array for a huge cgroup are orthogonal! Could you consider/test that is it a bug as I described(and is it as critical as I described, maybe I was too nervous)? And this is also a problem: opening a cgroup.tasks twice or will waste a lot of _physical_ memory. Thanks! Lai _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers