flood dissemination

2 files changed, 8 insertions, 6 deletions

diff --git a/docs/development.md b/docs/development.md
index 9296e8b..ed95bf0 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -30,10 +30,11 @@ unless `BENCH_WRITES` says otherwise (more, to see what grows with them); each
 scenario run several times, one run after another, with `BENCH_REPEAT=3`, and a
 summary of each workload's mean delay and messages per write, run by run (runs
 differ: one can't tell a small change from chance); with
-`SIM_DISSEMINATION=plumtree`, every simulated node passes changes on by PlumTree
-(`--dissemination`), the benchmark's views of the trees still being the writers'
-trees'; with `SIM_TOPOLOGY=hyparview`, every simulated node chooses its neighbours by
-HyParView (`--topology`; with PlumTree, as writers' trees need the shared graph); all at once with
+`SIM_DISSEMINATION=plumtree` (or `flood`), every simulated node passes changes on by
+PlumTree (or by flooding: `--dissemination`), the benchmark's views of the trees still
+being the writers' trees'; with `SIM_TOPOLOGY=hyparview`, every simulated node chooses
+its neighbours by HyParView (`--topology`; with PlumTree unless `SIM_DISSEMINATION`
+says otherwise, as `--dissemination` defaults to then); all at once with
 `BENCH_PARALLEL=1`, faster on many cores, though sharing them makes delays come out
 somewhat higher; and in `bench_bridge`, large values from a writer on a fast transport
 through a bridge to a node on a slow one: what that node gets as sync messages and as
diff --git a/docs/example.toml b/docs/example.toml
index de32ada..a44f1eb 100644
--- a/docs/example.toml
+++ b/docs/example.toml
@@ -189,8 +189,9 @@ htpasswd = "/etc/continuum/htpasswd"
 # superseded-writes = "drop"
 
 # How a change reaches every member: writers-trees (computed alike on every node from
-# the member list) or plumtree (eager links pruned where they deliver twice, grafted
-# where announcements had to bring a change). A genesis node records its own in the
+# the member list), plumtree (eager links pruned where they deliver twice, grafted
+# where announcements had to bring a change) or flood (every change pushed to every
+# neighbour: the baseline). A genesis node records its own in the
 # document; every node follows what the swarm records, which a protocol writer may
 # change (_continuum/dissemination), and uses its own only where the swarm records none
 # it knows.