lkml.org 
[lkml]   [2002]   [Mar]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] Arch option to touch newly allocated pages
Rik van Riel wrote:
>
> > So what *is* a solution. Well, there's only so much memory available.
> > In either case a) or case b) we're "fairly" distributing that memory
> > between all files. And that's the problem. *All* the files have too
> > small a readahead window. Which points one at: we need to stop being
> > fair. We need to give some files a good readahead window and others
> > not. The "soft pinning" which I propose with GFP_READAHEAD and
> > PG_readhead might have that effect, I think.
>
> Actually, it could boil down to something more:
>
> use-once reduces the VM to FIFO order, which suffers from
> belady's anomaly so it doesn't matter much how much memory
> you throw at it
>
> drop-behind will suffer the same problem once the readahead
> memory is too large to keep in the system, but at least the
> already-used pages won't kick out readahead pages

err.. Was there a fix in there somewhere, or are we stuck?

-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [W:0.107 / U:0.468 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site