From: Paolo Bonzini <pbonzini@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 5/8] block: wait for overlapping requests
Date: Thu, 17 Nov 2011 14:43:51 +0100 [thread overview]
Message-ID: <4EC50F97.4090802@redhat.com> (raw)
In-Reply-To: <1321537232-799-6-git-send-email-stefanha@linux.vnet.ibm.com>
On 11/17/2011 02:40 PM, Stefan Hajnoczi wrote:
> When copy-on-read is enabled it is necessary to wait for overlapping
> requests before issuing new requests. This prevents races between the
> copy-on-read and a write request.
What about discards?
Paolo
next prev parent reply other threads:[~2011-11-17 13:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 13:40 [Qemu-devel] [PATCH v2 0/8] block: generic copy-on-read Stefan Hajnoczi
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 1/8] qemu-common: add QEMU_ALIGN_DOWN() and QEMU_ALIGN_UP() macros Stefan Hajnoczi
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 2/8] coroutine: add qemu_co_queue_restart_all() Stefan Hajnoczi
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 3/8] block: add request tracking Stefan Hajnoczi
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 4/8] block: add bdrv_set_copy_on_read() Stefan Hajnoczi
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 5/8] block: wait for overlapping requests Stefan Hajnoczi
2011-11-17 13:43 ` Paolo Bonzini [this message]
2011-11-17 13:51 ` Stefan Hajnoczi
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 6/8] block: request overlap detection Stefan Hajnoczi
2011-11-22 15:06 ` Kevin Wolf
2011-11-22 15:10 ` Stefan Hajnoczi
2011-11-22 16:36 ` Kevin Wolf
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 7/8] block: core copy-on-read logic Stefan Hajnoczi
2011-11-23 3:42 ` Zhi Yong Wu
2011-11-23 9:05 ` Stefan Hajnoczi
2011-11-23 9:51 ` Zhi Yong Wu
2011-11-23 4:42 ` Zhi Yong Wu
2011-11-23 8:58 ` Stefan Hajnoczi
2011-11-23 9:00 ` Stefan Hajnoczi
2011-11-17 13:40 ` [Qemu-devel] [PATCH v2 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=4EC50F97.4090802@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 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).