You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 30, 2021. It is now read-only.
This is a follow up of #34. Roughly after commit 93333a6, we make our scheduler schedule one-thread-at-a-time. However, there're several downside (beside PRO being more deterministic):
It should be a safe assumption a task is deterministic unless it enters syscalls. hence we can allow parallel execution, upon entry of syscalls, which is serialized.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is a follow up of #34. Roughly after commit 93333a6, we make our scheduler schedule one-thread-at-a-time. However, there're several downside (beside PRO being more deterministic):
It should be a safe assumption a task is deterministic unless it enters syscalls. hence we can allow parallel execution, upon entry of syscalls, which is serialized.
The text was updated successfully, but these errors were encountered: