] block: add watermark event
On Tue, Aug 05, 2014 at 10:47:57AM +0200, Kevin Wolf wrote:
Am 01.08.2014 um 13:39 hat Stefan Hajnoczi geschrieben:
On Tue, Jul 08, 2014 at 04:49:24PM +0200, Francesco Romani wrote:
@@ -5813,3 +5815,57 @@ void bdrv_flush_io_queue(BlockDriverState *bs
On 08/08/2014 02:01 AM, Francesco Romani wrote:
So let the block-set-watermark caller pass an absolute sector number
instead. It keeps things simple for both QEMU and thin provisioning
manager.
No sector numbers in external interfaces, please. These units of 512
bytes are completely
Am 01.08.2014 um 13:39 hat Stefan Hajnoczi geschrieben:
On Tue, Jul 08, 2014 at 04:49:24PM +0200, Francesco Romani wrote:
@@ -5813,3 +5815,57 @@ void bdrv_flush_io_queue(BlockDriverState *bs)
bdrv_flush_io_queue(bs-file);
}
}
+
+static bool
On Tue, Aug 05, 2014 at 10:47:57AM +0200, Kevin Wolf wrote:
Am 01.08.2014 um 13:39 hat Stefan Hajnoczi geschrieben:
On Tue, Jul 08, 2014 at 04:49:24PM +0200, Francesco Romani wrote:
@@ -5813,3 +5815,57 @@ void bdrv_flush_io_queue(BlockDriverState *bs)
On Tue, Jul 08, 2014 at 04:49:24PM +0200, Francesco Romani wrote:
@@ -5813,3 +5815,57 @@ void bdrv_flush_io_queue(BlockDriverState *bs)
bdrv_flush_io_queue(bs-file);
}
}
+
+static bool watermark_exceeded(BlockDriverState *bs,
+ int64_t
Managing applications, like oVirt (http://www.ovirt.org), make extensive
use of thin-provisioned disk images.
In order to let the guest run flawlessly and be not unnecessarily
paused, oVirt sets a watermark based on the percentage occupation of the
device against the advertised size, and
On 07/08/2014 08:49 AM, Francesco Romani wrote:
Managing applications, like oVirt (http://www.ovirt.org), make extensive
use of thin-provisioned disk images.
In order to let the guest run flawlessly and be not unnecessarily
paused, oVirt sets a watermark based on the percentage occupation of
