Il 24/08/2014 21:31, Peter Lieven ha scritto:
Am 24.08.2014 um 18:30 schrieb Paolo Bonzini:
Il 22/08/2014 10:42, Kevin Wolf ha scritto:
Unfortunately, I missed that one. The zeroblock is typicalls 512 Byte or
4K depending
on the blocksize.
I don't remember the details, but I think when I
On 25.08.2014 10:56, Paolo Bonzini wrote:
Il 24/08/2014 21:31, Peter Lieven ha scritto:
Am 24.08.2014 um 18:30 schrieb Paolo Bonzini:
Il 22/08/2014 10:42, Kevin Wolf ha scritto:
Unfortunately, I missed that one. The zeroblock is typicalls 512 Byte or 4K
depending
on the blocksize.
I don't
Il 22/08/2014 10:42, Kevin Wolf ha scritto:
Unfortunately, I missed that one. The zeroblock is typicalls 512 Byte or 4K
depending
on the blocksize.
I don't remember the details, but I think when I went through all
drivers, I couldn't convince myself that a reasonable block size is
Am 24.08.2014 um 18:30 schrieb Paolo Bonzini:
Il 22/08/2014 10:42, Kevin Wolf ha scritto:
Unfortunately, I missed that one. The zeroblock is typicalls 512 Byte or 4K
depending
on the blocksize.
I don't remember the details, but I think when I went through all
drivers, I couldn't convince
Am 22.08.2014 um 09:35 schrieb Peter Lieven:
Some code in the block layer makes potentially huge allocations. Failure
is not completely unexpected there, so avoid aborting qemu and handle
out-of-memory situations gracefully.
This patch addresses the allocations in the iscsi block driver.
Am 22.08.2014 um 09:40 hat Peter Lieven geschrieben:
Am 22.08.2014 um 09:35 schrieb Peter Lieven:
Some code in the block layer makes potentially huge allocations. Failure
is not completely unexpected there, so avoid aborting qemu and handle
out-of-memory situations gracefully.
This
Am 22.08.2014 um 10:42 schrieb Kevin Wolf:
Am 22.08.2014 um 09:40 hat Peter Lieven geschrieben:
Am 22.08.2014 um 09:35 schrieb Peter Lieven:
Some code in the block layer makes potentially huge allocations. Failure
is not completely unexpected there, so avoid aborting qemu and handle
