jdike@karaya.com said:
> Yeah, MADV_DONTNEED looks right. UML and Linux/s390 (assuming VM has
> the equivalent of MADV_DONTNEED) would need a hook in free_pages to
> make that happen.
MADV_DONTNEED
Do not expect access in the near future. (For the
time being, the application is finished with the
given range, so the kernel can free resources asso
ciated with it.)
It's not clear from that that the host kernel is actually permitted to
discard the data.
alan@lxorguk.ukuu.org.uk said:
> VM allows you to give it back a page and if you use it again you get
> a clean copy. What it seems to lack is the more ideal "here have this
> page and if I reuse it trap if you did throw it out" semantic.
I've wittered on occasion about other situations where such semantics might
be useful -- essentially 'drop these pages if you need to as if they were
clean, and tell me when I next touch them so I can recreate their data'.
UML might want that kind of thing for its (clean) page cache pages or
something, but for pages allocated for kernel stack and task struct we
really want the opposite -- we want to make sure they're present when we
allocate them, and explicitly discard them when we're done.
-- dwmw2- 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 : Thu Mar 07 2002 - 21:00:57 EST