Large disk images need large L2 caches in order to maximize their
I/O performance. However setting a correct size for the cache is not
necessarily easy since apart from the image size, it also depends
on other factors like its usage patterns or whether it's part of a
backing chain.
In order to be
On Tue, Apr 21, 2015 at 03:53:11PM +0200, Kashyap Chamarthy wrote:
[. . .]
And, invoking `drive-backup` *without* pre-creating the target image
(i.e. 'incremental.o.img'):
{ 'execute': 'drive-backup',
'arguments': {
'device': 'ide0-0-0',
Small typo (in this email, not
On 21/04/2015 03:25, Wen Congyang wrote:
Please do not introduce name+colo block drivers. This approach is
invasive and makes block replication specific to only a few block
drivers, e.g. NBD or qcow2.
NBD is used to connect to secondary qemu, so it must be used. But the primary
qemu
On Fri, Apr 17, 2015 at 09:01:10PM -0400, John Snow wrote:
I am not prepared to send a v3 on this, primarily because I am still
waffling on whether or not to do the code motion patch that is present in
patch #8 of v2 of this series.
However, for the purposes of testing, reviewers may find it
On Tue, Apr 21, 2015 at 03:53:11PM +0200, Kashyap Chamarthy wrote:
[. . .]
And, invoking `drive-backup` *without* pre-creating the target image
(i.e. 'incremental.o.img'):
{ 'execute': 'drive-backup',
'arguments': {
'device': 'ide0-0-0',
'bitmap': 'bitmap0',
