Question about Shenandoah pacer

[Kemper, William]

I'm considering a change that would have the heap notify the pacer directly of allocations. Currently, the heap notifies ShenandoahControlThread of words allocated, where they are accumulated into an _alloc_seen member. On iterations of the control thread loop that do not perform a GC, the accumulated _allocs_seen are passed to the pacer (otherwise, they are dropped and reset at the start of the next loop). Would there be harm in having the heap send these alloc'd words directly to the pacer?


I'm also a little confused because these 'allocs_seen' are added to the pacer's budget - I thought allocations consumed the budget?


Thank you,

William