From: "Michael Fritscher" <michael@fritscher.net>
To: Michael Fritscher <michael@fritscher.net>
Cc: Samuel Thibault <samuel.thibault@gnu.org>,
Stefan Weil <sw@weilnetz.de>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
QEMU Developer <qemu-devel@nongnu.org>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [Qemu-devel] [PATCH for 2.6] wxx: Fix broken TCP networking (regression)
Date: Fri, 15 Apr 2016 11:35:37 +0200 [thread overview]
Message-ID: <2277028c27fba5fe3c8b29a3c1ea28f3.squirrel@mifritscher.de> (raw)
In-Reply-To: <570FE780.2090600@fritscher.net>
Hello Samuel,
> @Ipv6: I'll test it tomorrow.
Interesting results:
On my native windows builds with msys2 and mingw64, a time wget
http://www.heise.de gives me (tested under native Win7)
real 0m24.081s
user 0m2.313s
sys 0m9.620s
or
real 0m52.250s
user 0m3.647s
sys 0m21.117s
The results are quite the same for IPv4+IPv6 or IPv4 only.
Interestingly, they are working fine under Ubuntu Wine!
Stefan Weil builds (he has made a RC3 build in which the fix is applied)
is a lot faster - tested under native Win7:
real 0m2.581s
user 0m0.227s
sys 0m0480s
My cross builds built with Ubuntu and mingw64 are ok as well (tested under
wine)! I can't test them under Windows, because I got problems with the
vnc viewer...
The qemu command line is
qemu-system-x86_64.exe -m 512 --cdrom
c:\Users\michaelfritscher\Downloads\linux\KNOPPIX_V7.4.2DVD-2014-09-28-DE.iso
-netdev user,id=mynet0,restrict=n -device e1000,netdev=mynet0
A simple openssl speed aes shows roughly the same numbers on both builds.
My configure command: ./configure --target-list=x86_64-softmmu
--enable-sdl --extra-cflags=-mthreads
So:
Stefan build + Windows 7 64 = ok
Native MSYS build + Windows 7 64= slow
Native MSYS build + Ubuntu + Wine = ok
My MingW build + Ubuntu + Wine = ok
My MingW build + Windows 7 = (not testable)
You find my builds under
http://mifritscher.de/austausch/qemu/qemu_msys2.zip and
http://mifritscher.de/austausch/qemu/qemu-linux-mingw64.tar.gz .
Best regards,
Michael Fritscher
next prev parent reply other threads:[~2016-04-15 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 17:46 [Qemu-devel] [PATCH for 2.6] wxx: Fix broken TCP networking (regression) Stefan Weil
2016-04-14 17:53 ` Michael Fritscher
2016-04-14 18:08 ` Samuel Thibault
2016-04-14 18:54 ` Michael Fritscher
2016-04-15 9:35 ` Michael Fritscher [this message]
2016-04-14 19:12 ` Peter Maydell
2016-04-15 9:15 ` Daniel P. Berrange
2016-04-15 16:56 ` Stefan Weil
2016-04-15 16:59 ` Peter Maydell
2016-04-15 17:52 ` Stefan Weil
2016-04-15 9:11 ` Daniel P. Berrange
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=2277028c27fba5fe3c8b29a3c1ea28f3.squirrel@mifritscher.de \
--to=michael@fritscher.net \
--cc=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.org \
--cc=sw@weilnetz.de \
/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).