Uploaded image for project: 'VinePerf'
  1. VinePerf
  2. VINEPERF-115

Added packet resequencing and packet loss support to l2fwd

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • None
    • None

      As a VSPERF user I want to have tests that validates performance when packets are received out of sequence or when packets are lost during transmission. Since the packet generators will generate packets in sequence the processing chain must be disrupted to re-order them ( but NOT renumber them ). While some generators may have the ability to skip certain packets ( simulating packet loss ) this is not a global capability.

      This ticket is to add the ability to intermittently drop packets or to resequence packet order.

      The existing command line options for l2fwd should be extended to include:

      resequence=XXX

      To designate the packet windows to be resequence. So if the resequence count is 10 then each group of 10 packets will get resequenced. It is acceptable to simply reverse the packet order but the optimal implementation would randomly select packets from the resequencing windows such that all packets are transmitted but the order is random.

      packet_loss=[count,window]

      To designate a packet loss rate for a packet windows. So if
      packet_loss=1,100
      would randomly drop 1 packet out of every 100.

      This requirement may be extended to include factor flags such 'M' for 1000 packets or 'G' for 1,000,000 packets.

      It is acceptable for these tests to introduce minimal latency due to the additional packet processing overhead.

            egbertfitzwilly Gene Snider
            egbertfitzwilly Gene Snider
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 2 days
                2d
                Remaining:
                Remaining Estimate - 2 days
                2d
                Logged:
                Time Spent - Not Specified
                Not Specified