commit | ca5a89c7acf6d4fa475551ee0d8a143585873707 | [log] [tgz] |
---|---|---|
author | Kuo-Hsin Yang <[email protected]> | Tue Oct 13 05:38:41 2020 |
committer | Commit Bot <[email protected]> | Tue Oct 13 05:38:41 2020 |
tree | 220ac4d77f3e886da0fa59aa27c3c473d8cf931e | |
parent | 90345a0c8e6f8174d88a733aa67c6cc2222d6736 [diff] |
[base] Add function GetGraphicsMemoryInfo Before this patch, GetSystemMemoryInfo() reads both /proc/meminfo and /run/debugfs_gpu/i915_gem_objects (for x86 CPU family). Reading /run/debugfs_gpu/i915_gem_objects could take more than 500 ms under memory pressure on Intel platform with kernel 5.4, while reading /proc/meminfo only takes about 1 ms. Add GetGraphicsMemoryInfo() to read the gpu memory info, GetSystemMemoryInfo() reads /proc/meminfo only. GetGraphicsMemoryInfo() would return false on Intel platform with kernel 5.4 to avoid the slow i915_gem_objects access. (cherry picked from commit 7cc65fc4c97210143ccf8d17c6cb77abb4c22481) Bug: b/170150180, 1134131 Change-Id: I0a0cfb868826b59f508a478d3db69ec089f5d4d5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2449519 Commit-Queue: Kuo-Hsin Yang <[email protected]> Reviewed-by: Wez <[email protected]> Reviewed-by: Cheng-Yu Lee <[email protected]> Reviewed-by: Robert Kaplow <[email protected]> Reviewed-by: Brian Geffon <[email protected]> Reviewed-by: Xiyuan Xia <[email protected]> Cr-Original-Commit-Position: refs/heads/master@{#816143} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2467042 Reviewed-by: Kuo-Hsin Yang <[email protected]> Cr-Commit-Position: refs/branch-heads/4280@{#306} Cr-Branched-From: ea420fb963f9658c9969b6513c56b8f47efa1a2a-refs/heads/master@{#812852}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.