qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] vl.c:main_loop() non-blocking TCG optimization still useful?
Date: Tue, 2 Feb 2016 13:29:39 +0000	[thread overview]
Message-ID: <CAJSP0QXhTwqZDEDervaDx9S1oaDJ+rHFx1GiRHoDXThhLb-Krg@mail.gmail.com> (raw)

Hi Jan,
In 2011 the following patch was merged to optimize I/O vs vcpu scheduling:

commit c9f711a5d31e22dac932c1c01e9c0f97caff0988
Author: Jan Kiszka <jan.kiszka@siemens.com>
Date:   Mon Aug 22 17:46:02 2011 +0200

    Poll main loop after I/O events were received

This was back in the days of CONFIG_IOTHREAD.  Things have changed
quite a bit since then.

Do you think the last_io/non-blocking trick is still needed today in TCG?

Thanks,
Stefan

             reply	other threads:[~2016-02-02 13:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 13:29 Stefan Hajnoczi [this message]
2016-02-02 13:39 ` [Qemu-devel] vl.c:main_loop() non-blocking TCG optimization still useful? Jan Kiszka
2016-02-08 16:41   ` Stefan Hajnoczi

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=CAJSP0QXhTwqZDEDervaDx9S1oaDJ+rHFx1GiRHoDXThhLb-Krg@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=jan.kiszka@web.de \
    --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).