[lkml]   [2002]   [Jul]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: memory leak?
    On Sunday 21 July 2002 16:20, Martin Josefsson wrote:
    > free don't know about slabcaches. take a look in /proc/slabinfo and see
    > what's using that memory. it's not a leak, the memory will be free'd
    > when the machine is under enough memory pressure.

    What happens when updatedb(1) runs? It does a `find /' and thus loads a lot of
    fs related data into memory, which makes the kernel caches grow. But how
    aggressive do these caches grow? Does this lead to any swapout because the
    kernel likes it better to have some dentries and inodes in memory than
    probably not-recently-used user pages?

    If so, this would mean that a low-priority job like updatedb(1) makes pages
    being swapped out that definitely have a higher priority. For updatedb and
    similar things (largish ls -lR's) it would make sense to
    load-and-quickly-forget all the inode and dentry cache stuff. Another
    optimisation syscall, like madvise?


    "That's interesting. Can it be disabled?" -- someone on LKML, after being
    told about the PIV hyperthreading features

    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 13:27    [W:0.025 / U:62.240 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site