Google Git
Sign in
chromium / chromium / src / fc048525c4b49065cde5064c313dc19a7b660a33
commitfc048525c4b49065cde5064c313dc19a7b660a33[log] [tgz]
authorSaifuddin Hitawala <hitawala@chromium.org>Wed May 21 19:46:27 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 21 19:46:27 2025
tree5a861c8e22d40dd2ccae9360bc11d95183fcb13e
parent0648e0709d9d952472a11332e3f042b58ab3c02a [diff]
[gpu] Add dedicated memory bit for Ganesh/Vulkan lazy allocations

While investigating high GPU memory usage for Graphite/Dawn/Vulkan
we found that transient lazy memory allocations in both Ganesh/Vulkan
and Graphite/Danw/Vulkan are being tracked as part of total and used
vulkan memory allocations. Since presumable Graphite allocates more
transient memory and this memory is lazily allocated it is better to
track this separately.

This change adds a dedicated memory bit for lazily allocated memory
so that the memory is a dedicated allocation. This will allow us to
easily calculate the total real allocated and used memory that is
not lazily allocated/sub-allocated from this memory. Follow-up CLs
will update this tracking for ganesh and graphite.

Bug: 407730048
Change-Id: I3bf2e9694f27d93efdc241f062c10a3e0f07c2b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6574477
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Saifuddin Hitawala <hitawala@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1463659}
1 file changed
tree: 5a861c8e22d40dd2ccae9360bc11d95183fcb13e
  1. .github/
  2. android_webview/
  3. apps/
  4. ash/
  5. base/
  6. build/
  7. build_overrides/
  8. buildtools/
  9. cc/
  10. chrome/
  11. chromecast/
  12. chromeos/
  13. codelabs/
  14. components/
  15. content/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. gpu/
  25. headless/
  26. infra/
  27. ios/
  28. ipc/
  29. media/
  30. mojo/
  31. native_client_sdk/
  32. net/
  33. pdf/
  34. ppapi/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. clank
  51. internal
  52. ios_internal
  53. native_client
  54. signing_keys
  55. v8
  56. .clang-format
  57. .clang-tidy
  58. .clangd
  59. .git-blame-ignore-revs
  60. .gitallowed
  61. .gitattributes
  62. .gitignore
  63. .gitmodules
  64. .gn
  65. .mailmap
  66. .rustfmt.toml
  67. .vpython3
  68. .yapfignore
  69. ATL_OWNERS
  70. AUTHORS
  71. BUILD.gn
  72. CODE_OF_CONDUCT.md
  73. codereview.settings
  74. CPPLINT.cfg
  75. CRYPTO_OWNERS
  76. DEPS
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. SECURITY_OWNERS
  86. WATCHLISTS
README.md

Logo Chromium

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.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

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.

If you found a bug, please file it at https://crbug.com/new.