From 31549982d3bb674ee251cc3f1e9f358badbf632d Mon Sep 17 00:00:00 2001 From: ahothan Date: Wed, 9 Aug 2017 10:12:26 -0700 Subject: Update doc/faq and config comments Change-Id: I263f2d33ef9010d4ead0a26c390736a11edaaa20 Signed-off-by: ahothan --- docs/development/design/ndrpdr.rst | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'docs/development') 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 + -- cgit 1.2.3-korg