tweak margo progress loop logic
- make sure that we allow for the possibility of ULTs in the same pool as the progress loop being resumed by external events - rely on abt statistics rather than results of Mercury progress and trigger calls to determine when to yield. Mercury return codes can be slightly ambiguous when not blocking. - this prevents periodic stalls when Margo is used in conjunction with abt-io and/or self forward calls in Mercury.
Showing with 33 additions and 19 deletions