Re: RFC: design for new VM

[Matthew Wilcox <matthew@wil.cx>]

On Mon, Aug 07, 2000 at 10:40:52AM -0700, Gerrit.Huizenga@us.ibm.com wrote:
> Also, I note that your filesys->flush() mechanism utilizes a call
> per page.  This is an interesting capability, although I'd question
> the processor efficiency of a page granularity here.  On large memory
> systems, with large processes starting (e.g. Netscape, StarOffice, or
> possible a database client), it seems like a callback to a filesystem
> which said something like flush("I must have at least 10 pages from
> you", "and I'd really like 100 pages") might be a better way to
> use this advisory capability.  You've already pointed out that you
> may request that a specific page might be requested but other pages
> may be freed; this may be a more explicit way to code the policy
> you really want.

i had a little argument with Rik about this.  his PoV is that the
filesystem should know nothing about which pages are aged and are ready
to be sent to disc.  so what he wants is the filesystem to be able to say
`no, you can't flush that page'.

-- 
Revolutions do not require corporate support.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/