commit | ad3258647ec3945730de4673522c0f09a6663f42 | [log] [tgz] |
---|---|---|
author | Tomas Gunnarsson <tommi@webrtc.org> | Wed Feb 03 15:23:40 2021 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Feb 03 17:44:47 2021 |
tree | 4a3b312be4764651788803f1cb26657425c2a82c | |
parent | 3f7990d38b1ad8d4ae2d8e31385f727560f58b2a [diff] |
Reland "Prepare to avoid hops to worker for network events." This is a reland of d48a2b14e7545d0a0778df753e062075c044e2a1 The diff of the reland (what caused the tsan error) can be seen by diffing patch sets 2 and 3. Essentially I missed keeping the calls to the transport controller on the worker thread. Note to self to add thread/sequence checks to that code so that we won't have to rely on tsan :) Original change's description: > Prepare to avoid hops to worker for network events. > > This moves the thread hop for network events, from BaseChannel and > into Call. The reason for this is to move the control over those hops > (including DeliverPacket[Async]) into the same class where the state > is held that is affected by those hops. Once that's done, we can start > moving the relevant network state over to the network thread and > eventually remove the hops. > > I'm also adding several TODOs for tracking future steps and give > developers a heads up. > > Bug: webrtc:11993 > Change-Id: Ice7ee3b5b6893532df52039324293979196d341d > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/204800 > Commit-Queue: Tommi <tommi@webrtc.org> > Reviewed-by: Niels Moller <nisse@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#33138} Bug: webrtc:11993, webrtc:12430 Change-Id: I4fccaa418d22c2087a55bbb3ddbb25fac3b4dfcc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/205580 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Commit-Queue: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/master@{#33153}
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.
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.