From 79afc744017bd0e060c9629044e331fc1f4cd74c Mon Sep 17 00:00:00 2001 From: Steven Moreland Date: Mon, 10 Feb 2025 16:56:01 +0000 Subject: libbinder_rs: disambiguate startThreadPool "recommendation" This is only required for processes that want multiple threads, and this takes more resources than a single thread. Bug: N/A Test: N/A Change-Id: I1131be291dfbcb13fad1b6d4a6e33697812cbd5b --- libs/binder/rust/src/state.rs | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'libs') diff --git a/libs/binder/rust/src/state.rs b/libs/binder/rust/src/state.rs index 8a06274e9c..145ae651d7 100644 --- a/libs/binder/rust/src/state.rs +++ b/libs/binder/rust/src/state.rs @@ -28,8 +28,9 @@ impl ProcessState { /// `num_threads` additional threads as specified by /// [`set_thread_pool_max_thread_count`](Self::set_thread_pool_max_thread_count). /// - /// This should be done before creating any Binder client or server. If - /// neither this nor [`join_thread_pool`](Self::join_thread_pool) are + /// If this is called, it must be done before creating any Binder client or server. + /// + /// If neither this nor [`join_thread_pool`](Self::join_thread_pool) are /// called, then some things (such as callbacks and /// [`IBinder::link_to_death`](crate::IBinder::link_to_death)) will silently /// not work: the callbacks will be queued but never called as there is no -- cgit v1.2.3-59-g8ed1b