| commit | b4a3c64b16856a018869bfd4a9ed3b2a74554541 | |
| author | Felipe Franciosi <felipe@nutanix.com> | |
| Wed, 24 May 2017 16:10:03 +0000 (24 17:10 +0100) | ||
| committer | Juan Quintela <quintela@redhat.com> | |
| Wed, 31 May 2017 07:39:20 +0000 (31 09:39 +0200) | ||
| tree | 2b22a072b2b6d5a5be44963669087d2e4a809032 | treesnapshot (tar.gz zip) |
| parent | d2a4d85a8a786e1e59fc631c34dd474752810463 | commitdiff |
migration: use dirty_rate_high_cnt more aggressively
The commit message from 070afca25 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: Felipe Franciosi <felipe@nutanix.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
The commit message from 070afca25 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: Felipe Franciosi <felipe@nutanix.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
| migration/ram.c | diffblobblamehistory |