chore: updated max_link_latency

n-hop · Oct 22, 2024 · 5efbb64 · 5efbb64
1 parent 5d125b0
commit 5efbb64
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -43,7 +43,7 @@ Detailed information can be found in [Protocols and Tools](docs/protocols_and_to
 
 ## Limitations
 
-- **Link latency**: The valid range is 0-100ms; 0ms means no additional latency is added. And the maximum latency of each link is 100ms.
+- **Link latency**: The valid range is 0-110ms; 0ms means no additional latency is added. And the maximum latency of each link is 110ms.
   The link latency is simulated by the Linux `tc` module, which requires sufficient queuing buffer capacity. If the queuing buffer is not large enough, `tc` module will drop packets under heavy traffic, affecting the accuracy of simulating the link loss rate.
 
 - **Link bandwidth**: The valid range is 1-100Mbps. The maximum bandwidth for each link is limited because the processing rate of the BATS™ protocol binary in this repository is capped at 100Mbps. For rates higher than 100Mbps, a software license from n-hop is required.
diff --git a/src/containernet/linear_topology.py b/src/containernet/linear_topology.py
@@ -4,7 +4,7 @@
 from .topology import (ITopology, MatrixType, MatType2LinkAttr, LinkAttr)
 
 max_link_bandwidth = 100
-max_link_latency = 100
+max_link_latency = 110
 
 
 class LinearTopology(ITopology):