diff options
author | ccameron@chromium.org <ccameron@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-12-13 01:16:48 +0000 |
---|---|---|
committer | ccameron@chromium.org <ccameron@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-12-13 01:16:48 +0000 |
commit | 68e81a4a69fcfd394e4e5e86e59c9b5db17c4370 (patch) | |
tree | aebf1a486dadc15ef9640079c550b9ecc5f688ed /sync/internal_api/sync_manager_impl.cc | |
parent | 04b5defa857ffd767aa5827e9dc6b3d847c328de (diff) | |
download | chromium_src-68e81a4a69fcfd394e4e5e86e59c9b5db17c4370.zip chromium_src-68e81a4a69fcfd394e4e5e86e59c9b5db17c4370.tar.gz chromium_src-68e81a4a69fcfd394e4e5e86e59c9b5db17c4370.tar.bz2 |
Track managed memory usage in the command buffer.
This adds infrastructure necessary to support tracking which allocations
are through the compositor (or, more generally, any managed allocator that
the GPU memory manager affect) and allocations that are not (e.g, WebGL).
This is part of a scheme which will add a GL extension where the compositor
can mark a texture as being managed by a call to glTexParameteri.
This information had previously been tracked by an IPC being sent by the
compositor to the GPU process informing it of the managed memory usage (in
addition to the usage required for all visible content, etc). This had
the two problems. First, the information was not accurate -- the data sent
about managed allocations to the GPU memory manager would always lag the
actual allocations. Second, these IPCs were expensive and needed to be
throttled. The more we throttle the IPCs, the less accurate the information
would become, making the GPU memory manager's behavior less precise and
predictable.
BUG=164947
Review URL: https://chromiumcodereview.appspot.com/11516014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172754 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sync/internal_api/sync_manager_impl.cc')
0 files changed, 0 insertions, 0 deletions