Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
G
Grpc
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
tci-gateway-module
Grpc
Commits
d6731628
Commit
d6731628
authored
Feb 4, 2015
by
Craig Tiller
Browse files
Options
Downloads
Patches
Plain Diff
Cleanup documentation
parent
30fd935a
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
src/core/surface/call.c
+3
-2
3 additions, 2 deletions
src/core/surface/call.c
with
3 additions
and
2 deletions
src/core/surface/call.c
+
3
−
2
View file @
d6731628
...
@@ -163,11 +163,12 @@ struct grpc_call {
...
@@ -163,11 +163,12 @@ struct grpc_call {
a request, and is valid iff request_set[op] <= GRPC_IOREQ_OP_COUNT.
a request, and is valid iff request_set[op] <= GRPC_IOREQ_OP_COUNT.
The set fields are as per the request type specified by op.
The set fields are as per the request type specified by op.
Finally, one element of masters
[op]
is set per active _
group
_ of ioreq
Finally, one element of masters is set per active _
set
_ of ioreq
operations. It describes work left outstanding, result status, and
operations. It describes work left outstanding, result status, and
what work to perform upon operation completion. As one ioreq of each
what work to perform upon operation completion. As one ioreq of each
op type can be active at once, by convention we choose the first element
op type can be active at once, by convention we choose the first element
of a the group to be the master. This allows constant time allocation
of the group to be the master -- ie the master of in-progress operation
op is masters[request_set[op]]. This allows constant time allocation
and a strong upper bound of a count of masters to be calculated. */
and a strong upper bound of a count of masters to be calculated. */
gpr_uint8
request_set
[
GRPC_IOREQ_OP_COUNT
];
gpr_uint8
request_set
[
GRPC_IOREQ_OP_COUNT
];
grpc_ioreq_data
request_data
[
GRPC_IOREQ_OP_COUNT
];
grpc_ioreq_data
request_data
[
GRPC_IOREQ_OP_COUNT
];
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment