Google Git
Sign in
chromium / chromium / src / 5c65041f496a122d09e5e2a8fcfe28a9e0884734
commit5c65041f496a122d09e5e2a8fcfe28a9e0884734[log] [tgz]
authorFei Shao <fshao@chromium.org>Mon May 27 16:06:26 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 27 16:06:26 2024
tree19b50493d1ec1a1c61b23a0da7dc94028b39605e
parent064bf98dfae995738418058266512389b03ecc28 [diff]
ozone/drm: Restrict maximum cursor buffer size

Some platforms, e.g. MediaTek, support the cursor plane as an additional
hardware plane. As a result, the supported cursor size from DRM driver
can be as large as 2048 or 4096 (or potentially larger).

In such cases, allocating two 4096*4096*4 buffers for a cursor plane
is wasteful - that's 128MB of RAM solely for rendering the cursor.

On the other hand, Intel GPUs support a maximum cursor size of 256,
which should be sufficiently large for most non-Intel platforms as well.

Therefore, limit the cursor size to a maximum of 256, so that only two
256*256*4 buffers will be allocated i.e. 0.5MB.
That directly frees up hundred of RAM back to the system on platforms
like MediaTek.

Bug: b/342940839

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