qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: wang sheng <wansheg@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: How can I understand CONFIG_IO_THREAD ?
Date: Mon, 21 Feb 2011 09:16:55 +0100	[thread overview]
Message-ID: <4D621F77.3080802@redhat.com> (raw)
In-Reply-To: <AANLkTi=N4JweMvDP=v4z4Ndu=-L2MzuJ14rWNxOEZi3R@mail.gmail.com>

On 02/21/2011 04:13 AM, wang sheng wrote:
> What is the purpose of io_thread desigment in qemu ?

There was a lengthy thread recently explaining how it helps fixing a 
possibly delay in handling I/O.  It is also useful for KVM, where you 
have one I/O thread and multiple CPU threads.  This way, KVM can 
implement "real" SMP (i.e. multiple virtual CPUs running concurrently).

Paolo

  reply	other threads:[~2011-02-21  8:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21  3:13 [Qemu-devel] How can I understand CONFIG_IO_THREAD ? wang sheng
2011-02-21  8:16 ` Paolo Bonzini [this message]
2011-02-21  9:29   ` [Qemu-devel] " 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=4D621F77.3080802@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wansheg@gmail.com \
    /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).