For our use case, the callback just puts the reported pageI thought you only updated a pre allocated bitmat... Anyway, I cannot
block to the ring, then returns. If the ring is full as the host
is busy, then I think it should skip this one, and just return.
A. This is an optimization feature, losing a couple of free
pages to report isn't that important;
B. In reality, I think it's uncommon to see this ring getting
full (I didn't observe ring full in the tests), since the host
(consumer) is notified to take out the page block right
after it is added.
comment on this part much as I am not familiar with your usecase.