Changes between Version 38 and Version 39 of rpc_implementation
- Timestamp:
- Jan 17, 2019, 4:00:43 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
rpc_implementation
v38 v39 88 88 At any time, only one RPC thread has the FIFO ownership and can consume RPC requests from the FIFO. 89 89 90 Therefore, it can exist for each RPC_FIFO[i,k] a variable number M of activeRPC threads: the running one is the FIFO owner, and the (M-1) others are blocked on a wait condition.90 Therefore, it can exist for each RPC_FIFO[i,k] a variable number M of RPC threads: the running one is the FIFO owner, and the (M-1) others are blocked on a wait condition. 91 91 This number M can temporarily exceed the CONFIG_RPC_THREAD_MAX value, but the exceeding server threads are destroyed when the temporary overload is solved. 92 92