Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754161AbZLVRGO (ORCPT ); Tue, 22 Dec 2009 12:06:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754103AbZLVRGM (ORCPT ); Tue, 22 Dec 2009 12:06:12 -0500 Received: from mx1.redhat.com ([209.132.183.28]:13336 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753666AbZLVRGL (ORCPT ); Tue, 22 Dec 2009 12:06:11 -0500 Message-ID: <4B30FC5B.80506@redhat.com> Date: Tue, 22 Dec 2009 19:05:31 +0200 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 MIME-Version: 1.0 To: Andi Kleen CC: Anthony Liguori , Gregory Haskins , Ingo Molnar , kvm@vger.kernel.org, Andrew Morton , torvalds@linux-foundation.org, "linux-kernel@vger.kernel.org" , netdev@vger.kernel.org, "alacrityvm-devel@lists.sourceforge.net" Subject: Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33 References: <4B2F9582.5000002@gmail.com> <4B2F978D.7010602@redhat.com> <4B2F9C85.7070202@gmail.com> <4B2FA42F.3070408@codemonkey.ws> <4B2FA655.6030205@gmail.com> <4B2FAE7B.9030005@codemonkey.ws> <4B2FB3F1.5080808@gmail.com> <4B300EF8.8010602@codemonkey.ws> <87637zdy9g.fsf@basil.nowhere.org> <4B30E654.40702@codemonkey.ws> <20091222162110.GG10314@basil.fritz.box> In-Reply-To: <20091222162110.GG10314@basil.fritz.box> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1431 Lines: 36 On 12/22/2009 06:21 PM, Andi Kleen wrote: >> So far, the only actual technical advantage I've seen is that vbus avoids >> EOI exits. >> > The technical advantage is that it's significantly faster today. > > Maybe your proposed alternative is as fast, or maybe it's not. Who knows? > We're working on numbers for the proposed alternative, so we should know soon. Are the AlacrityVM folks working on having all the virtio drivers for all the virtio archs? We shouldn't drop everything and switch to new code just because someone came up with a new idea. The default should be to enhance the existing code. >> We think we understand why vbus does better than the current userspace >> virtio backend. That's why we're building vhost-net. It's not done yet, >> but our expectation is that it will do just as well if not better. >> > That's the vapourware vs working code disconnect I mentioned. One side has hard > numbers&working code and the other has expectations. I usually find it sad when the > vapourware holds up the working code. > vhost-net is working code and is queued for 2.6.33. -- error compiling committee.c: too many arguments to function -- 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/