All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 3/8] block: add request tracking
Date: Mon, 05 Dec 2011 13:20:54 +0100	[thread overview]
Message-ID: <4EDCB726.4040001@redhat.com> (raw)
In-Reply-To: <20111205121748.GA30711@amt.cnet>

On 12/05/2011 01:17 PM, Marcelo Tosatti wrote:
> There is no need to worry about synchronous read/write requests
> bypassing this interface, correct?
>

Synchronous read/write requests do not exist anymore (in the sense that 
they also go through coroutines).

Paolo

  reply	other threads:[~2011-12-05 12:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 11:47 [Qemu-devel] [PATCH v4 0/8] block: generic copy-on-read Stefan Hajnoczi
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 1/8] qemu-common: add QEMU_ALIGN_DOWN() and QEMU_ALIGN_UP() macros Stefan Hajnoczi
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 2/8] coroutine: add qemu_co_queue_restart_all() Stefan Hajnoczi
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 3/8] block: add request tracking Stefan Hajnoczi
2011-12-05 12:17   ` Marcelo Tosatti
2011-12-05 12:20     ` Paolo Bonzini [this message]
2011-12-05 16:09   ` Marcelo Tosatti
2011-12-05 16:20     ` Stefan Hajnoczi
2011-12-05 16:31       ` Marcelo Tosatti
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 4/8] block: add bdrv_set_copy_on_read() Stefan Hajnoczi
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 5/8] block: wait for overlapping requests Stefan Hajnoczi
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 6/8] block: request overlap detection Stefan Hajnoczi
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 7/8] block: core copy-on-read logic Stefan Hajnoczi
2011-12-02 17:13   ` Marcelo Tosatti
2011-12-05 11:35     ` Stefan Hajnoczi
2011-11-23 11:47 ` [Qemu-devel] [PATCH v4 8/8] block: add -drive copy-on-read=on|off 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=4EDCB726.4040001@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@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 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.