[lkml]   [2007]   [Jul]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 0/3] readahead drop behind and size adjustment
    On Sun, 2007-07-22 at 16:10 +0800, Fengguang Wu wrote:

    > - It will avoid large-file-reads-thrashing-my-desktop problem,
    > so most desktop users should like it. But sure there will be counter
    > cases when a user want to keep the data cached.
    > - File servers may hurt from it. Imagine a mp3/png file server. The
    > files are large enough to trigger drop-behind, but small (and hot)
    > enough to be cached. Also when a new fedora DVD iso is released, it
    > may be cached for some days. These are only the obvious cases.
    > So I opt for it being made tunable, safe, and turned off by default.

    I'm still not convinced (Rik wasn't either last time around). When these
    files really are hot, they will be kept in memory due to them becoming

    Also, by scaling up the max readahead size it takes a larger file before
    it starts dropping. If say this server has 4G of memory (not much at all
    for a server) resulting in a 1M readahead window, the file needs to be >
    ~2M before it starts drop behind.

    But I guess it takes someone to try this IRL before we can settle this
    debate :-/

    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: 2007-07-22 10:27    [W:0.019 / U:2.932 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site