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

KAMEZAWA Hiroyuki kamezawa.hiroyu at jp.fujitsu.com
Mon Jul 13 20:53:34 PDT 2009

On Mon, 13 Jul 2009 20:50:33 -0700
Paul Menage <menage at google.com> wrote:

> On Mon, Jul 13, 2009 at 4:49 PM, KAMEZAWA
> Hiroyuki<kamezawa.hiroyu at jp.fujitsu.com> wrote:
> > IIUC, this place, .../procs interface is not so important for performance
> > as to being allowed this ugly conding.
> >
> It's not just the calling thread that suffers from the overhead -
> we've seen performance hits on other processes on a machine due to the
> TLB-shootdown overhead associated with vmalloc()/vfree().
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.


More information about the Containers mailing list