lkml.org 
[lkml]   [2002]   [Mar]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Scalability problem (kmap_lock) with -aa kernels
    My guess: persistent kmaps are okay, kmapped high pagetables are okay,
    persistent kmapped high pagetables are okay. What's wrong is how we
    flush_all_zero_pkmaps on all cpus, synchronously while holding the
    kmap_lock everyone needs to get a new kmap (and hopefully more often,
    just inc or dec the pkmap_count of kmap already got). That's what
    cries out for redesign: it's served us well but should now be improved.

    Hugh

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:25    [W:0.022 / U:0.596 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site