On Tue, Mar 21, 2017 at 09:22:52AM +0100, Juan Quintela wrote:
>Chao Fan wrote:
>> The number of dirty pages outputed in 'pages' in the command
>> 'info migrate', so add page-size to calculate the number of dirty
>> pages in bytes.
>>
>>
The number of dirty pages outputed in 'pages' in the command
'info migrate', so add page-size to calculate the number of dirty
pages in bytes.
Signed-off-by: Chao Fan
Signed-off-by: Li Zhijian
---
v2: fix the grammar in qapi-schema.json [Eric Blake]
---
hmp.c
The number of dirty pages outputed in 'pages' in the command
'info migrate', so add page-size to calculate the number of dirty
pages in bytes.
Signed-off-by: Chao Fan
Signed-off-by: Li Zhijian
---
hmp.c | 3 +++
include/migration/migration.h | 1 +
m
On Tue, Mar 14, 2017 at 12:37:30PM +, Daniel P. Berrange wrote:
>On Tue, Mar 14, 2017 at 01:29:43PM +0100, Juan Quintela wrote:
>> Chao Fan wrote:
>> > In hmp, dirty-bytes-rate is more friendly than dirty-pages-rate.
>> > It's also better for other too
On Tue, Mar 14, 2017 at 09:54:34AM -0500, Eric Blake wrote:
>On 03/14/2017 05:27 AM, Chao Fan wrote:
>> In hmp, dirty-bytes-rate is more friendly than dirty-pages-rate.
>> It's also better for other tools to determine the cpu throttle
>> value in different architecture.
On Tue, Mar 14, 2017 at 01:29:43PM +0100, Juan Quintela wrote:
>Chao Fan wrote:
>> In hmp, dirty-bytes-rate is more friendly than dirty-pages-rate.
>> It's also better for other tools to determine the cpu throttle
>> value in different architecture.
>>
>> Sig
On Tue, Mar 14, 2017 at 12:37:30PM +, Daniel P. Berrange wrote:
>On Tue, Mar 14, 2017 at 01:29:43PM +0100, Juan Quintela wrote:
>> Chao Fan wrote:
>> > In hmp, dirty-bytes-rate is more friendly than dirty-pages-rate.
>> > It's also better for other too
Daniel and Juan,
Sorry for this patch, cause I did not see your reply.
So Nack this patch.
And thank you very much.
Thanks,
Chao Fan
On Tue, Mar 14, 2017 at 08:38:41PM +0800, Chao Fan wrote:
>Because 'dirty-bytes-rate' is in 'bytes/s', so it's better for other
Because 'dirty-bytes-rate' is in 'bytes/s', so it's better for other
tools to determine the cpu throttle value in different architecture.
Signed-off-by: Chao Fan
Signed-off-by: Li Zhijian
---
hmp.c | 6 +-
migration/migration.c | 1 +
qapi-sche
On Tue, Mar 14, 2017 at 10:45:16AM +, Daniel P. Berrange wrote:
>On Tue, Mar 14, 2017 at 06:27:47PM +0800, Chao Fan wrote:
>> In hmp, dirty-bytes-rate is more friendly than dirty-pages-rate.
>> It's also better for other tools to determine the cpu throttle
>> value
In hmp, dirty-bytes-rate is more friendly than dirty-pages-rate.
It's also better for other tools to determine the cpu throttle
value in different architecture.
Signed-off-by: Chao Fan
Signed-off-by: Li Zhijian
---
hmp.c | 6 +++---
migration/migration.c | 2 +-
On Tue, Mar 14, 2017 at 09:38:46AM +0100, Juan Quintela wrote:
>Chao Fan wrote:
>> In function cpu_physical_memory_sync_dirty_bitmap, file
>> include/exec/ram_addr.h:
>>
>> if (src[idx][offset]) {
>> unsigned long bits = atomic_xchg(&src[idx][offset
0b0011,
the new_dirty will be 0b1100, and this function will return 2 but not
4 which is expected.
the dirty pages in dirty_memory[DIRTY_MEMORY_MIGRATION] are all new,
so these should be calculated also.
Signed-off-by: Chao Fan
Signed-off-by: Li Zhijian
---
v2: Remove the parameter '
On Tue, Mar 14, 2017 at 09:41:30AM +0800, Li Zhijian wrote:
>
>
>On 03/14/2017 09:26 AM, Chao Fan wrote:
>> In function cpu_physical_memory_sync_dirty_bitmap, file
>> include/exec/ram_addr.h:
>>
>> if (src[idx][offset]) {
>> unsigned long
0b0011,
the new_dirty will be 0b1100, and this function will return 2 but not
4 which is expected.
the dirty pages in dirty_memory[DIRTY_MEMORY_MIGRATION] are all new,
so these should be calculated also.
Signed-off-by: Chao Fan
Signed-off-by: Li Zhijian
---
include/exec/ram_addr.h | 5 -
On Wed, Mar 08, 2017 at 01:45:59PM +, Daniel P. Berrange wrote:
>On Wed, Mar 08, 2017 at 04:28:19PM +0800, Chao Fan wrote:
>> Auto-converge aims to accelerate migration by slowing down the
>> generation of dirty pages. But user doesn't know how to determine the
>>
Auto-converge aims to accelerate migration by slowing down the
generation of dirty pages. But user doesn't know how to determine the
throttle value, so, a new item "inst-dirty-pages-rate" in "info migrate"
would be helpful for user's determination.
Signed-off-by: C
Auto-converge aims to accelerate migration by slowing down the
generation of dirty pages. But user doesn't know how to determine the
throttle value, so, a new item "inst-dirty-pages-rate" in "info migrate"
would be helpful for user's determination.
Signe
On Fri, Jan 27, 2017 at 12:07:27PM +, Dr. David Alan Gilbert wrote:
>* Chao Fan (fanc.f...@cn.fujitsu.com) wrote:
>> Hi all,
>>
>> This is a test for this RFC patch.
>>
>> Start vm as following:
>> cmdline="./x86_64-softmmu/qemu-system-x86_
is 70.80.90 (total time from 21 to
30), 6s with the cpu throttle percentage is 99 (total time from 30 to
completed). So I think the influence to the guest performance after my
patch is fewer than the upstream version.
Any comments will be welcome.
[*]http://accc.riken.jp/en/supercom/himenobmt
Hi all,
There is something to explain in this RFC PATCH.
On Thu, Dec 29, 2016 at 05:16:19PM +0800, Chao Fan wrote:
>This RFC PATCH is my demo about the new feature, here is my POC mail:
>https://lists.gnu.org/archive/html/qemu-devel/2016-12/msg00646.html
>
>When migration_bitmap_s
-by: Chao Fan
---
include/qemu/bitmap.h | 17 +
migration/ram.c | 49 +
2 files changed, 66 insertions(+)
diff --git a/include/qemu/bitmap.h b/include/qemu/bitmap.h
index 63ea2d0..dc99f9b 100644
--- a/include/qemu/bitmap.h
ping...
Thanks,
Chao Fan
On Tue, Dec 06, 2016 at 04:52:11PM +0800, Chao Fan wrote:
>Hi all,
>
>Here is an issue in auto-converge feature of migration.
>
>When migrating a guest which consumes too much CPU & memory, dirty
>pages amount will increase significantly, so do
this feature is needed.
If anyone has good ideas, please tell me.
Thanks,
Chao Fan
, cpu_throttle_increment will be useless,
as the the percentage of CPU frequency will be 1, the least value.
Signed-off-by: Chao Fan
---
v2: fix the wrong variable type
---
migration/migration.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/migration/migration.c b/migration
, cpu_throttle_increment will be useless,
as the the percentage of CPU frequency will be 1, the least value.
Signed-off-by: Chao Fan
---
migration/migration.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/migration/migration.c b/migration/migration.c
index f498ab8..a6d0334 100644
26 matches
Mail list logo
