diff options
author | Vratko Polak <vrpolak@cisco.com> | 2021-02-09 17:16:21 +0100 |
---|---|---|
committer | Tibor Frank <tifrank@cisco.com> | 2021-02-12 08:55:30 +0000 |
commit | 26328f390e81f7bcfd536fb7faabaa224d82f857 (patch) | |
tree | 264c3c4d44be0df7535c95282f012060d8770e46 /docs/report/introduction/methodology_packet_flow_ordering.rst | |
parent | 42a4834d143fe480d70aaed3c1ebb9eb9681d53e (diff) |
Methodology: Added packet flow ordering
Change-Id: If0f0397c2ace9112490e017ec8d18cfbf1dffbc5
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
Signed-off-by: Maciek Konstantynowicz <mkonstan@cisco.com>
Diffstat (limited to 'docs/report/introduction/methodology_packet_flow_ordering.rst')
-rw-r--r-- | docs/report/introduction/methodology_packet_flow_ordering.rst | 42 |
1 files changed, 42 insertions, 0 deletions
diff --git a/docs/report/introduction/methodology_packet_flow_ordering.rst b/docs/report/introduction/methodology_packet_flow_ordering.rst new file mode 100644 index 0000000000..3796b21796 --- /dev/null +++ b/docs/report/introduction/methodology_packet_flow_ordering.rst @@ -0,0 +1,42 @@ +.. _packet_flow_ordering: + +Packet Flow Ordering +^^^^^^^^^^^^^^^^^^^^ + +TRex Traffic Generator (TG) supports two main ways how to cover +address space (on allowed ranges) in scale tests. + +In most cases only one field value (e.g. IPv4 destination address) is +altered, in some cases two fields (e.g. IPv4 destination address and UDP +destination port) are altered. + +Incremental Ordering +-------------------- + +This case is simpler to implement and offers greater control. + +When changing two fields, they can be incremented synchronously, or one +after another. In the latter case we can specify which one is +incremented each iteration and which is incremented by "carrying over" +only when the other "wraps around". This way also visits all +combinations once before the "carry" field also wraps around. + +It is possible to use increments other than 1. + +Randomized Ordering +------------------- + +This case chooses each field value at random (from the allowed range). +In case of two fields, they are treated independently. +TRex allows to set random seed to get deterministic numbers. +We use a different seed for each field and traffic direction. +The seed has to be a non-zero number, we use 1, 2, 3, and so on. + +The seeded random mode in TRex requires a "limit" value, +which acts as a cycle length limit (after this many iterations, +the seed resets to its initial value). +We use the maximal allowed limit value (computed as 2^24 - 1). + +Randomized profiles do not avoid duplicated values, +and do not guarantee each possible value is visited, +so it is not very useful for stateful tests. |