Skip to content
This repository has been archived by the owner on Jan 9, 2024. It is now read-only.

Consistency between Slot/Round/Epoch/Schedule #160

Open
lbarman opened this issue May 8, 2017 · 0 comments
Open

Consistency between Slot/Round/Epoch/Schedule #160

lbarman opened this issue May 8, 2017 · 0 comments

Comments

@lbarman
Copy link
Collaborator

lbarman commented May 8, 2017

In the paper,
A slot is a upstream cell, for one client
A round contains N slot, one for each client
An epoch is a succession of rounds between two resync's
A schedule assigns each slot of a round to a client

Unfortunately, this is not the case in the code, especially because a round is [1 downstream message]+[N upstream messages].

Proposed terminology:
A cell is on byte message (up- or downstream)
A round is N+1 cells, 1 downstream, N upstream (that gets XORed into one message)
A slot is a position in the schedule
An epoch is a succession of rounds between two resync's
We have no terminology for a succession of N rounds.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant