From: Andi Kleen <ak@suse.de>
To: Randy Thelen <rthelen@netapp.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: HVM network performance
Date: 07 May 2006 11:15:34 +0200 [thread overview]
Message-ID: <p73y7xe42mh.fsf@bragg.suse.de> (raw)
In-Reply-To: <2A7B286D-B337-421E-A247-44F1C3D2426A@netapp.com>
Randy Thelen <rthelen@netapp.com> writes:
> > 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)
>
> Yes, but given a good back-end driver model, these should be
> relatively simple. Especially if a couple examples were BSD licensed
> to kick start the development of these drivers.
Even if it's simple each by itself it will be a logistical
nightmare. Or do you know how to write driver for all the zillion
versions of old x86 OS people might want to run under the hypervisor?
Probably just getting development environment for all of these
would be "interesting".
> > Also it's a logistical problem because you'll need to distribute
> > and setup
> > all these drivers even if they are written.
>
> I would think the performance benefit would greatly outweigh the
> setup issues.
I would expect a optimized modern NIC model to be not that
much worse than a pure para virtual driver.
> But, what do you mean by 'distribute and setup'?
If the OS don't have a driver already you need to distribute the drivers
in a form that they can be used during installation.
-Andi
prev parent reply other threads:[~2006-05-07 9:15 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
2006-05-05 22:25 ` Randy Thelen
2006-05-07 9:15 ` Andi Kleen [this message]
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=p73y7xe42mh.fsf@bragg.suse.de \
--to=ak@suse.de \
--cc=rthelen@netapp.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.