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.
(This PR is more of a question mark, there's an unpleasant change to make this POC work, and perhaps
domainslib
shouldn't provide this primitive?)When using a lockfree datastructure to communicate between tasks, I didn't find a way to write the basic strategy "failed to make progress, retry later". With standard domains, we can use
Domain.cpu_relax ()
to spinlock a bit... but with tasks this can deadlock the current domain (if we are waiting on a task scheduled on the same domain, we'll never give it a chance to run). Of course it (slowly) works if another domain steals our pending tasks, but all the domains may actually be stuck and unable to help.I've included a small artificial example to demonstrate the issue :)