Thread (40 messages) 40 messages, 4 authors, 2015-12-09

Re: [RFC PATCH V2 3/3] Ixgbevf: Add migration support for ixgbevf driver

From: Michael S. Tsirkin <hidden>
Date: 2015-11-25 12:28:19
Also in: intel-wired-lan, kvm, lkml, netdev, qemu-devel

On Wed, Nov 25, 2015 at 01:39:32PM +0800, Lan Tianyu wrote:
On 2015年11月25日 05:20, Michael S. Tsirkin wrote:
quoted
I have to say, I was much more interested in the idea
of tracking dirty memory. I have some thoughts about
that one - did you give up on it then?
No, our finial target is to keep VF active before doing
migration and tracking dirty memory is essential. But this
seems not easy to do that in short term for upstream. As
starters, stop VF before migration.
Frankly, I don't really see what this short term hack buys us,
and if it goes in, we'll have to maintain it forever.

Also, assuming you just want to do ifdown/ifup for some reason, it's
easy enough to do using a guest agent, in a completely generic way.

After deep thinking, the way of stopping VF still needs tracking
DMA-accessed dirty memory to make sure the received data buffer
before stopping VF migrated. It's easier to do that via dummy writing
data buffer when receive packet.


-- 
Best regards
Tianyu Lan
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help