All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block/mirror: Sleep periodically during bitmap scanning
Date: Wed, 13 May 2015 11:30:29 +0200	[thread overview]
Message-ID: <555319B5.2040704@redhat.com> (raw)
In-Reply-To: <1431486673-19280-1-git-send-email-famz@redhat.com>



On 13/05/2015 05:11, Fam Zheng wrote:
> Before, we only yield after initializing dirty bitmap, where the QMP
> command would return. That may take very long, and guest IO will be
> blocked.
> 
> Add sleep points like the later mirror iterations.

You were also planning to let bdrv_co_is_allocated/get_block_status
return a larger p_num than nb_sectors---which maybe could make
nb_sectors obsolete completely, I don't know.  But this is already an
improvement.

Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

Thanks,

Paolo

> 
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
>  block/mirror.c | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/block/mirror.c b/block/mirror.c
> index 1a1d997..baed225 100644
> --- a/block/mirror.c
> +++ b/block/mirror.c
> @@ -467,11 +467,23 @@ static void coroutine_fn mirror_run(void *opaque)
>      sectors_per_chunk = s->granularity >> BDRV_SECTOR_BITS;
>      mirror_free_init(s);
>  
> +    last_pause_ns = qemu_clock_get_ns(QEMU_CLOCK_REALTIME);
>      if (!s->is_none_mode) {
>          /* First part, loop on the sectors and initialize the dirty bitmap.  */
>          BlockDriverState *base = s->base;
>          for (sector_num = 0; sector_num < end; ) {
>              int64_t next = (sector_num | (sectors_per_chunk - 1)) + 1;
> +            int64_t now = qemu_clock_get_ns(QEMU_CLOCK_REALTIME);
> +
> +            if (now - last_pause_ns > SLICE_TIME) {
> +                last_pause_ns = now;
> +                block_job_sleep_ns(&s->common, QEMU_CLOCK_REALTIME, 0);
> +            }
> +
> +            if (block_job_is_cancelled(&s->common)) {
> +                goto immediate_exit;
> +            }
> +
>              ret = bdrv_is_allocated_above(bs, base,
>                                            sector_num, next - sector_num, &n);
>  
> @@ -490,7 +502,6 @@ static void coroutine_fn mirror_run(void *opaque)
>      }
>  
>      bdrv_dirty_iter_init(s->dirty_bitmap, &s->hbi);
> -    last_pause_ns = qemu_clock_get_ns(QEMU_CLOCK_REALTIME);
>      for (;;) {
>          uint64_t delay_ns = 0;
>          int64_t cnt;
> 

  parent reply	other threads:[~2015-05-13  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  3:11 [Qemu-devel] [PATCH] block/mirror: Sleep periodically during bitmap scanning Fam Zheng
2015-05-13  5:17 ` Wen Congyang
2015-05-13  6:40   ` Fam Zheng
2015-06-05  2:50     ` Wen Congyang
2015-05-13  7:11 ` Wen Congyang
2015-05-13  9:30 ` Paolo Bonzini [this message]
2015-05-19 10:46 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-06-15 16:35 ` Stefan Hajnoczi
2015-06-16  4:06 ` [Qemu-devel] " Jeff Cody
2015-06-29  8:56   ` Alexandre DERUMIER

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=555319B5.2040704@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.