[lkml]   [2004]   [Oct]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 2/6] vmtrunc: restore unmap_vmas zap_bytes

    * Hugh Dickins <> wrote:

    > The low-latency unmap_vmas patch silently moved the zap_bytes test
    > after the TLB finish and lockbreak and regather: why? That not only
    > makes zap_bytes redundant (might as well use ZAP_BLOCK_SIZE), it makes
    > the unmap_vmas level redundant too - it's all about saving TLB flushes
    > when unmapping a series of small vmas.

    the problem was latency generated by pages queueing up in tlb_gather's
    queue and being freed in one loop, causing latencies. So there was no
    latency-break, only a shifting of the queue.

    > Move zap_bytes test back before the lockbreak, and delete the curious
    > comment that a small zap block size doesn't matter: it's true
    > need_flush prevents TLB flush when no page has been unmapped, but
    > unmapping pages in small blocks involves many more TLB flushes than in
    > large blocks.

    could we perhaps free those pages outside of the lock? That would be
    just as good for me.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:06    [W:0.025 / U:4.136 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site