Skip to content

Use GRPC_CLOSURE_SCHED instead of GRPC_CLOSURE_RUN in complete_closure_step#18491

Merged
yashykt merged 1 commit intogrpc:masterfrom
yashykt:httpclosuresched
Mar 27, 2019
Merged

Use GRPC_CLOSURE_SCHED instead of GRPC_CLOSURE_RUN in complete_closure_step#18491
yashykt merged 1 commit intogrpc:masterfrom
yashykt:httpclosuresched

Conversation

@yashykt
Copy link
Copy Markdown
Member

@yashykt yashykt commented Mar 25, 2019

Use GRPC_CLOSURE_SCHED instead of GRPC_CLOSURE_RUN in complete_closure_step.

Doing this makes sure that we will be done executing code in the calling function before we run the closure.

@yashykt yashykt requested a review from markdroth March 25, 2019 18:54
@yashykt yashykt added the release notes: no Indicates if PR should not be in release notes label Mar 25, 2019
Copy link
Copy Markdown
Member

@markdroth markdroth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make sure that this does not affect performance before merging.

@yashykt
Copy link
Copy Markdown
Member Author

yashykt commented Mar 27, 2019

Internal benchmark runs do not show any negative affect

@yashykt
Copy link
Copy Markdown
Member Author

yashykt commented Mar 27, 2019

Thanks for reviewing!

@yashykt
Copy link
Copy Markdown
Member Author

yashykt commented Mar 27, 2019

Macos failure looks infra related but kokoro is currently facing issues so cannot rerun.
Distrib tests should get fixed by #18475

@yashykt yashykt merged commit 59ffdd9 into grpc:master Mar 27, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 25, 2019
@yashykt yashykt deleted the httpclosuresched branch May 18, 2023 19:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release notes: no Indicates if PR should not be in release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants