-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UCT: fix hang when using polling fd #1492 #1561
Conversation
34f0416
to
71474ca
Compare
Test FAILed. |
Test PASSed. |
Test FAILed. |
Test PASSed. |
@evgeny-leksikov why need to rearm inside progress, if the user has to explicitly call arm after progress anyway?
so how is adding "arm" after (1) helps, given that we already have arm in (2)? |
@yosefe because arm did not re-arm if there are any events. Pls, take a look now. |
@evgeny-leksikov user should call arm again when getting BUSY, until he gets UCS_OK, which would mean the cq is really re-armed. |
@MattBBaker can you please post ORNL failure? |
@yosefe yes, but some events can be missed between BUSY and next re-arm but not polled from the CQ by progress. So, we have to have re-armed transport all the time. |
Test PASSed. |
@evgeny-leksikov so you mean that if there are unpolled CQEs, and then arm is done, no event is generated? |
yes |
Test FAILed. |
bot:mlx:retest |
@evgeny-leksikov what if the event arrives just before arming is done, and the cq is not armed yet? for example, on the first time? |
Test FAILed. |
Test FAILed. |
@yosefe Looks like a build environment failure. |
bot:ornl:retest |
1 similar comment
bot:ornl:retest |
probably should go to v1.2 as well |
bot:mlx:retest |
Test FAILed. |
the reported issue is not a bug |
Fixes #1492