[lkml]   [2009]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 3/3] Quick vmalloc vs kmalloc fix to the case where array size is too large
    On Mon, Jul 13, 2009 at 8:53 PM, KAMEZAWA
    Hiroyuki<> 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.


     \ /
      Last update: 2009-07-14 06:07    [W:0.020 / U:12.700 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site