All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Andrew Theurer <habanero@us.ibm.com>
Cc: Steve Dobbelstein <steved@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: Re: HVM network performance
Date: Fri, 5 May 2006 21:33:13 +0200	[thread overview]
Message-ID: <200605052133.13429.ak@suse.de> (raw)
In-Reply-To: <445B9FD0.6050800@us.ibm.com>

On Friday 05 May 2006 20:56, Andrew Theurer wrote:
> Andi Kleen wrote:
> > Steve Dobbelstein <steved@us.ibm.com> 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

  reply	other threads:[~2006-05-05 19:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04 20:42 HVM network performance Steve Dobbelstein
2006-05-05 10:23 ` Andi Kleen
2006-05-05 18:56   ` Andrew Theurer
2006-05-05 19:33     ` Andi Kleen [this message]
2006-05-05 22:25       ` Randy Thelen
2006-05-07  9:15         ` Andi Kleen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200605052133.13429.ak@suse.de \
    --to=ak@suse.de \
    --cc=habanero@us.ibm.com \
    --cc=steved@us.ibm.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.