RFR: Classic problem 02 producer consumer problem - second try

[Aleksey Shipilev]

On Tue, 9 Nov 2021 00:10:23 GMT, Michael Mirwaldt <duke at openjdk.java.net> wrote:

> This sample implements some solutions from the wikipedia article about the producer-consumer-problem on https://en.wikipedia.org/wiki/Producer%E2%80%93consumer_problem .
> It contains these solutions:
> - _OneProducerOneConsumer_ with semaphores
> - _FlawedTwoProducersOneConsumer_ with semaphores in which the producers sometimes use the same index for their items and overwrite each others item in the buffer
> - _FixedTwoProducersOneConsumer_ with semaphores which uses an extra lock for the index so that the producers never use the same index for their items
> - _Lock_ doesn't use any sempahores but a reentrant lock with two conditions. It supports many producers and many consumers
> - _AtomicIntegers_ neither uses any semaphores but two atomic integers and supports one producer and one consumer.
> 
> I have decided not to implement the last solution with finite-range single writer registers in the wikipedia article. It looked far too complicated to me.

I believe you end up in this mess because your `mmirwaldt:master` has your own commits. You are not supposed to commit anything to `master`. If you want to bring `mmirwaldt:master` to the state of upstream `master`, you just need to fetch it. Either in GitHub UI ("Fetch Upstream"), or in Skara tools ("git sync"), or via raw Git commands (you can google a bit for them). But the core invariant is that your local `master` should not have your "diverged" commits -- only the branches should have them. This way your PRs would not bring excessive changesets.

If I were you, I would dump the `mmirwaldt` fork, do a clean fork, pushed the work in the branch there, recreated the PR.

-------------

PR: https://git.openjdk.java.net/jcstress/pull/103