balsoft/ligo
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

[doc] Reword section in gretlist in p2p.rst

Browse Source
This commit is contained in:
Pietro 2018-04-26 13:52:39 +02:00 committed by Grégoire Henry
parent fe9c06b7ca
commit 0f1916981b
1 changed files with 9 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/whitedoc/p2p.rst
View File

@ -33,10 +33,7 @@ bandwidth usage as well as implementing different policies
(e.g. read/write quotas) to different peers. For now, each peer is (e.g. read/write quotas) to different peers. For now, each peer is
granted a fair share of the global allocated bandwidth, but it is granted a fair share of the global allocated bandwidth, but it is
planned for the individual allocated bandwidth to each peer to be a planned for the individual allocated bandwidth to each peer to be a
function of the peer's score. Each connection has a read (resp. write) function of the peer's score.
queue where data is copied at a rate of ``max_download_speed /
num_connections`` (resp. ``max_upload_speed / num_connections``).
Encryption Encryption
~~~~~~~~~~ ~~~~~~~~~~
@ -89,16 +86,14 @@ will decide how this new connection must be handled.
{Black, While, Grey}lists {Black, While, Grey}lists
~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~
The welcome worker takes care of filtering all incoming connections The welcome worker takes care of filtering all incoming connections using two
using two static lists of addresses provided either by ``tezos-admin`` static lists of addresses handled either by ``tezos-admin-client`` and a system
or directly in the configuration file. Also, an automatic (grey) list table that is handled automatically by the p2p layer. The node admin can block
is handled automatically by the p2p layer. The node admin can block or or whitelist individual ip addresses, while the p2p layer is in charge of
whitelist individual ip addresses, while the p2p layer can temporarily temporarily banning ip addresses and peers who misbehave. The delay to remove
ban ip addresses and peers who misbehaved. The delay to remove an ip an ip address from the greylist table is defined by the configuration variable
address from the greylist table is defined by the configuration ``greylist_timeout``, while peers that are greylisted are periodically removed.
variable ``greylist_timeout``, while peers are greylisted in a The node admin can also flush greylist tables with the ``tezos-admin-client``.
fixed-size ring buffer and periodically removed. The node admin can
also flush greylist tables with the ``tezos-admin`` client.
Maintenance worker Maintenance worker
------------------ ------------------