Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764147AbZDBPGR (ORCPT ); Thu, 2 Apr 2009 11:06:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1762955AbZDBPAg (ORCPT ); Thu, 2 Apr 2009 11:00:36 -0400 Received: from mx2.redhat.com ([66.187.237.31]:53448 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1762950AbZDBPAe (ORCPT ); Thu, 2 Apr 2009 11:00:34 -0400 Message-ID: <49D4D301.2090209@redhat.com> Date: Thu, 02 Apr 2009 18:00:17 +0300 From: Avi Kivity User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: Herbert Xu CC: Gregory Haskins , Rusty Russell , anthony@codemonkey.ws, andi@firstfloor.org, linux-kernel@vger.kernel.org, agraf@suse.de, pmullaney@novell.com, pmorreale@novell.com, netdev@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [RFC PATCH 00/17] virtual-bus References: <20090402085253.GA29932@gondor.apana.org.au> <49D487A6.407@redhat.com> <49D49C1F.6030306@novell.com> <200904022243.21088.rusty@rustcorp.com.au> <49D4B4A3.5070008@novell.com> <49D4B87D.2000202@redhat.com> <20090402145018.GA816@gondor.apana.org.au> In-Reply-To: <20090402145018.GA816@gondor.apana.org.au> 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: 1051 Lines: 28 Herbert Xu wrote: > On Thu, Apr 02, 2009 at 04:07:09PM +0300, Avi Kivity wrote: > >> I think Rusty did mean a UP guest, and without schedule-and-forget. >> > > Going off on a tangent here, I don't really think it should matter > whether we're UP or SMP. The ideal state is where we have the > same number of (virtual) TX queues as there are cores in the guest. > On the host side we need the backend to run at least on a core > that shares cache with the corresponding guest queue/core. If > that happens to be the same core as the guest core then it should > work as well. > > IOW we should optimise it as if the host were UP. > Good point - if we rely on having excess cores in the host, large guest scalability will drop. -- 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/