Thanks for the clarification. I understand the design boundary now: the ring buffer metadata is supposed to describe the allocated record size, not the requested payload size. Given that, I will stop pushing this ring-buffer approach.
If there is a valid fix here, it should be done at the event layer for the users that need the true payload length, not in the generic ring buffer code. Thanks, Cao Ruichuang
