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
| ||
|
Message-ID: <20100620114719.GC5285@redhat.com> Date: Sun, 20 Jun 2010 14:47:19 +0300 From: "Michael S. Tsirkin" <mst@...hat.com> To: Herbert Xu <herbert@...dor.hengli.com.au> Cc: "Xin, Xiaohui" <xiaohui.xin@...el.com>, Stephen Hemminger <shemminger@...tta.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "mingo@...e.hu" <mingo@...e.hu>, "davem@...emloft.net" <davem@...emloft.net>, "jdike@...ux.intel.com" <jdike@...ux.intel.com>, Rusty Russell <rusty@...tcorp.com.au> Subject: Re: [RFC PATCH v7 01/19] Add a new structure for skb buffer from external. On Sun, Jun 20, 2010 at 09:36:09PM +1000, Herbert Xu wrote: > On Sun, Jun 20, 2010 at 02:11:24PM +0300, Michael S. Tsirkin wrote: > > > > Rather than modifying all guests, it seems much easier not to assume > > specific buffer layout in host. Copying network header around seems a > > small cost. > > Well sure we can debate the specifics of this implementation detail. Let's do this then. So far the virtio spec avoided making layout assumptions, leaving guests lay out data as they see fit. Isn't it possible to keep supporting this with zero copy for hardware that can issue DMA at arbitrary addresses? > However, the fact that virtio_net doesn't support feature renegotiation > on live migration is not a valid reason against this. > > Cheers, -- MST -- 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