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
Today, Arachne does not require the application to inform the runtime when a user-level thread running on an exclusive core exits. However, it is expensive to check on every thread exit for whether the exiting thread was exclusive on a core.
Hence, we lazily check for cores that have been vacated by previous exclusive threads when we need additional cores.
We would like a mechanism for finding out about exclusive thread exit sooner.
The text was updated successfully, but these errors were encountered:
Today, Arachne does not require the application to inform the runtime when a user-level thread running on an exclusive core exits. However, it is expensive to check on every thread exit for whether the exiting thread was exclusive on a core.
Hence, we lazily check for cores that have been vacated by previous exclusive threads when we need additional cores.
We would like a mechanism for finding out about exclusive thread exit sooner.
The text was updated successfully, but these errors were encountered: