search for: chunks_of_balloon_pages

Displaying 7 results from an estimated 7 matches for "chunks_of_balloon_pages".

2017 Apr 05
2
[PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER
...esp_data; I think the implementation has an issue here - both the balloon pages and the unused pages use the same buffer ("resp_data" above) to store chunks. It would cause a race in this case: live migration starts while ballooning is also in progress. I plan to use separate buffers for CHUNKS_OF_BALLOON_PAGES and CHUNKS_OF_UNUSED_PAGES. Please let me know if you have a different suggestion. Thanks. Best, Wei
2017 Apr 05
2
[PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER
...esp_data; I think the implementation has an issue here - both the balloon pages and the unused pages use the same buffer ("resp_data" above) to store chunks. It would cause a race in this case: live migration starts while ballooning is also in progress. I plan to use separate buffers for CHUNKS_OF_BALLOON_PAGES and CHUNKS_OF_UNUSED_PAGES. Please let me know if you have a different suggestion. Thanks. Best, Wei
2017 Apr 05
1
[PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER
...ink the implementation has an issue here - both the balloon pages and the > unused pages use the same buffer ("resp_data" above) to store chunks. It would > cause a race in this case: live migration starts while ballooning is also in progress. > I plan to use separate buffers for CHUNKS_OF_BALLOON_PAGES and > CHUNKS_OF_UNUSED_PAGES. Please let me know if you have a different > suggestion. Thanks. > > > > Best, > > Wei > > Is only one resp data ever in flight for each kind? > If not you want as many buffers as vq allows. > No, all the kinds were using only one...
2017 Apr 05
1
[PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER
...ink the implementation has an issue here - both the balloon pages and the > unused pages use the same buffer ("resp_data" above) to store chunks. It would > cause a race in this case: live migration starts while ballooning is also in progress. > I plan to use separate buffers for CHUNKS_OF_BALLOON_PAGES and > CHUNKS_OF_UNUSED_PAGES. Please let me know if you have a different > suggestion. Thanks. > > > > Best, > > Wei > > Is only one resp data ever in flight for each kind? > If not you want as many buffers as vq allows. > No, all the kinds were using only one...
2017 Apr 05
0
[PATCH kernel v8 2/4] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER
...> > I think the implementation has an issue here - both the balloon pages and the unused pages use the same buffer ("resp_data" above) to store chunks. It would cause a race in this case: live migration starts while ballooning is also in progress. I plan to use separate buffers for CHUNKS_OF_BALLOON_PAGES and CHUNKS_OF_UNUSED_PAGES. Please let me know if you have a different suggestion. Thanks. > > Best, > Wei Is only one resp data ever in flight for each kind? If not you want as many buffers as vq allows. -- MST
2017 Mar 16
8
[PATCH kernel v8 0/4] Extend virtio-balloon for fast (de)inflating & fast live migration
This patch series implements two optimizations: 1) transfer pages in chuncks between the guest and host; 2) transfer the guest unused pages to the host so that they can be skipped to migrate in live migration. Please read each patch commit log for details. Changes: v7->v8: 1) Use only one chunk format, instead of two. 2) re-write the virtio-balloon implementation patch. 3) commit changes 4)
2017 Mar 16
8
[PATCH kernel v8 0/4] Extend virtio-balloon for fast (de)inflating & fast live migration
This patch series implements two optimizations: 1) transfer pages in chuncks between the guest and host; 2) transfer the guest unused pages to the host so that they can be skipped to migrate in live migration. Please read each patch commit log for details. Changes: v7->v8: 1) Use only one chunk format, instead of two. 2) re-write the virtio-balloon implementation patch. 3) commit changes 4)