On Fri, 2009-03-27 at 16:09 +0100, Martin Schwidefsky wrote: > If the host picks one of the > pages the guest can recreate, the host can throw it away instead of writing > it to the paging device. Simple and elegant. Heh, simple and elegant for the hypervisor. But I'm not sure I'm going to call *anything* that requires a new CPU instruction elegant. ;) I don't see any description of it in there any more, but I thought this entire patch set was to get rid of the idiotic triple I/Os in the following scenario: 1. Hypervisor picks a page and evicts it out to disk, pays the I/O cost to get it written out. (I/O #1) 2. Linux comes along (being a bit late to the party) and picks the same page, also decides it needs to be out to disk 3. Linux tries to write the page to disk, but touches it in the process, pulling the page back in from the store where the hypervisor wrote it. (I/O #2) 4. Linux writes the page to its swap device (I/O #3) I don't see that mentioned at all in the current description. Simplifying the hypervisor is hard to get behind, but cutting system I/O by 2/3 is a much nicer benefit for 1200 lines of invasive code. ;) Can we persuade the hypervisor to tell us which pages it decided to page out and just skip those when we're scanning the LRU? -- Dave _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
