Ring buffer implementation ported from OSCL

[mnmoron]

Add a ring buffer implementation that was simplified-modified-and ported from OSCL.

[mnmoron]

@johnttaylor The "Run Windows build script" CI has been "executing" for 22 hours now.

[johnttaylor]

@mnmoron the build machine is not in the running state. Not sure why Github has not figured out the build failed :(. That said - you need to add unit test for new Ring buffer (in the _0test/) directory. In theory when you push your changes for the unit tests - it should trigger a new build

[johnttaylor]

Why does RxDesc have commitAll() and TxDesc does not?

[mnmoron]

This was driven by a need in a particular situation where the receiver (a framer) needed to read a number of items ahead before deciding to commit() or rewind ( resetAllocationOffset() ).
This operation is an optimization making use of the RxDesc internal knowledge rather than calling commit() n-times in a loop.
There has not been any particular situation where a similar mechanism was needed by a TxDesc client.

[mnmoron]

That said - you need to add unit test for new Ring buffer (in the _0test/) directory.

Will that work if I move the Ring code to Cpl/Container/Ring ? Or will I need a whole new test application rather than adding an additional test to Cpl/Container/_0test?

[johnttaylor]

@mnmoron Solved the mystery on why the build does not work...
References service endpoint. PRs from repository forks are not allowed to access secrets in the pipeline. For more information see https://go.microsoft.com/fwlink/?linkid=862029

Not sure how to fix this. That is problem for later this week.