Benoît Canet benoit.ca...@irqsave.net writes:
The Wednesday 27 Aug 2014 à 16:58:12 (+0200), Anshul Makkar wrote :
Hi,
I am writing a block IO latency tracker.
As obvious, I am calculating the latency by tracking the interval between
start of IO and end of IO.
(firing my latency tracker
On Wed, Aug 27, 2014 at 04:58:12PM +0200, Anshul Makkar wrote:
I am writing a block IO latency tracker.
As obvious, I am calculating the latency by tracking the interval between
start of IO and end of IO.
(firing my latency tracker from function BlockDriverAIOCB *raw_aio_submit()
The Thursday 28 Aug 2014 à 13:36:35 (+0100), Stefan Hajnoczi wrote :
On Wed, Aug 27, 2014 at 04:58:12PM +0200, Anshul Makkar wrote:
I am writing a block IO latency tracker.
As obvious, I am calculating the latency by tracking the interval between
start of IO and end of IO.
(firing my
Benoît Canet benoit.ca...@irqsave.net writes:
The Thursday 28 Aug 2014 à 13:36:35 (+0100), Stefan Hajnoczi wrote :
On Wed, Aug 27, 2014 at 04:58:12PM +0200, Anshul Makkar wrote:
I am writing a block IO latency tracker.
As obvious, I am calculating the latency by tracking the interval
Hi,
I am writing a block IO latency tracker.
As obvious, I am calculating the latency by tracking the interval between
start of IO and end of IO.
(firing my latency tracker from function BlockDriverAIOCB *raw_aio_submit()
raw-posix.c when job is submitted).
The latency data per QEMU process
The Wednesday 27 Aug 2014 à 16:58:12 (+0200), Anshul Makkar wrote :
Hi,
I am writing a block IO latency tracker.
As obvious, I am calculating the latency by tracking the interval between
start of IO and end of IO.
(firing my latency tracker from function BlockDriverAIOCB
