commit/stream: Reset delay_ns
PATCH 1/1 commit/stream: Reset delay_ns
Streaming and the commit block job only want to apply throttling when they actually copied data instead of skipping it, so they made the calculation of delay_ns conditional. However, delay_ns isn't reset when skipping some sectors, so instead of not waiting, the old delay is applied again.
Properly reset delay_ns where needed.
--- block/commit.c | 2 ++ block/stream.c | 2 ++ 2 files changed, 4 insertions(+)
block/commit.c +2 -0
@@ -202,6 +202,8 @@ static void coroutine_fn commit_run(void *opaque)if (copy && s->common.speed) { delay_ns =ratelimit_calculate_delay (&s->limit, n); + }else { + delay_ns =0 ; } }
block/stream.c +2 -0
@@ -188,6 +188,8 @@ static void coroutine_fn stream_run(void *opaque) s->common.offset += n;if (copy && s->common.speed) { delay_ns =ratelimit_calculate_delay (&s->limit, n); + }else { + delay_ns =0 ; } }
Signature · 1 line
2.13.6
Quoted 6 lines · Kevin Wolf
Streaming and the commit block job only want to apply throttling when they actually copied data instead of skipping it, so they made the calculation of
delay_nsconditional. However,delay_nsisn't reset when skipping some sectors, so instead of not waiting, the old delay is applied again.
Quoted 8 lines
Properly reset
delay_nswhere needed.Signed-off-by Kevin Wolf <[email protected]>--- block/commit.c | 2 ++ block/stream.c | 2 ++ 2 files changed, 4 insertions(+)
Signature · 3 lines
Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org
Quoted 6 lines · Kevin Wolf
Streaming and the commit block job only want to apply throttling when they actually copied data instead of skipping it, so they made the calculation of
delay_nsconditional. However,delay_nsisn't reset when skipping some sectors, so instead of not waiting, the old delay is applied again.
Quoted 7 lines
Properly reset
delay_nswhere needed.Signed-off-by Kevin Wolf <[email protected]>--- block/commit.c | 2 ++ block/stream.c | 2 ++ 2 files changed, 4 insertions(+)