On Wed, May 02, 2018 at 04:30:39PM +0100, Dr. David Alan Gilbert wrote: > * Peter Xu (peterx@xxxxxxxxxx) wrote: > > On Sat, Apr 28, 2018 at 04:10:45PM +0800, guangrong.xiao@xxxxxxxxx wrote: > > > From: Xiao Guangrong <xiaoguangrong@xxxxxxxxxxx> > > > > > > Fix the bug introduced by da3f56cb2e767016 (migration: remove > > > ram_save_compressed_page()), It should be 'return' rather than > > > 'res' > > > > > > Sorry for this stupid mistake :( > > > > > > Signed-off-by: Xiao Guangrong <xiaoguangrong@xxxxxxxxxxx> > > > > Reviewed-by: Peter Xu <peterx@xxxxxxxxxx> > > > > So is that only a performance degradation without this fix (since > > AFAIU the compressing pages will be sent twice)? Thanks, > > It might be a bit more messy than that; because I think the > 'compress_page_with_multi_thread' hands it to a compression thread to > compress and write, but I don't think it waits for it. > So I think you'll end up with this being written at the same time as the > uncompressed data is written - I'm not sure what the other end receives. > (Which makes me realise I don't think I understand how the compression > threads are safe with their writing data out). IIUC the compression threads are not really writting stuff to sockets, but only to local RAM. Please refer to do_data_compress() - when we do do_compress_ram_page() we are writting to CompressParam.file which is only a local buffer. We flush this buffer in flush_compressed_data() with qemu_put_qemu_file(). So IMHO the pages are still serialized no matter whether it's a compressed page or normal page. Then IMHO it'll be fine, since no matter whether we receive the compressed page or normal page first, we just update that page twice. Then we have two possibilities: - If the page is further modified, then both updates won't have any effect since we'll send a new version soon; - If the page is not modified any more, then both the compressed page and normal page will have exactly the same content, then it won't matter much on which one we handled first on destination (note that we will still handle the pages sequentially on destination). > > Anyway, I think we should get this one in quickly. Yes. Regards, -- Peter Xu
