[PATCH 3/3] Quick vmalloc vs kmalloc fix to the case where array size is too large

Dave Hansen dave at linux.vnet.ibm.com
Tue Jul 14 10:47:32 PDT 2009

On Tue, 2009-07-14 at 10:28 -0700, Paul Menage wrote:
> On Mon, Jul 13, 2009 at 9:25 PM, KAMEZAWA
> Hiroyuki<kamezawa.hiroyu at jp.fujitsu.com> wrote:
> > My point is
> >  - More PIDs, More time necessary to read procs file.
> Right now, many pids => impossible to read procs file due to kmalloc
> failure. (This was always the case with cpusets too). So using kmalloc
> in those cases is a strict improvement.

How big were those allocations that were failing?  The code made it
appear that order-2 (PAGE_SIZE*4) allocations were failing.  That's a
bit lower than I'd expect the page allocator to start failing.

-- Dave

More information about the Containers mailing list