From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shirley Ma Subject: RE: [RFC PATCH v8 00/16] Provide a zero-copy method on KVM virtio-net. Date: Fri, 30 Jul 2010 08:51:52 -0700 Message-ID: <1280505112.9058.31.camel@localhost.localdomain> References: <1280402088-5849-1-git-send-email-xiaohui.xin@intel.com> <1280442682.9058.15.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: "netdev@vger.kernel.org" , "kvm@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "mst@redhat.com" , "mingo@elte.hu" , "davem@davemloft.net" , "herbert@gondor.apana.org.au" , "jdike@linux.intel.com" To: "Xin, Xiaohui" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org Hello Xiaohui, On Fri, 2010-07-30 at 16:53 +0800, Xin, Xiaohui wrote: > >Since vhost-net already supports macvtap/tun backends, do you think > >whether it's better to implement zero copy in macvtap/tun than > inducing > >a new media passthrough device here? > > > > I'm not sure if there will be more duplicated code in the kernel. I think it should be less duplicated code in the kernel if we use macvtap to support what media passthrough driver here. Since macvtap has support virtio_net head and offloading already, the only missing func is zero copy. Also QEMU supports macvtap, we just need add a zero copy flag in option. Thanks Shirley