On 08/16/2017 01:57 PM, Adam Tao wrote:
On Thu, Aug 03, 2017 at 02:38:14PM +0800, Wei Wang wrote:
This patch series enhances the existing virtio-balloon with the following
new features:
1) fast ballooning: transfer ballooned pages between the guest and host in
chunks using sgs, instead of one by one; and
2) free_page_vq: a new virtqueue to report guest free pages to the host.
Hi wei,
The reason we add the new vq for the migration feature is based on
what(original design based on inflate and deflate vq)?
I am wondering if we add new feature in the future do we still need to add new type
of vq?
Do we need to add one command queue for the common purpose(including
different type of requests except the in/deflate ones)?
Thanks
Adam
Hi Adam,
The the free_page_vq is added to report free pages to the hypervisor.
Neither inflate nor deflate vq was for this purpose.
Based on the current implementation, a vq dedicated to one usage (i.e.
report
free pages) is better, since mixing with other usages, e.g. a command vq to
handle multiple commands at the same time, would have some issues (e.g. one
being delayed by another due to some resource control), and it also
results in
more complex interfaces between the driver and device.
For future usages which are still unknown at present, I think we can discuss
them case by case in the future.
Best,
Wei
