diff options
Diffstat (limited to 'en/devices/architecture/hidl/threading.html')
| -rw-r--r-- | en/devices/architecture/hidl/threading.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/en/devices/architecture/hidl/threading.html b/en/devices/architecture/hidl/threading.html index 26c2cc12..fef555ad 100644 --- a/en/devices/architecture/hidl/threading.html +++ b/en/devices/architecture/hidl/threading.html @@ -112,7 +112,7 @@ concurrently with future calls from the client (unless the server threadpool has only one thread).</p> <p>In addition to synchronous callbacks, <code>oneway</code> calls from a -single-threadedclient may be handled concurrently by a server with multiple +single-threaded client may be handled concurrently by a server with multiple threads in its threadpool, but only if those <code>oneway</code> calls are executed on different interfaces. <code>oneway</code> calls on the same interface are always serialized.</p> @@ -164,9 +164,9 @@ and does not wait for the server to complete its function call invocation. At th surface (and in aggregate), this means the function call takes half the time because it is executing half the code, but when writing implementations that are performance sensitive, this has some scheduling implications. Normally, -using a oneway call causes the callee to continue to be scheduled whereas +using a oneway call causes the caller to continue to be scheduled whereas using a normal synchronous call causes the scheduler to immediately transfer -from the callee to the caller process. This is a performance optimization in +from the caller to the callee process. This is a performance optimization in binder. For services where the oneway call must be executed in the target process with a high priority, the scheduling policy of the receiving service can be changed. In C++, using <code>libhidltransport</code>'s method |