From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org, MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
Subject: Re: [Qemu-devel] [PATCH 2/6] sheepdog: restart I/O when socket becomes ready in do_co_req()
Date: Tue, 03 Jul 2012 15:44:02 +0200 [thread overview]
Message-ID: <4FF2F722.8080808@redhat.com> (raw)
In-Reply-To: <4FF2EF0E.2030802@redhat.com>
Il 03/07/2012 15:09, Kevin Wolf ha scritto:
>> > Signed-off-by: MORITA Kazutaka <morita.kazutaka@lab.ntt.co.jp>
>> > ---
>> > block/sheepdog.c | 14 ++++++++++++++
>> > 1 files changed, 14 insertions(+), 0 deletions(-)
> Paolo, is this how qemu_co_recv/send are supposed to be used?
Yes.
> Shouldn't
> the functions take care of reentering the coroutine like the block
> functions do?
No, because qemu_co_recv/send are generic outside the block layer and
they don't have enough context from the caller to set up the handler.
For example qemu_co_send to keep the recv handler, but in turn the recv
handler might have its own opaque.
In fact, qemu_co_recv/send originated in sheepdog :) so they are (even
with all the refactoring that went in since) Kazutaka's pet too!
Paolo
next prev parent reply other threads:[~2012-07-03 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340749583-5292-1-git-send-email-morita.kazutaka@lab.ntt.co.jp>
[not found] ` <1340749583-5292-3-git-send-email-morita.kazutaka@lab.ntt.co.jp>
2012-07-03 13:09 ` [Qemu-devel] [PATCH 2/6] sheepdog: restart I/O when socket becomes ready in do_co_req() Kevin Wolf
2012-07-03 13:44 ` Paolo Bonzini [this message]
[not found] ` <1340749583-5292-4-git-send-email-morita.kazutaka@lab.ntt.co.jp>
2012-07-03 13:15 ` [Qemu-devel] [PATCH 3/6] sheepdog: use coroutine based socket functions in coroutine context Kevin Wolf
2012-07-04 0:25 ` Peter Crosthwaite
2012-07-04 8:37 ` Kevin Wolf
2012-07-04 15:27 ` MORITA Kazutaka
2012-07-03 13:26 ` [Qemu-devel] [PATCH 0/6] sheepdog: various fixes Kevin Wolf
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=4FF2F722.8080808@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=morita.kazutaka@lab.ntt.co.jp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.