From: Michael Fritscher <michael@fritscher.net>
To: Samuel Thibault <samuel.thibault@gnu.org>, Stefan Weil <sw@weilnetz.de>
Cc: QEMU Developer <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH for 2.6] wxx: Fix broken TCP networking (regression)
Date: Thu, 14 Apr 2016 20:54:56 +0200 [thread overview]
Message-ID: <570FE780.2090600@fritscher.net> (raw)
In-Reply-To: <20160414180804.GE3189@var.upmc.fr>
Hello Samuel,
> Michael, what do you mean by "slow", the bandwidth, or the time to
> connect? Does it help if you disable ipv6?
@Ipv6: I'll test it tomorrow.
I tested with wget http://www.heise.de.
On the guest program point of view, it seems to hang at waiting at the
first patch of data after sending the request. (see the screenshot I
sent you directly). After starting receiving, it seems as the data were
here instantly (a bit slowed down by the strace, but this was very much
faster than the wait for the beginning of the response).
Another thing: The tcpdump which was running within qemu dropped 30 out
of 83 packets... It was running on a Skylake based Xeon CPU with almost
3 GHz - so I think this shouldn't be a problem^^ I sent you the tcpdumps
directly as well.
I tested it on Windows 7 64 bit.
Best regards,
Michael
next prev parent reply other threads:[~2016-04-14 18:55 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 [this message]
2016-04-15 9:35 ` Michael Fritscher
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=570FE780.2090600@fritscher.net \
--to=michael@fritscher.net \
--cc=berrange@redhat.com \
--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).