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
For most operations (e.g., link, monitor etc.) it's likely fine to go through the nodeContextProcessesMap to look up some target process and make modifications. However, when sending a message, going through this Map is quite wasteful. Instead, we could consider keeping a reference to a process' CQueue in its ProcessId, so send pid a doesn't need to go through the process table and can instead simply retrieve the CQueue from the ProcessId and deliver a.
The text was updated successfully, but these errors were encountered:
For most operations (e.g.,
link
,monitor
etc.) it's likely fine to go through thenodeContextProcesses
Map
to look up some target process and make modifications. However, whensend
ing a message, going through thisMap
is quite wasteful. Instead, we could consider keeping a reference to a process'CQueue
in itsProcessId
, sosend pid a
doesn't need to go through the process table and can instead simply retrieve theCQueue
from theProcessId
and delivera
.The text was updated successfully, but these errors were encountered: