Re: [RFC] Arch option to touch newly allocated pages

[Jeff Dike <jdike@karaya.com>]

mbeattie@clueful.co.uk said:
> A "quich hack" that turns out to have rather useful, fun properties is
> to have a little device driver (can be a module) which stores
> "negative pages" in the page cache by allocating page cache pages for
> the device's inode and then invoking the CP "release page" call
> mentioned above. 

Yeah, I was thinking about something like that.  It's unclear how it should
figure out how much memory to grab, though.  You'd have to get some idea
how desperate the host is for memory and balance that off against how 
desperate the VM is.

And you want to avoid doing things that just aggravate the host's situation,
i.e. if it is swapping its brains out, you want the VM to just drop some
clean pages and you definitely don't want it swapping dirty ones and add
to the host's IO load.

>  However, closer
> integration with the main mm system is the "proper" way to do it (but
> depends on stuff like the latency, overheads and information shared
> with CP so is a little more than an afternoon hack.)

Yup.

Is any of your (you or IBM in general) thinking on this written down publically
anywhere?

				Jeff