修复在threadDispatcher启用时，socket相关的读取造成的死锁问题 #665
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
在threadDispatcherEnabled时，由于使用抢先式调度，会导致socketpair在其中一个线程在接收时，持续占用调度，导致永远无法接收到发送线程的信息。
同理，由于ppoll没有考虑io是否有信息可读，会导致线程持续卡死在后接的recv中，导致实际运行逻辑与实际不符，同时如果其他线程正在同一socket准备发送请求，也会造成死锁。
详细样例可见本fork的master分支