From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH 01/12] coroutine: Add gtk-vnc coroutines library
Date: Wed, 26 Jan 2011 17:25:39 +0200 [thread overview]
Message-ID: <4D403CF3.8080102@redhat.com> (raw)
In-Reply-To: <1295688567-25496-2-git-send-email-stefanha@linux.vnet.ibm.com>
On 01/22/2011 11:29 AM, Stefan Hajnoczi wrote:
> Asynchronous image format code is becoming very complex. Let's try
> using coroutines to write sequential code without callbacks but use
> coroutines to switch stacks under the hood.
>
>
> +
> +int cc_swap(struct continuation *from, struct continuation *to)
> +{
> + to->exited = 0;
> + if (getcontext(&to->last) == -1)
> + return -1;
> + else if (to->exited == 0)
> + to->exited = 1;
> + else if (to->exited == 1)
> + return 1;
> +
> + return swapcontext(&from->uc,&to->uc);
> +}
swapcontext() is very slow, involving the fpu and a syscall.
A nice trick I've used in the past is to use getcontext/makecontext for
the initial setup and setjmp/longjmp for switching. Of course this can
be done later, as an optimization.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-01-26 15:27 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 9:29 [Qemu-devel] [RFC][PATCH 00/12] qcow2: Convert qcow2 to use coroutines for async I/O Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 01/12] coroutine: Add gtk-vnc coroutines library Stefan Hajnoczi
2011-01-26 15:25 ` Avi Kivity [this message]
2011-01-26 16:00 ` Anthony Liguori
2011-01-26 16:13 ` Avi Kivity
2011-01-26 16:19 ` Anthony Liguori
2011-01-26 16:22 ` Avi Kivity
2011-01-26 16:29 ` Anthony Liguori
2011-01-26 16:21 ` Anthony Liguori
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 02/12] continuation: Fix container_of() redefinition Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 03/12] Make sure to release allocated stack when coroutine is released Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 04/12] coroutine: Use thread-local leader and current variables Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 05/12] coroutine: Add coroutines Stefan Hajnoczi
2011-01-26 15:29 ` Avi Kivity
2011-01-26 16:00 ` Anthony Liguori
2011-01-27 9:40 ` Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 06/12] coroutine: Add qemu_coroutine_self() Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 07/12] coroutine: Add coroutine_is_leader() Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 08/12] coroutine: Add qemu_in_coroutine() Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 09/12] block: Add bdrv_co_readv() and bdrv_co_writev() Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 10/12] block: Add coroutine support to synchronous I/O functions Stefan Hajnoczi
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 11/12] qcow2: Convert qcow2 to use coroutines for async I/O Stefan Hajnoczi
2011-01-23 23:40 ` Anthony Liguori
2011-01-24 11:09 ` Stefan Hajnoczi
2011-01-26 15:40 ` Avi Kivity
2011-01-26 15:50 ` Kevin Wolf
2011-01-26 16:08 ` Anthony Liguori
2011-01-26 16:13 ` Avi Kivity
2011-01-26 16:28 ` Anthony Liguori
2011-01-26 16:38 ` Avi Kivity
2011-01-26 17:12 ` Anthony Liguori
2011-01-27 9:25 ` Avi Kivity
2011-01-27 9:27 ` Kevin Wolf
2011-01-27 9:49 ` Avi Kivity
2011-01-27 10:34 ` Kevin Wolf
2011-01-27 10:41 ` Avi Kivity
2011-01-27 11:27 ` Kevin Wolf
2011-01-27 12:21 ` Avi Kivity
2011-01-26 16:08 ` Avi Kivity
2011-01-27 10:09 ` Stefan Hajnoczi
2011-01-27 10:46 ` Avi Kivity
2011-01-22 9:29 ` [Qemu-devel] [RFC][PATCH 12/12] qcow2: Serialize all requests Stefan Hajnoczi
2011-01-23 23:31 ` [Qemu-devel] [RFC][PATCH 00/12] qcow2: Convert qcow2 to use coroutines for async I/O Anthony Liguori
2011-02-01 13:23 ` Kevin Wolf
2011-01-24 11:58 ` [Qemu-devel] " Kevin Wolf
2011-01-24 13:10 ` 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=4D403CF3.8080102@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--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).