From: "andrzej zaborowski" <balrogg@gmail.com>
To: dor.laor@qumranet.com, qemu-devel@nongnu.org
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>, ir Peleg <nir@tutis.com>
Subject: Re: [Qemu-devel] [PATCH] e1000 emulation code
Date: Thu, 10 Jan 2008 17:58:26 +0100 [thread overview]
Message-ID: <fb249edb0801100858h7d91f1d7u3ac6ec67ff7d31ef@mail.gmail.com> (raw)
In-Reply-To: <1199896975.4382.31.camel@localhost.localdomain>
Hi,
On 09/01/2008, Dor Laor <dor.laor@gmail.com> wrote:
> It which supports TCP/UDP and IP transmit checksum, as well as TSO.
> It has been tested with Linux (2.6.18|22|23|24)++ and Windows XP (using
> the driver supplied at the intel download site).
> Windows Vista recognizes it but there is no traffic.
>
> Checksum calculation is currently naïve and unoptimized (the host
> kernel does it better). But when working in conjuction to tso
> the performance is drastically better.
>
> Some figures: Linux rx 350Mbps, tx 150bps, Windows rx 700mbps, tx 100 mbps.
That will be great to have in qemu.
>
> The e1000_hw.h is copied from Linux kernel.
Would it be possible to pick only the useful stuff from the header and
put it into the same file, rather than maintaining a copy of a linux
header (which is 3.5 bigger than the actual emulation in kLoC)? Qemu
has avoided that until now.
> qemu/hw/e1000.c | 1000 +++++++++++++++
> qemu/hw/e1000_hw.h | 3411 ++++++++++++++++++++++++++++++++++++++++++++++++++
Regards.
next prev parent reply other threads:[~2008-01-10 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 16:42 [Qemu-devel] [PATCH] e1000 emulation code Dor Laor
2008-01-09 20:29 ` [Qemu-devel] Re: [kvm-devel] " Alexey Eremenko
2008-01-09 23:40 ` Alex Williamson
2008-01-10 4:08 ` Javier Guerra Giraldez
2008-01-10 11:27 ` Dor Laor
2008-01-10 15:36 ` Paul Brook
2008-01-10 18:58 ` [kvm-devel] [Qemu-devel] " Christoph Hellwig
2008-01-10 16:58 ` andrzej zaborowski [this message]
2008-01-10 23:12 ` [Qemu-devel] " Dor Laor
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=fb249edb0801100858h7d91f1d7u3ac6ec67ff7d31ef@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=dor.laor@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=nir@tutis.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).