From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
andrey@xdel.ru, qemu-devel@nongnu.org,
sviatoslav.pestov@gmail.com
Subject: Re: [Qemu-devel] [PATCH 1/2] block: fix overlapping multiwrite requests
Date: Tue, 29 Jul 2014 20:46:56 +0800 [thread overview]
Message-ID: <20140729124656.GC16854@T430.nay.redhat.com> (raw)
In-Reply-To: <1406637686-25762-2-git-send-email-stefanha@redhat.com>
On Tue, 07/29 13:41, Stefan Hajnoczi wrote:
> When request A is a strict subset of request B:
>
> AAAAAAAA
> BBBB
s/subset/superset/ ?
Fam
next prev parent reply other threads:[~2014-07-29 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 12:41 [Qemu-devel] [PATCH 0/2] block: fix multiwrite_merge() overlapping requests Stefan Hajnoczi
2014-07-29 12:41 ` [Qemu-devel] [PATCH 1/2] block: fix overlapping multiwrite requests Stefan Hajnoczi
2014-07-29 12:46 ` Fam Zheng [this message]
2014-07-29 12:52 ` Stefan Hajnoczi
2014-07-29 12:41 ` [Qemu-devel] [PATCH 2/2] qemu-iotests: add multiwrite test cases Stefan Hajnoczi
2014-07-29 15:11 ` Eric Blake
2014-07-30 8:11 ` Stefan Hajnoczi
2014-07-31 18:19 ` Slava Pestov
2014-08-01 10:02 ` 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=20140729124656.GC16854@T430.nay.redhat.com \
--to=famz@redhat.com \
--cc=andrey@xdel.ru \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=sviatoslav.pestov@gmail.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).