qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Linux SIGIO handling changes
Date: Sun, 20 Apr 2008 17:04:25 -0500	[thread overview]
Message-ID: <480BBDE9.5040209@codemonkey.ws> (raw)
In-Reply-To: <12086832292508-git-send-email-mail@flac.kalibalik.dk>

Anders Melchiorsen wrote:
> I am resending this patch, split into two parts now.
>
> This cleans up SIGIO handling to improve latency:
> - SIGALRM for alarm timers
> - enable SIGIO on qemu_set_fd_handler2()
>
> The issue was found in KVM, where it is much more visible,
> because there is no periodic timer. However, it has been
> confirmed (by Aurelien Jarno) that even for qemu, this
> approach "improves network transfers in a huge way".
>
> Please apply, or give a firm rejection so I can stop resending.
>   

Probably the right thing to do is the direction KVM is moving toward, 
i.e. have a separate IO thread.

Setting SIGIO on every file descriptor is really just a hack to break 
out of the cpu exec loop.  It's unclear to me whether it's really always 
the right thing to do for every file descriptor.

Regards,

Anthony Liguori

> Cheers,
> Anders.
>
>
>
>   

  parent reply	other threads:[~2008-04-20 22:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-20  9:20 [Qemu-devel] Linux SIGIO handling changes Anders Melchiorsen
2008-04-20  9:20 ` [Qemu-devel] [PATCH] Use SIGALRM even for timers delivered over a fd Anders Melchiorsen
2008-04-20  9:20   ` [Qemu-devel] [PATCH] Use SIGIO in Linux host Anders Melchiorsen
2008-04-20 22:04 ` Anthony Liguori [this message]
2008-04-21 13:37   ` [Qemu-devel] Linux SIGIO handling changes Avi Kivity
2008-04-21 15:43     ` Anthony Liguori
2008-04-21 16:13       ` Paul Brook
2008-04-21 18:48         ` Anthony Liguori
2008-04-22  8:02       ` Avi Kivity

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=480BBDE9.5040209@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).