[lkml]   [2012]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v5 6/7] x86/tlb: optimizing flush_tlb_mm
    On 15 May 2012 20:00, Peter Zijlstra <> wrote:
    > On Tue, 2012-05-15 at 19:52 +1000, Nick Piggin wrote:
    >> It could be warranted to change tlb_flush_mmu to a range API to
    >> avoid doing the per-entry tracking which those architectures do?
    > The per-entry could result in a much smaller range, there's no point in
    > flushing tlbs for unpopulated pages.

    Well common case for small ranges hopefully would be quite dense
    I think. It could be not worth the extra work (although maybe it would

    > Anyway, I don't think even think we'd need to change the API for that,
    > you could track the entire range through tlb_start_vma() if you wanted
    > (although nobody does that IIRC).

    I'm not sure if you can do that very well, because the tlb might have to
    be flushed part way through a vma when we fill up the gather, so you
    don't want to flush the full range each time.

     \ /
      Last update: 2012-05-15 13:01    [W:0.023 / U:36.720 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site