d9faa73cbb
Originally DMABufs were imported into a temporary buffer followed by a copy operation into the desktop frame itself. This is not needed as we can import them directly into desktop frames and avoid this overhead. Also drop support for MemPtr buffers as both Mutter and KWin don't seem to support them and they are going to be too slow anyway. Testing with latest Chromium, I could see two processes with usage around 20% and 40% without this change going down to 10% and 20% with this change applied. Bug: webrtc:13429 Bug: chrome:1378258 Change-Id: Ice3292528ff56300931c8638f8e03d4883d5e331 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/297501 Reviewed-by: Alexander Cooper <alcooper@chromium.org> Commit-Queue: Jan Grulich <grulja@gmail.com> Cr-Commit-Position: refs/heads/main@{#39594}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
Development
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation