Dong, Eddie wrote: >> The push model may require parallelization of the disk and memory >> convergence depending on how much disk activity the guest is doing. >> That's a pretty interesting problem but it shouldn't be too >> hard to solve. >> >> > Embed this kind of cache like disk ops (write and read hit always > goes to local disk, while read miss goes to remote source before > convergence) > feature into IDE device model would be great which will benefit both KVM > & Qemu > and thus easier to push into Qemu tree. >
I was actually thinking it ought to be another BlockDriver. There's no need to make it part of the device emulation. Regards, Anthony Liguori > thx, eddie > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > kvm-devel mailing list > kvm-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kvm-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
