Currently we have SL API for calling blocking version vs non-blocking version.
However this would require that the root scheduler vs other hierarchical scheduler code be different for this scenario.
@gparmer suggested that we could fix this by passing blocking/non-blocking function at the time of creating a rcvcap for that scheduler. Though this takes away the flexibility of making such decision at runtime, I don't think this flexibility is necessary. We do not make run-time decisions for blocking/non-blocking imo.
This is not done in PR #315 and will be taken up by me after the deadline.
Currently we have SL API for calling blocking version vs non-blocking version. However this would require that the root scheduler vs other hierarchical scheduler code be different for this scenario.
@gparmer suggested that we could fix this by passing blocking/non-blocking function at the time of creating a rcvcap for that scheduler. Though this takes away the flexibility of making such decision at runtime, I don't think this flexibility is necessary. We do not make run-time decisions for blocking/non-blocking imo.
This is not done in PR #315 and will be taken up by me after the deadline.