diff options
| author |   ahothan <ahothan@cisco.com> | 2017-08-09 10:12:26 -0700 |
|---|---|---|
| committer | ahothan <ahothan@cisco.com> | 2017-08-09 10:17:14 -0700 |
| commit | 31549982d3bb674ee251cc3f1e9f358badbf632d (patch) | |
| tree | 99b8cdd39cb3a3db998fbe2e7cafb34eb8240801 /docs/development | |
| parent | 0ab04ab7103fc4bfb17042b60c1e005049375cc2 (diff) | |
Update doc/faq and config comments1.0.1
Change-Id: I263f2d33ef9010d4ead0a26c390736a11edaaa20
Signed-off-by: ahothan <ahothan@cisco.com>
Diffstat (limited to 'docs/development')
| -rw-r--r-- | docs/development/design/ndrpdr.rst | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/development/design/ndrpdr.rst b/docs/development/design/ndrpdr.rst index f748476..4f611a0 100644 --- a/docs/development/design/ndrpdr.rst +++ b/docs/development/design/ndrpdr.rst @@ -23,7 +23,12 @@ Call chain for calculating the NDR-PDR for a list of frame sizes: The search range is delimited by a left and right rate (expressed as a % of line rate per direction). +The load_epsilon configuration parameter defines the accuracy of the result as a % of line rate. +The default value of 0.1 indicates for example that the measured NDR and PDR are within 0.1% of line rate of the +actual NDR/PDR (e.g. 0.1% of 10Gbps is 10Mbps). It also determines how small the search range must be in the binary search. + The recursion narrows down the range by half and stops when: - the range is smaller than the configured load_epsilon value - or when the search hits 100% or 0% of line rate + |