From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Venkateswararao Jujjuri <jvrao@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 4/4] coroutine: pool coroutines to speed up creation
Date: Thu, 12 May 2011 13:12:37 +0200 [thread overview]
Message-ID: <4DCBC0A5.9040203@redhat.com> (raw)
In-Reply-To: <4DCBB8AD.7000106@redhat.com>
On 05/12/2011 12:38 PM, Kevin Wolf wrote:
>> I don't want to add qemu-img/qemu-io things yet because we don't have
>> a block layer user for coroutines yet. The qcow2 patches should
>> contain these changes.
>
> I hope we won't forget it. A missing atexit isn't a very obvious bug.
I was going to reply that this atexit is actually useless, since memory
is freed automatically at exit?
Paolo
next prev parent reply other threads:[~2011-05-12 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 9:54 [Qemu-devel] [PATCH v2 0/4] Coroutines for better asynchronous programming Stefan Hajnoczi
2011-05-12 9:54 ` [Qemu-devel] [PATCH v2 1/4] coroutine: introduce coroutines Stefan Hajnoczi
2011-05-12 18:12 ` Blue Swirl
2011-05-12 19:22 ` Stefan Hajnoczi
2011-05-13 8:17 ` Kevin Wolf
2011-05-12 9:54 ` [Qemu-devel] [PATCH v2 2/4] coroutine: add check-coroutine automated tests Stefan Hajnoczi
2011-05-12 9:54 ` [Qemu-devel] [PATCH v2 3/4] coroutine: add check-coroutine --benchmark-lifecycle Stefan Hajnoczi
2011-05-12 9:54 ` [Qemu-devel] [PATCH v2 4/4] coroutine: pool coroutines to speed up creation Stefan Hajnoczi
2011-05-12 10:13 ` Kevin Wolf
2011-05-12 10:22 ` Stefan Hajnoczi
2011-05-12 10:38 ` Kevin Wolf
2011-05-12 11:12 ` Paolo Bonzini [this message]
2011-05-12 11:15 ` Stefan Hajnoczi
2011-05-12 11:18 ` Paolo Bonzini
2011-05-12 11:52 ` 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=4DCBC0A5.9040203@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=jvrao@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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).