qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4341] qemu: generate signals on tap I/O
Date: Mon, 05 May 2008 17:57:24 -0500	[thread overview]
Message-ID: <481F90D4.6090507@codemonkey.ws> (raw)
In-Reply-To: <481F8F74.9010507@aurel32.net>

Aurelien Jarno wrote:
>>> You're seeing improvement with normal QEMU?  Can you please post a
>>> description of what you're seeing improve with SIGIO.  SIGIO should
>>> really only slow things down.
>>>       
>> I haven't tried Anders' patch, but the patch I accidentally committed
>> improved the network speed (tap mode) by a huge factor (I haven't the
>> exact factor in mind anymore). I can now easily reach 170 MBps with an
>>     
>                                                        ^^^^^^^^^^
>                                                   oops that is 170 Mbps
>   

If you explicitly call host_alarm_handler in tap_send(), do you see the 
same improvement?  Perhaps your host timer is just very slow?

Regards,

Anthony Liguori

>> e1000 card on the MIPS Malta target.
>>
>> That's why I use that patch in my local tree.
>>
>>     
>
>
>   

  reply	other threads:[~2008-05-05 22:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05 21:26 [Qemu-devel] [4341] qemu: generate signals on tap I/O Aurelien Jarno
2008-05-05 22:06 ` Anders
2008-05-05 22:15   ` Aurelien Jarno
2008-05-05 22:42     ` Anders
2008-05-05 22:44       ` Anthony Liguori
2008-05-05 22:49         ` Aurelien Jarno
2008-05-05 22:51           ` Aurelien Jarno
2008-05-05 22:57             ` Anthony Liguori [this message]
2008-05-05 23:00               ` Anthony Liguori
2008-05-05 23:12         ` Anders
2008-05-06  2:48           ` Anthony Liguori
2008-05-06  8:35             ` Anders
2008-05-05 22:50       ` Anthony Liguori
2008-05-05 22:43 ` Anthony Liguori

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=481F90D4.6090507@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aurelien@aurel32.net \
    --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).