Changes between Version 35 and Version 36 of rpc_implementation

Timestamp:

Jan 17, 2019, 3:54:02 PM (6 years ago)

Author:

alain

Comment:

--

rpc_implementation

@@ -60 +60 @@
 On the server side, a  kernel RPC thread is activated at the next scheduling point on the selected server core, as soon as the RPC_FIFO is non-empty. This server thread executes the following tasks:
 1. extract relevant informations from RPC descriptor stored in client cluster,
-1. depending on the RPC index, call the specific ''roc_xyz_server()'' function to perform the RPC arguments unmarshmaling,
-1. call the recant kernel function to and execute the requested service,
+1. depending on the RPC index, call the specific ''rpc_xyz_server()'' function to perform the RPC arguments unmarshmaling,
+1. call the relevant kernel function to execute the requested service,
 1. atomically increment the responses counter in the client cluster,
 1. if this response is the last expected response, unblocks the client thread, and send an IPI to the client core.