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
As I read the code, I find that there are at most three opportunities for a request to trigger schedule_request: after adding a new request, after a request completed and when a non-ready request gets ready. My question is, will dmclock queue get stuck if can_handle_fn frequently return false and waste all the opportunities to call schedule_request?
The text was updated successfully, but these errors were encountered:
As I read the code, I find that there are at most three opportunities for a request to trigger schedule_request: after adding a new request, after a request completed and when a non-ready request gets ready. My question is, will dmclock queue get stuck if can_handle_fn frequently return false and waste all the opportunities to call schedule_request?
The text was updated successfully, but these errors were encountered: