From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Re: HVM network performance Date: Fri, 5 May 2006 21:33:13 +0200 Message-ID: <200605052133.13429.ak@suse.de> References: <445B9FD0.6050800@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <445B9FD0.6050800@us.ibm.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andrew Theurer Cc: Steve Dobbelstein , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Friday 05 May 2006 20:56, Andrew Theurer wrote: > Andi Kleen wrote: > > Steve Dobbelstein writes: > > > >> I don't see any obvious problems in the Xenoprof output. Anyone with > >> experience with the inner workings of HVM domains care to comment on what > >> might be causing the network performance to suffer so much? > >> > > > > You'll never get good throughput either from a NE2000 nor from a pcnet32 > > model. > > > That was a suspicion of mine, but I wasn't sure. I wonder if qemu-dm > could emulate another adapter (if so, which one would be best?) I looked some time ago at specs but all the promising adapters (widely used, good features, not too broken design) had very restrictive license terms on their specifications (if they were available) They tended to only allow using the specification to write drivers for the hardware. > or do we > just punt and go for para-virt drivers. That's the easy and probably fastest way short term, but long term it's a lot more work (you will need to write drivers for all the old and new guest OS you want to run to get good performance) Also it's a logistical problem because you'll need to distribute and setup all these drivers even if they are written. -Andi