MTU configuration, TCP customization and DPDK 16.07

v1.3:

FEATURES:

• Upgrade to DPDK 16.07.
• Add MTU configuration.
• Add TCP stack customization.

FIXED ISSUES:

• Fixed L3 IP initialization from the CLI.

KNOWN ISSUES:

• See v1.2

API CHANGES:

• Aggregated Update* RPC APIs in a single UpdateTestCase API.
• Added SetPortOptions/GetPortOptions and SetTcpSockopt/GetTcpSockopt RPC APIs
  for configuring Port related options (MTU) and TCP Stack related options.

v1.2:

FEATURES:

• Upgrade to DPDK 16.04.
• Add Ring Interface support to allow running WARP17 without using physical
  Ethernet interfaces.
• Add command line options for customizing packet pool sizes in 1K multiples.
• Update command line options for customizing TCB/UCB pool sizes to 1K multiples versus 1M multiples.

FIXED ISSUES:

• Extra validation for command line core-queue mappings (qmap).

KNOWN ISSUES:

• See v1.1

API CHANGES:

• No Changes

v1.1:

FEATURES:

• Add details on where to download the prebuilt & configured WARP17 VM
• Add perl scripting support

FIXED ISSUES:

• Correct display of numa_node in "show port info"

KNOWN ISSUES:

• See v1.0

API CHANGES:

• No changes

v1.0:

FEATURES:

• HTTP 1.1 Client/Server Application traffic generation.
• RAW TCP Client/Server Application traffic generation.
• RAW UDP Client/Server Application traffic generation.
• Python API for configuring, monitoring and controlling test cases.

KNOWN ISSUES:

• When using a DUT (e.g., NAT device) between clients and servers, the
  sessions on the DUT should be cleared after every test. This is required
  because whenever a test-case stops, either because the pass-criteria was
  reached or because it was explicitly stopped, the connections are forcefully
  closed by WARP17 without performing the normal close sequence (e.g., no FIN is
  sent for TCP). The DUT will only clear the existing sessions once its local
  timeout expires.
• Client test cases are automatically stopped when the pass-criteria is
  reached. This, however, is not the case for server test cases. The
  pass-criteria for server test-cases is to have all the servers up and
  waiting for connections. Therefore, even if a server test-case shows status
  PASSED it MUST still be explicitly stopped ("stop tests port ") when
  the user decides that the test has completed. This must be done in order to
  avoid keeping server connections established forever when the clients silently
  went down (e.g., when the client test case is manually stopped).
• Limited ARP table + limited number of L3 interfaces (TPG_TEST_MAX_L3_INTF):
  only 10 interfaces supported per port for now
• No VLAN support.
• No TCP options or keep-alive support.
• No IPv4 fragmentation support (neither on the send side nor on the receive side).

API CHANGES:

• Initial release