| commit | 198f1cd771751f113641219e05d6ecf9f22b2bc2 | |
| author | vmpstr <vmpstr@chromium.org> | |
| Fri, 13 Feb 2015 01:52:02 +0000 (12 17:52 -0800) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 13 Feb 2015 01:52:46 +0000 (13 01:52 +0000) | ||
| tree | 0c00e256f2c78064a98854f6ec043e56a01eeaf1 | treesnapshot (tar.gz zip) |
| parent | 62fc8d9d8e96b06feffea2de35c56edd0d2cee3c | commitdiff |
cc: Switch eviction iterators to consider combined priority.
When processing eviction, we should be considering combined priority as
the determining factor in which tile goes next. The reason for this is
that even in situations where a tree priority would imply that a
particular tile is of low priority, we need to be mindful of where it
appears on the other tree as well.
This is captured in the fact that tile manager is using combined
priority to schedule tiles, but the eviction iterator itself does not
reflect this.
BUG=457977
R=vmiura, danakj
Review URL: https://codereview.chromium.org/924613002
Cr-Commit-Position: refs/heads/master@{#316124}
When processing eviction, we should be considering combined priority as
the determining factor in which tile goes next. The reason for this is
that even in situations where a tree priority would imply that a
particular tile is of low priority, we need to be mindful of where it
appears on the other tree as well.
This is captured in the fact that tile manager is using combined
priority to schedule tiles, but the eviction iterator itself does not
reflect this.
BUG=457977
R=vmiura, danakj
Review URL: https://codereview.chromium.org/924613002
Cr-Commit-Position: refs/heads/master@{#316124}