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
Now that we have a scheduler and task system in place, we would benefit greatly from not using spinning synchronization primitives. Of course the scheduler/task system themselves and systems they depend on like the kernel heap cannot use the these, but places like the WASM engine or maybe even the virtual memory subsystem could be "asyncified" and made to use async sync primitives.
This issue is the tracking issue for implementing these primitives, here is the list of things I anticipate needing:
The text was updated successfully, but these errors were encountered:
Now that we have a scheduler and task system in place, we would benefit greatly from not using spinning synchronization primitives. Of course the scheduler/task system themselves and systems they depend on like the kernel heap cannot use the these, but places like the WASM engine or maybe even the virtual memory subsystem could be "asyncified" and made to use async sync primitives.
This issue is the tracking issue for implementing these primitives, here is the list of things I anticipate needing:
The text was updated successfully, but these errors were encountered: