From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [RFC] dataplane: IOThreads and writing dataplane-capable code
Date: Thu, 08 May 2014 15:10:48 +0200 [thread overview]
Message-ID: <536B8258.2020902@redhat.com> (raw)
In-Reply-To: <20140508130846.GC4034@noname.redhat.com>
Il 08/05/2014 15:08, Kevin Wolf ha scritto:
> Am 08.05.2014 um 12:16 hat Stefan Hajnoczi geschrieben:
>> Side note: The main loop and IOThread are both event loops but their code is
>> not shared completely. Sometimes it is useful to remember that although they
>> are conceptually similar they are currently not interchangeable.
>
> We need to be careful with the terminology. The choice made here, that
> the main loop thread is not an IOThread, is somewhat unfortunate,
> because traditionally, the "I/O thread" has been what the main loop
> thread is called (in contrast to vcpu threads).
Note that the main loop thread could definitely be an IOThread, since it
has an AioContext and the IOThread is just a QOM veneer for AioContext.
It's just not done yet.
Paolo
next prev parent reply other threads:[~2014-05-08 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 10:16 [Qemu-devel] [RFC] dataplane: IOThreads and writing dataplane-capable code Stefan Hajnoczi
2014-05-08 11:33 ` Fam Zheng
2014-05-08 11:56 ` Stefan Hajnoczi
2014-05-08 12:12 ` Paolo Bonzini
2014-05-08 13:08 ` Kevin Wolf
2014-05-08 13:10 ` Paolo Bonzini [this message]
2014-05-08 13:18 ` Stefan Hajnoczi
2014-05-08 13:44 ` Dr. David Alan Gilbert
2014-05-08 14:42 ` Stefan Hajnoczi
2014-05-08 18:58 ` Dr. David Alan Gilbert
2014-05-09 8:20 ` 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=536B8258.2020902@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).