Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751296AbZIVSew (ORCPT ); Tue, 22 Sep 2009 14:34:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751161AbZIVSew (ORCPT ); Tue, 22 Sep 2009 14:34:52 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:61255 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751107AbZIVSeu (ORCPT ); Tue, 22 Sep 2009 14:34:50 -0400 From: Arnd Bergmann To: Stephen Hemminger Subject: Re: [RFC] Virtual Machine Device Queues(VMDq) support on KVM Date: Tue, 22 Sep 2009 20:34:28 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.31-10-generic; KDE/4.3.1; x86_64; ; ) Cc: "Michael S. Tsirkin" , Chris Wright , Rusty Russell , virtualization@lists.linux-foundation.org, "Xin, Xiaohui" , "kvm@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-mm@kvack.org" , "hpa@zytor.com" , "mingo@elte.hu" , "akpm@linux-foundation.org" References: <200909221350.54847.arnd@arndb.de> <20090922092957.17e68cbc@s6510> In-Reply-To: <20090922092957.17e68cbc@s6510> X-Face: I@=L^?./?$U,EK.)V[4*>`zSqm0>65YtkOe>TFD'!aw?7OVv#~5xd\s,[~w]-J!)|%=]> =?utf-8?q?+=0A=09=7EohchhkRGW=3F=7C6=5FqTmkd=5Ft=3FLZC=23Q-=60=2E=60Y=2Ea=5E?= =?utf-8?q?3zb?=) =?utf-8?q?+U-JVN=5DWT=25cw=23=5BYo0=267C=26bL12wWGlZi=0A=09=7EJ=3B=5Cwg?= =?utf-8?q?=3B3zRnz?=,J"CT_)=\H'1/{?SR7GDu?WIopm.HaBG=QYj"NZD_[zrM\Gip^U MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200909222034.28865.arnd@arndb.de> X-Provags-ID: V01U2FsdGVkX19zU4lnGyDT5ZH7UNEOyzwbP1PHgjxQp0BfgYr YdWplNeazAT5CrmUt/9//0srAKA7a3vJUZcLCqLb9EsKCo3Om4 AAhn2EjI5Jd0J+hPHwjiA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1113 Lines: 23 On Tuesday 22 September 2009, Stephen Hemminger wrote: > > My idea for that was to open multiple file descriptors to the same > > macvtap device and let the kernel figure out the right thing to > > do with that. You can do the same with raw packed sockets in case > > of vhost_net, but I wouldn't want to add more complexity to the > > tun/tap driver for this. > > > Or get tap out of the way entirely. The packets should not have > to go out to user space at all (see veth) How does veth relate to that, do you mean vhost_net? With vhost_net, you could still open multiple sockets, only the access is in the kernel. Obviously, once it all is in the kernel, that could be done under the covers, but I think it would be cleaner to treat vhost_net purely as a way to bypass the syscalls for user space, with as little as possible visible impact otherwise. Arnd <>< -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/