[Direct Receiver] Viz Compositor Direct Receiver for FrameSinkManager By making the primary interface from a group of associated interfaces direct, all the interfaces involved become Direct Receivers. This CL converts the primary interface (FrameSinkManager) to a direct receiver, allowing RCFSI, DisplayPrivate (and many other interfaces) to benefit from reduced latency by eliminating the I/O thread hop. NOTE: This surfaces a subtle behaviour of Direct Receiver. Every pending receiver passed through FSM will receive I/O on the VizCompositor thread. This is fine as long as those receivers are bound to VizCompositor, which seems to be the case here. The bug contains more details. Bug: 430256405 Change-Id: Icd60262483428f24d4f01616f2ba407eddef3a63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6655377 Reviewed-by: Jonathan Ross <jonross@chromium.org> Reviewed-by: Daniel Cheng <dcheng@chromium.org> Commit-Queue: Nafis Abedin <nafisabedin@google.com> Reviewed-by: Zhenyao Mo <zmo@chromium.org> Cr-Commit-Position: refs/heads/main@{#1504686}
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.