8e3f651d6b76a33f580ea9811b64168610d3ebd4 - chromium/src

commit	8e3f651d6b76a33f580ea9811b64168610d3ebd4	[log] [tgz]
author	ericrk <ericrk@chromium.org>	Wed Mar 29 18:22:31 2017
committer	Commit bot <commit-bot@chromium.org>	Wed Mar 29 18:22:31 2017
tree	a07f999be6d239ede74587f4d630cc58836dd878
parent	e29fdab2cf168e2a4de8709aea221cf5ef65cf5f [diff]

Split image decode cache limits into "working set" vs "cache" limits

Working set limit impacts how many images we will keep locked before
going to at-raster. This is different from the cache limit, which
impacts how many images we will keep around once unlocked.

SW Image Decode Cache doesn't use cache limit, just working set, as
it keeps all not-in-use images unlocked and effectively "free".

BUG=706470
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2780843002
Cr-Commit-Position: refs/heads/master@{#460461}

cc/raster/raster_source_unittest.cc[diff]
cc/test/fake_tile_manager.cc[diff]
cc/tiles/gpu_image_decode_cache.cc[diff]
cc/tiles/gpu_image_decode_cache.h[diff]
cc/tiles/gpu_image_decode_cache_unittest.cc[diff]
cc/trees/layer_tree_host_impl.cc[diff]
cc/trees/layer_tree_host_unittest.cc[diff]
cc/trees/layer_tree_settings.h[diff]
content/renderer/gpu/render_widget_compositor.cc[diff]

9 files changed