[Top][All Lists]

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

Re: [Qemu-block] [RFC] finegrained disk driver options control

From: Daniel P. Berrange
Subject: Re: [Qemu-block] [RFC] finegrained disk driver options control
Date: Sat, 18 Mar 2017 09:54:16 +0000
User-agent: Mutt/1.7.1 (2016-10-04)

On Thu, Mar 16, 2017 at 05:26:26PM +0100, Kevin Wolf wrote:
> Am 16.03.2017 um 16:52 hat Daniel P. Berrange geschrieben:
> If you don't care about that at all, the optimal configuration in terms
> of performance is to give qemu a cache large enough that the metadata of
> the whole image fits in it. When setting cache-clean-interval, this
> could actually be reasonable even for large images because the memory
> wouldn't be used forever but just as long as the guest is submitting the
> problematic I/O patterns - but it still means that temporarily qemu
> could really use all of this memory.

Is there some easy algorithm that libvirt can use to determine the size
of the L2 tables, and thus report what the maximum useful cache size
would be ?

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

reply via email to

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