From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH +stable] block: don't attempt to merge overlapping requests
Date: Tue, 18 May 2010 23:41:48 +0400 [thread overview]
Message-ID: <4BF2ED7C.4040807@msgid.tls.msk.ru> (raw)
In-Reply-To: <AANLkTiljDN_CYXjFcCG8zkdTX5c1s8t3sJSq78bVOU9m@mail.gmail.com>
18.05.2010 23:37, Stefan Hajnoczi wrote:
> I just caught up on mails and saw you had already mentioned that
> overlapping writes from the guest look fishy in the "the>1Tb block
> issue". Cache mode might still be interesting because it affects how
> guest virtio-blk chooses queue ordering mode.
What I can say for sure is that the issue mentioned (>1Tb block)
occurs regardless of the cache mode. I tried all 3, with exactly
the same results (well, not entirely exactly, since the prob
depends on timing too, and timing is different depending on the
cache mode), and performed all further tests with cache=writeback
since it's the mode which lets the guest to finish mkfs'ing the
1.5Tb "disk" in a reasonable time (or else it takes hours).
But actually I don't quite see where that dependency is: guest
does not know how its data is cached on host...
/mjt
next prev parent reply other threads:[~2010-05-18 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 17:18 [PATCH +stable] block: don't attempt to merge overlapping requests Avi Kivity
2010-05-18 19:22 ` Stefan Hajnoczi
2010-05-18 19:37 ` Stefan Hajnoczi
2010-05-18 19:41 ` Michael Tokarev [this message]
2010-05-18 20:19 ` Stefan Hajnoczi
2010-05-19 8:09 ` Avi Kivity
2010-05-19 9:01 ` Stefan Hajnoczi
2010-05-19 9:06 ` Avi Kivity
2010-05-19 9:23 ` Stefan Hajnoczi
2010-05-19 9:31 ` Christoph Hellwig
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=4BF2ED7C.4040807@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=avi@redhat.com \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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