Messages in this thread | | | Date | Tue, 5 Mar 2002 12:30:03 -0500 | Subject | Re: [RFC] Arch option to touch newly allocated pages | From | Jan Harkes <> |
| |
On Tue, Mar 05, 2002 at 09:43:39AM -0500, Jeff Dike wrote: > bcrl@redhat.com said: > > you only need to do the memsets once at startup of UML where the ram > > is allocated -> a uml booted with 64MB of ram would write into every > > page of the backing store file before even running the kernel. > > Doesn't that accomplish the same thing? > > The other reason I don't like this is that, at some point, I'd like to > start thinking about userspace cooperating with the kernel on memory > management. UML looks like a perfect place to start since it's essentially > identical to the host making it easier for the two to bargain over memory.
I could use the same thing in Coda, we have large private memory mappings that are backed by a file which isn't always up-to-date. But we can make it so by applying the logged modifications. If there is some 'memory pressure' signal we could apply the log and remap the memory to reduce swap usage.
On the other hand, applying the logged modifications generates a lot of write activity which could push the system over the edge, so the current method of having a large amount of swap available is probably more reliable. Otherwise we'll get the whole OOM killer debate again (the pre-OOM signaller?).
Jan
- 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/
| |