diff options
author | Sree Kuchibhotla <sreek@google.com> | 2018-09-27 12:28:21 -0700 |
---|---|---|
committer | Sree Kuchibhotla <sreek@google.com> | 2018-09-27 12:28:21 -0700 |
commit | c1f880d9fe0e0ce810fb50f7ac6ebe5bedee3922 (patch) | |
tree | e20e375f1919ed2ab757f6e7e2fd0be32bd3d167 | |
parent | a74492e8a41a086f82d73f640d0e69d187c38be6 (diff) |
Minor change
-rw-r--r-- | doc/core/grpc-client-server-polling-engine-usage.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/core/grpc-client-server-polling-engine-usage.md b/doc/core/grpc-client-server-polling-engine-usage.md index 8de3979a56..fa54f94621 100644 --- a/doc/core/grpc-client-server-polling-engine-usage.md +++ b/doc/core/grpc-client-server-polling-engine-usage.md @@ -26,7 +26,7 @@ This document talks about how polling engine is used in gRPC core (both on clien ## gRPC server - The listening fd (i.e., the socket fd corresponding to the server listening port) is added to each of the server completion queues. Note that in gRPC we use SO_REUSEPORT option and create multiple listening fds but all of them map to the same listening port -- A new incoming channel is randomly assigned to some server completion queue (see picture below) +- A new incoming channel is assigned to some server completion queue picked randomly (note that we currently [round-robin](https://github.com/grpc/grpc/blob/v1.15.1/src/core/lib/iomgr/tcp_server_posix.cc#L231) over the server completion queues) ![image](../images/grpc-server-cq-fds.png) |