On Tue, Oct 08, 2002 at 12:05:13PM -0700, Chris Wedgwood wrote:
> Playing the devil's advocate here... I didn't see this earlier (when
> was it discussed, I can't see it looking back either), so sorry if
> this sounds circular or I'm going over stuff that has been discussed
> before... but...
>
>
> On Tue, Oct 08, 2002 at 02:49:09PM -0400, Robert Love wrote:
>
> > In other words, this flag pretty much disables the pagecache for
> > this mapping, although we happily keep it around for write-behind
> > and read-ahead. But once the data is behind us and safe to kill, we
> > do. It is manual drop-behind.
>
> OK. What might use this though? What applications might want to
> disable the page-cache but still use write-behind?
mkisofs?
Or do you have a machine with 5-6 GB of RAM to cache the content of a
DVD-image?
I only have 3 GB of RAM, and creating and writing trashes the whole
cache twice.
Bis denn
-- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.- 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/
This archive was generated by hypermail 2b29 : Tue Oct 15 2002 - 22:00:27 EST