qemu-stable
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-stable] [Qemu-devel] [PATCH] block: fix big write


From: Paolo Bonzini
Subject: Re: [Qemu-stable] [Qemu-devel] [PATCH] block: fix big write
Date: Wed, 10 Dec 2014 13:55:17 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0


On 10/12/2014 13:23, Ming Lei wrote:
>> >
>> > Again, we're talking of 2GB and this is something that should never
>> > happen in practice.
> Again, the 2GB limit can be avoided if I/O is splitted, isn't it?

Sure.  The guest kernel is doing the split.

> It is _not_ never happen at all, and easy to be triggered when using
> mkfs.

mkfs is not something to optimize for, it's just something that should
work.  (Also, some hardware may time out if you do write same with too
high a block count).

Both Linux and Windows will always use UNMAP on QEMU, except for the
small time period where Linux used WRITE SAME and this bug was
discovered.  And all versions of Linux that used WRITE SAME honored the
max_ws_blocks field.

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]