Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Serializing bitseq alloc #1788
Previously the bitseq alloc was allocating the first available bit from the beginning of the bit sequence for each sequence handle. With this commit the bitseq alloc will proceed
The commit also contains a fix for byteoffset allocation which plays a role in calculating the allocated ordinal. This scenerio play when the starting ordinal is part of the head sequence block and the available bit is part of subsequent blocks in the bitseq.
Signed-off-by: Abhinandan Prativadi email@example.com
changed the title from
Serializing bitseq alloc
[Not Ready for Review ] Serializing bitseq alloc
May 31, 2017
@trapier gossip control plane is a transportation mean, does not take any decision on IP matter also the key of every element is the endpoint ID that is unique.
referenced this pull request
Sep 21, 2017
Understood @fcrisciani. What I was thinking is if there are many joins and leaves occurring at the same time on a particular network (and despite the fact that it has a lamport clock), numerically ordered ip allocation will reduce the likelihood of same-time same-address events on the control plane.
@@ Coverage Diff @@ ## master #1788 +/- ## ========================================= Coverage ? 38.02% ========================================= Files ? 137 Lines ? 27313 Branches ? 0 ========================================= Hits ? 10386 Misses ? 15656 Partials ? 1271
Please sign your commits following these rules:
$ git clone -b "ipam_alloc" firstname.lastname@example.org:abhi/libnetwork.git somewhere $ cd somewhere $ git rebase -i HEAD~842354211816 editor opens change each 'pick' to 'edit' save the file and quit $ git commit --amend -s --no-edit $ git rebase --continue # and repeat the amend for each commit $ git push -f
Amending updates the existing PR. You DO NOT need to open a new one.