On 23.07.2014 10:10, Kevin Wolf wrote:
Am 22.07.2014 um 22:06 hat Max Reitz geschrieben:
On 21.07.2014 17:52, Eric Blake wrote:
On 07/19/2014 02:35 PM, Max Reitz wrote:
Many qemu-img subcommands only read the source file(s) once. For these
use cases, a full write-back cache is unnecessary and
Am 22.07.2014 um 22:06 hat Max Reitz geschrieben:
> On 21.07.2014 17:52, Eric Blake wrote:
> >On 07/19/2014 02:35 PM, Max Reitz wrote:
> >>Many qemu-img subcommands only read the source file(s) once. For these
> >>use cases, a full write-back cache is unnecessary and mainly clutters
> >>host cache
On 21.07.2014 17:52, Eric Blake wrote:
On 07/19/2014 02:35 PM, Max Reitz wrote:
Many qemu-img subcommands only read the source file(s) once. For these
use cases, a full write-back cache is unnecessary and mainly clutters
host cache memory. Though this is generally no concern as cache memory
is f
On 07/19/2014 02:35 PM, Max Reitz wrote:
> Many qemu-img subcommands only read the source file(s) once. For these
> use cases, a full write-back cache is unnecessary and mainly clutters
> host cache memory. Though this is generally no concern as cache memory
> is freely available and can be scaled
Many qemu-img subcommands only read the source file(s) once. For these
use cases, a full write-back cache is unnecessary and mainly clutters
host cache memory. Though this is generally no concern as cache memory
is freely available and can be scaled by the host OS, it may become a
concern with thin
