From: Javier Guerra Giraldez <javier-796Irmz5ZkZBDgjK7y7TUQ@public.gmane.org>
To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org
Cc: ir Peleg <nir-DHAoeUZcRjAAvxtiuMwx3w@public.gmane.org>,
qemu-devel <qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] e1000 emulation code
Date: Wed, 9 Jan 2008 23:08:45 -0500 [thread overview]
Message-ID: <200801092308.46482.javier@guerrag.com> (raw)
In-Reply-To: <1199896975.4382.31.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
On Wednesday 09 January 2008, Dor Laor wrote:
> Some figures: Linux rx 350Mbps, tx 150bps, Windows rx 700mbps, tx 100 mbps.
very nice!
in a related note, the VMWare tools package, which is supposed to 'enhance
performance' by installing 'specially tuned' drivers into a guest, doesn't
include net or HD drivers for linux! i was surprised, but it simply said
that using e1000 emulation on 64bit linux was optimised enough. since i saw
good performance (no hard benchmarks, but definitely not bad); i thought that
they do some paravirtualizification at runtime as part of their software
recompiling (because they're much older than HVM-capable processors).
now it seems that there are higher-level hardware that can be emulated far
more efficiently than the original set of QEMU hardware.
the next step would be to emulate LSI SCSI chips, eh?
--
Javier
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 278 bytes --]
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
[-- Attachment #3: Type: text/plain, Size: 186 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2008-01-10 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 16:42 [PATCH] e1000 emulation code Dor Laor
[not found] ` <1199896975.4382.31.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-09 20:29 ` Alexey Eremenko
2008-01-09 23:40 ` Alex Williamson
2008-01-10 4:08 ` Javier Guerra Giraldez [this message]
[not found] ` <200801092308.46482.javier-796Irmz5ZkZBDgjK7y7TUQ@public.gmane.org>
2008-01-10 11:27 ` Dor Laor
2008-01-10 15:36 ` [Qemu-devel] " Paul Brook
[not found] ` <200801101536.20530.paul-qD8j1LwMmJjtCj0u4l0SBw@public.gmane.org>
2008-01-10 18:58 ` Christoph Hellwig
2008-01-10 16:58 ` [Qemu-devel] " andrzej zaborowski
[not found] ` <fb249edb0801100858h7d91f1d7u3ac6ec67ff7d31ef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-01-10 23:12 ` Dor Laor
[not found] ` <4786A66F.1010509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-11 0:35 ` andrzej zaborowski
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=200801092308.46482.javier@guerrag.com \
--to=javier-796irmz5zkzbdgjk7y7tuq@public.gmane.org \
--cc=dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=nir-DHAoeUZcRjAAvxtiuMwx3w@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox