chromium/src
0
Fork 0
Code Activity

docs: minor fix in memory-infra compositor doc

Browse Source 
Looks like Gitiles mardown renderer doesn't support tables yet.
I filed https://bugs.chromium.org/p/gerrit/issues/detail?id=5923
to request the feature. In the meantime, turning the cc's table
into a code section, as currently gets renderer as unreadable
text.

TBR=ericrk@chromium.org

Review-Url: https://codereview.chromium.org/2791973002
Cr-Commit-Position: refs/heads/master@{#461396}
This commit is contained in:
primiano
2017-04-03 02:45:34 -07:00
committed by Commit bot
parent 6be2959e1a
commit b48bcd6aec
1 changed files with 2 additions and 0 deletions

2
docs/memory-infra/probe-cc.md

@ -43,12 +43,14 @@ like tile_memory, in that they are shared with cc/resource_memory.
Note that depending on the path being used, CC memory may be either shared
memory or GPU memory:
```
Path | Tile Memory Type | Staging Memory Type
-------------|-------------------------------------------
Bitmap | Shared Memory | N/A
One Copy | GPU Memory | Shared Memory
Zero Copy | GPU or Shared Memory | N/A
GPU | GPU Memory | N/A
```
Note that these values can be determined from a memory-infra dump. For a given
resource, hover over the small green arrow next to it's "size". This will show