Commit b4a3c64b authored by Felipe Franciosi's avatar Felipe Franciosi Committed by Juan Quintela
Browse files

migration: use dirty_rate_high_cnt more aggressively 



The commit message from 070afca2 suggests that dirty_rate_high_cnt
should be used more aggressively to start throttling after two
iterations instead of four. The code, however, only changes the auto
convergence behaviour to throttle after three iterations. This makes the
behaviour more aggressive by kicking off throttling after two iterations
as originally intended.

Signed-off-by: default avatarFelipe Franciosi <felipe@nutanix.com>
Reviewed-by: default avatarPeter Xu <peterx@redhat.com>
Reviewed-by: default avatarJuan Quintela <quintela@redhat.com>
Signed-off-by: default avatarJuan Quintela <quintela@redhat.com>
parent d2a4d85a

migration/ram.c

+1 −1
Original line number Diff line number Diff line
@@ -708,7 +708,7 @@ static void migration_bitmap_sync(RAMState *rs) 


            if ((rs->num_dirty_pages_period * TARGET_PAGE_SIZE >

                   (bytes_xfer_now - rs->bytes_xfer_prev) / 2) &&

                (rs->dirty_rate_high_cnt++ >= 2)) {

                (++rs->dirty_rate_high_cnt >= 2)) {

                    trace_migration_throttle();

                    rs->dirty_rate_high_cnt = 0;

                    mig_throttle_guest_down();