From: Avi Kivity <avi@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>, KVM list <kvm@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: the >1Tb block issue
Date: Wed, 19 May 2010 12:03:59 +0300 [thread overview]
Message-ID: <4BF3A97F.5000207@redhat.com> (raw)
In-Reply-To: <20100519085722.GA4343@infradead.org>
On 05/19/2010 11:57 AM, Christoph Hellwig wrote:
> On Tue, May 18, 2010 at 08:38:22PM +0300, Avi Kivity wrote:
>> Yes. Why would Linux post overlapping requests? makes
>> 0xffffffff00000000 sense.
>>
>> There may be a guest bug in here too. Christoph?
>
> Overlapping writes are entirely fine from the guest POV, although they
> should be rather unusual. We can update a page and send it out again
> when it gets redirtied while still out on the wire.
But the device may reorder requests:
system device
issue request r1 for sector n page p
dma into buffer b1
modify contents of page p
issue request r2 for sector n page p
dma into buffer b2
complete r2
complete r1
Is there any guarantee r2 will complete after r1, or that b1 and b2 are
coherent? I'm not aware of any.
What about NFS O_DIRECT backing virtio-blk? Here, requests can
definitely be reordered, and the buffers are certainly not coherent
(since they're don't even exist once the data has left the NIC).
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2010-05-19 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 15:52 the >1Tb block issue Michael Tokarev
2010-05-18 15:59 ` Daniel P. Berrange
2010-05-18 16:51 ` Michael Tokarev
2010-05-18 16:58 ` Gleb Natapov
2010-05-18 17:29 ` Avi Kivity
2010-05-18 17:34 ` Michael Tokarev
2010-05-18 17:38 ` Avi Kivity
2010-05-18 18:03 ` Michael Tokarev
2010-05-18 18:09 ` Avi Kivity
2010-05-18 18:38 ` Michael Tokarev
2010-05-18 18:43 ` Michael Tokarev
2010-05-19 8:57 ` Christoph Hellwig
2010-05-19 9:03 ` Avi Kivity [this message]
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=4BF3A97F.5000207@redhat.com \
--to=avi@redhat.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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