From: Aurelien Jarno <aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Network performance regression between kvm-29 and kvm-31
Date: Sat, 21 Jul 2007 09:47:57 +0200 [thread overview]
Message-ID: <46A1BA2D.30800@aurel32.net> (raw)
In-Reply-To: <46A1A610.2050603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Avi Kivity a écrit :
> Aurelien Jarno wrote:
>> On Sat, Jul 21, 2007 at 12:25:45AM +0200, Aurelien Jarno wrote:
>>
>>> Hi,
>>>
>>> I have just noticed that there is a huge performance regression in
>>> network transfers between kvm-29 and kvm-31. Using the RTL8139 emulated
>>> card, I have seen the network speed has been divided by 27!!! I haven't
>>> made precise speed measurements with other emulated card, but the
>>> network speed has been reduced by the same order.
>>>
>>> Those tests have been done on a Core 2 CPU.
>>>
>>> After some tests I have seen that the problem lies in the user part. I
>>> will do a git bisect tomorrow to find the patch that has caused the
>>> problem, unless somebody already find it.
>>>
>> I finally didn't resist to run git bisect before going to bed...
>>
>> The patch that causes the regression is:
>>
>> commit 7d2e674835492040c9baddf0989a95abea9a8d0f
>> Author: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
>> Date: Sun Jul 15 15:08:23 2007 +0300
>>
>> kvm: qemu: synchronous signal handling
>>
>> in order to ensure that signals are handled with the global lock held, we
>> block them, and dequeue them with sigtimedwait(). we can then call the
>> handlers directly.
>>
>> this ensures that the device model and internal qemu data structures are not
>> corrupted by cpu 0 thread handling a signal while cpu 1 is servicing a pio
>> or mmio request.
>>
>>
>
> Is this with -net user or -net tap?
>
With -net tap.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org | aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org
`- people.debian.org/~aurel32 | www.aurel32.net
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-07-21 7:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 22:25 Network performance regression between kvm-29 and kvm-31 Aurelien Jarno
[not found] ` <20070720222545.GB22656-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-20 22:58 ` Aurelien Jarno
[not found] ` <20070720225813.GA24368-OqXK5JiLQY5aJl8KAwiEcA@public.gmane.org>
2007-07-21 6:22 ` Avi Kivity
[not found] ` <46A1A610.2050603-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-21 7:47 ` Aurelien Jarno [this message]
[not found] ` <46A1BA2D.30800-rXXEIb44qovR7s880joybQ@public.gmane.org>
2007-07-22 10:30 ` Avi Kivity
[not found] ` <46A331B6.7020306-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-22 13:29 ` Aurelien Jarno
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=46A1BA2D.30800@aurel32.net \
--to=aurelien-rxxeib44qovr7s880joybq@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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