From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754558AbZHMNpG (ORCPT ); Thu, 13 Aug 2009 09:45:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754535AbZHMNpE (ORCPT ); Thu, 13 Aug 2009 09:45:04 -0400 Received: from moutng.kundenserver.de ([212.227.126.186]:59338 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753910AbZHMNpD (ORCPT ); Thu, 13 Aug 2009 09:45:03 -0400 From: Arnd Bergmann To: Anthony Liguori Subject: Re: [PATCH 2/2] vhost_net: a kernel-level virtio server Date: Thu, 13 Aug 2009 15:45:00 +0200 User-Agent: KMail/1.12.0 (Linux/2.6.31-5-generic; KDE/4.3.0; x86_64; ; ) Cc: "Michael S. Tsirkin" , virtualization@lists.linux-foundation.org, "Ira W. Snyder" , netdev@vger.kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20090812172141.GA29966@redhat.com> <4A83167E.2080701@codemonkey.ws> In-Reply-To: <4A83167E.2080701@codemonkey.ws> 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: <200908131545.00304.arnd@arndb.de> X-Provags-ID: V01U2FsdGVkX18sZob9tSKQNRV9erZDZxuvLBtIJY7Dui2ii5q l01pyLZ60n36g5gnrd66fxhBEgoL7NzcdKdJAzk0bhDPr6eS20 8BZOE6XTpLytDppfEHItw== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 12 August 2009, Anthony Liguori wrote: > At any rate, I'd like to see performance results before we consider > trying to reuse virtio code. Yes, I agree. I'd also like to do more work on the macvlan extensions to see if it works out without involving a socket. Passing the socket into the vhost_net device is a nice feature of the current implementation that we'd have to give up for something else (e.g. making the vhost a real network interface that you can hook up to a bridge) if it were to use virtio. Unless I can come up with a solution that is clearly superior, I'm taking back my objections on that part for now. Arnd <><