From: Dor Laor <dor.laor-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: andrzej zaborowski <balrogg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
ir Peleg <nir-DHAoeUZcRjAAvxtiuMwx3w@public.gmane.org>,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: [Qemu-devel] [PATCH] e1000 emulation code
Date: Fri, 11 Jan 2008 01:12:47 +0200 [thread overview]
Message-ID: <4786A66F.1010509@qumranet.com> (raw)
In-Reply-To: <fb249edb0801100858h7d91f1d7u3ac6ec67ff7d31ef-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
andrzej zaborowski wrote:
> 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.
>
>
I can but then how can you compile qemu for OS's which do not have
Linux/ or linux headers?
>> qemu/hw/e1000.c | 1000 +++++++++++++++
>> qemu/hw/e1000_hw.h | 3411 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>
> Regards.
>
-------------------------------------------------------------------------
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
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2008-01-10 23:12 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
[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 [this message]
[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=4786A66F.1010509@qumranet.com \
--to=dor.laor-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=balrogg-Re5JQEeQqe8AvxtiuMwx3w@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