[lkml]   [2001]   [Aug]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [resent PATCH] Re: very slow parallel read performance
    On August 25, 2001 01:23 am, ( Marc) (A.) (Lehmann ) wrote:
    > I could imagine that read() executes, returns to
    > userspace and at the same time the kernel thinks "nothing to do, let's
    > readahead". While, in the concurrent case, there is hardly a time when no
    > read() is running. But read-ahead does not seem to work that way.

    But it's a very interesting idea: instead of performing readahead in
    generic_file_read the user thread would calculate the readahead window
    information and pass it off to a kernel thread dedicated to readahead.
    This thread can make an informed, global decision on how much IO to
    submit. The user thread benefits by avoiding some stalls due to
    readahead->readpage, as well as avoiding thrashing due to excessive

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