[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56554994.1090305@intel.com>
Date: Wed, 25 Nov 2015 13:39:32 +0800
From: Lan Tianyu <tianyu.lan@...el.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
CC: a.motakis@...tualopensystems.com, alex.williamson@...hat.com,
b.reynal@...tualopensystems.com, bhelgaas@...gle.com,
carolyn.wyborny@...el.com, donald.c.skidmore@...el.com,
eddie.dong@...el.com, nrupal.jani@...el.com, agraf@...e.de,
kvm@...r.kernel.org, pbonzini@...hat.com, qemu-devel@...gnu.org,
emil.s.tantilov@...el.com, gerlitz.or@...il.com,
mark.d.rustad@...el.com, eric.auger@...aro.org,
intel-wired-lan@...ts.osuosl.org, jeffrey.t.kirsher@...el.com,
jesse.brandeburg@...el.com, john.ronciak@...el.com,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
matthew.vick@...el.com, mitch.a.williams@...el.com,
netdev@...r.kernel.org, shannon.nelson@...el.com,
weiyang@...ux.vnet.ibm.com, zajec5@...il.com
Subject: Re: [RFC PATCH V2 3/3] Ixgbevf: Add migration support for ixgbevf
driver
On 2015年11月25日 05:20, Michael S. Tsirkin wrote:
> 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.
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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists