[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH V6 10/10] migration: postcopy_blocktime document
From: |
Dr. David Alan Gilbert |
Subject: |
Re: [Qemu-devel] [PATCH V6 10/10] migration: postcopy_blocktime documentation |
Date: |
Thu, 1 Jun 2017 12:37:40 +0100 |
User-agent: |
Mutt/1.8.2 (2017-04-18) |
* Alexey Perevalov (address@hidden) wrote:
> Signed-off-by: Alexey Perevalov <address@hidden>
> ---
> docs/migration.txt | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/docs/migration.txt b/docs/migration.txt
> index 1b940a8..2207c6d 100644
> --- a/docs/migration.txt
> +++ b/docs/migration.txt
> @@ -402,6 +402,16 @@ will now cause the transition from precopy to postcopy.
> It can be issued immediately after migration is started or any
> time later on. Issuing it after the end of a migration is harmless.
>
> +Blocktime is a postcopy live migration metric, intended to show
> +how long the source vCPU was in state of interruptable sleep due to
> pagefault.
^^^^^^
I think it's just 'how long the vCPU' - I don't think 'source' adds
anything.
> +This value is calculated on destination side.
> +To enable postcopy blocktime calculation, enter following command on
> destination
> +monitor:
> +
> +migrate_set_capability postcopy-blocktime on
> +
> +Postcopy blocktime can be retrieved by query-migrate qmp command.
> +
I think other than that it's OK.
Reviewed-by: Dr. David Alan Gilbert <address@hidden>
> Note: During the postcopy phase, the bandwidth limits set using
> migrate_set_speed is ignored (to avoid delaying requested pages that
> the destination is waiting for).
> --
> 1.8.3.1
>
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Qemu-devel] [PATCH V6 10/10] migration: postcopy_blocktime documentation,
Dr. David Alan Gilbert <=