You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 9, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
In the paper,
A
slot
is a upstream cell, for one clientA
round
contains Nslot
, one for each clientAn
epoch
is a succession of rounds between two resync'sA
schedule
assigns eachslot
of around
to a clientUnfortunately, 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 theschedule
An
epoch
is a succession of rounds between two resync'sWe have no terminology for a succession of
N
rounds.The text was updated successfully, but these errors were encountered: