| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 26 Oct 2015 13:36:09 +0800 From: Lan Tianyu <tianyu.lan@...el.com> To: Alexander Duyck <alexander.duyck@...il.com>, bhelgaas@...gle.com, carolyn.wyborny@...el.com, donald.c.skidmore@...el.com, eddie.dong@...el.com, nrupal.jani@...el.com, yang.z.zhang@...el.com, agraf@...e.de, kvm@...r.kernel.org, pbonzini@...hat.com, qemu-devel@...gnu.org, emil.s.tantilov@...el.com, intel-wired-lan@...ts.osuosl.org, jeffrey.t.kirsher@...el.com, jesse.brandeburg@...el.com, john.ronciak@...el.com, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, matthew.vick@...el.com, mitch.a.williams@...el.com, netdev@...r.kernel.org, shannon.nelson@...el.com Subject: Re: [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC On 2015年10月24日 02:36, Alexander Duyck wrote: > I was thinking about it and I am pretty sure the dummy write approach is > problematic at best. Specifically the issue is that while you are > performing a dummy write you risk pulling in descriptors for data that > hasn't been dummy written to yet. So when you resume and restore your > descriptors you will have once that may contain Rx descriptors > indicating they contain data when after the migration they don't. How about changing sequence? dummy writing Rx packet data fist and then its desc. This can ensure that RX data is migrated before its desc and prevent such case. -- 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