All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Qiang <liq3ea@gmail.com>
To: Chuan Zheng <zhengchuan@huawei.com>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	zhanghailiang <zhang.zhanghailiang@huawei.com>,
	Juan Quintela <quintela@redhat.com>,
	yuxiating@huawei.com,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	xiexiangyou@huawei.com, Qemu Developers <qemu-devel@nongnu.org>,
	AlexChen <alex.chen@huawei.com>,
	jinyan12@huawei.com
Subject: Re: [PATCH v8 10/12] migration/dirtyrate: Implement calculate_dirtyrate() function
Date: Mon, 14 Sep 2020 23:45:04 +0800	[thread overview]
Message-ID: <CAKXe6S+XO5tEMxVBwdX9r4tyn6jaPUkbR_UM4tPUvJXbwcURTA@mail.gmail.com> (raw)
In-Reply-To: <1600074185-91624-11-git-send-email-zhengchuan@huawei.com>

Chuan Zheng <zhengchuan@huawei.com> 于2020年9月14日周一 下午4:52写道:
>
> Implement calculate_dirtyrate() function.
>
> Signed-off-by: Chuan Zheng <zhengchuan@huawei.com>
> Signed-off-by: YanYing Zhuang <ann.zhuangyanying@huawei.com>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
>  migration/dirtyrate.c | 45 +++++++++++++++++++++++++++++++++++++++++++--
>  1 file changed, 43 insertions(+), 2 deletions(-)
>
> diff --git a/migration/dirtyrate.c b/migration/dirtyrate.c
> index 6add846..cc31bd1 100644
> --- a/migration/dirtyrate.c
> +++ b/migration/dirtyrate.c
> @@ -162,6 +162,21 @@ static void get_ramblock_dirty_info(RAMBlock *block,
>      strcpy(info->idstr, qemu_ram_get_idstr(block));
>  }
>
> +static void free_ramblock_dirty_info(struct RamblockDirtyInfo *infos, int count)
> +{
> +    int i;
> +
> +    if (!infos) {
> +        return;
> +    }
> +
> +    for (i = 0; i < count; i++) {
> +        g_free(infos[i].sample_page_vfn);
> +        g_free(infos[i].hash_result);
> +    }
> +    g_free(infos);
> +}
> +
>  static bool skip_sample_ramblock(RAMBlock *block)
>  {
>      /*
> @@ -289,8 +304,34 @@ static int compare_page_hash_info(struct RamblockDirtyInfo *info,
>
>  static void calculate_dirtyrate(struct DirtyRateConfig config)
>  {
> -    /* todo */
> -    return;
> +    struct RamblockDirtyInfo *block_dinfo = NULL;
> +    int block_index = 0;
> +    int64_t msec = 0;
> +    int64_t initial_time;
> +
> +    rcu_register_thread();
> +    reset_dirtyrate_stat();
> +    rcu_read_lock();
> +    initial_time = qemu_clock_get_ms(QEMU_CLOCK_REALTIME);
> +    if (!record_ramblock_hash_info(&block_dinfo, config, &block_index)) {
> +        goto out;
> +    }
> +    rcu_read_unlock();
> +
> +    msec = config.sample_period_seconds * 1000;
> +    msec = set_sample_page_period(msec, initial_time);
> +
> +    rcu_read_lock();
> +    if (compare_page_hash_info(block_dinfo, block_index) < 0) {
> +        goto out;

It seems the value of 'DirtyRateStat.dirty_rate'  is 0 if this error occurs ?

Maybe we should set the DirtyRateStat.dirty_rate to -1 in
reset_dirtyrate_stat function.
As you say:

+#          If this field return '-1', it means querying is not
+#          start or not complete.

The '0' may confuse the people there is no dirty page.

Thanks,
Li Qiang

> +    }
> +
> +    update_dirtyrate(msec);
> +
> +out:
> +    rcu_read_unlock();
> +    free_ramblock_dirty_info(block_dinfo, block_index);
> +    rcu_unregister_thread();
>  }
>
>  void *get_dirtyrate_thread(void *arg)
> --
> 1.8.3.1
>


  parent reply	other threads:[~2020-09-14 17:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-14  9:02 [PATCH v8 00/12] *** A Method for evaluating dirty page rate *** Chuan Zheng
2020-09-14  9:02 ` [PATCH v8 01/12] migration/dirtyrate: setup up query-dirtyrate framwork Chuan Zheng
2020-09-14  9:02 ` [PATCH v8 02/12] migration/dirtyrate: add DirtyRateStatus to denote calculation status Chuan Zheng
2020-09-14  9:02 ` [PATCH v8 03/12] migration/dirtyrate: Add RamblockDirtyInfo to store sampled page info Chuan Zheng
2020-09-14  9:02 ` [PATCH v8 04/12] migration/dirtyrate: Add dirtyrate statistics series functions Chuan Zheng
2020-09-14  9:02 ` [PATCH v8 05/12] migration/dirtyrate: move RAMBLOCK_FOREACH_MIGRATABLE into ram.h Chuan Zheng
2020-09-14  9:02 ` [PATCH v8 06/12] migration/dirtyrate: Record hash results for each sampled page Chuan Zheng
2020-09-14 14:59   ` Li Qiang
2020-09-15  1:28     ` Zheng Chuan
2020-09-14  9:03 ` [PATCH v8 07/12] migration/dirtyrate: Compare page hash results for recorded " Chuan Zheng
2020-09-14 15:08   ` Li Qiang
2020-09-14  9:03 ` [PATCH v8 08/12] migration/dirtyrate: skip sampling ramblock with size below MIN_RAMBLOCK_SIZE Chuan Zheng
2020-09-14  9:03 ` [PATCH v8 09/12] migration/dirtyrate: Implement set_sample_page_period() and is_sample_period_valid() Chuan Zheng
2020-09-14  9:03 ` [PATCH v8 10/12] migration/dirtyrate: Implement calculate_dirtyrate() function Chuan Zheng
2020-09-14 15:08   ` Li Qiang
2020-09-14 15:45   ` Li Qiang [this message]
2020-09-14  9:03 ` [PATCH v8 11/12] migration/dirtyrate: Implement qmp_cal_dirty_rate()/qmp_get_dirty_rate() function Chuan Zheng
2020-09-14  9:03 ` [PATCH v8 12/12] migration/dirtyrate: Add trace_calls to make it easier to debug Chuan Zheng

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=CAKXe6S+XO5tEMxVBwdX9r4tyn6jaPUkbR_UM4tPUvJXbwcURTA@mail.gmail.com \
    --to=liq3ea@gmail.com \
    --cc=alex.chen@huawei.com \
    --cc=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=jinyan12@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=xiexiangyou@huawei.com \
    --cc=yuxiating@huawei.com \
    --cc=zhang.zhanghailiang@huawei.com \
    --cc=zhengchuan@huawei.com \
    /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.