On Fri, Feb 13, 2015 at 16:24:33 +0100, Michal Privoznik wrote:
Instead of unlocking and locking the domain object every 50ms
lets just wait on blockJob condition and run the loop body if and
BLOCK_JOB even occurred.
Signed-off-by: Michal Privoznik <mprivozn(a)redhat.com>
---
This one, well, I still left the only monitor call as I'm not
very familiar with this code so I don't know if it can be more
optimized. But hey, the 50ms sleep is gone!
It seems the monitor call just checks for block job status, which seems
redundant since it should already be present in disk->mirrorState thanks
to the block job event handler.
Jirka