Skip to content
Matt Callaghan edited this page May 1, 2018 · 20 revisions

TRex wiki

Release Notes

How to build TRex

$cd linux_dpdk
$./b configure  (only once)
$./b build

Build Output will be in "scripts" folder

more options

$./b configure --sanitized
$./b configure --gcc6
$./b configure --no-mlx
$./b configure --with-ntacc

How to debug with gdb TRex

from "scripts" folder

$./t-rex-64-debug-gdb [args]

this script will load set the patch to so and run gdb

How to build TRex Simulator

$cd linux
$./b configure  (only once)
$./b build

Build Output will be in "scripts" folder

Run simulation unit-test

$cd script
$./bp-sim-64 --ut
$./bp-sim-64-debug --ut

Run simulation functional

$cd script
$ ./run_regression --func

Documentation

Presentations

Video of DPDK 2015 summit: https://www.youtube.com/watch?v=U0gRalB7DOs

Manual

Download

TRex on your laptop (using VirtualBox OVA)

TRex Sandbox

Python API

Running regression

In case you did some changes in code and/or want to check some new NIC, you can run our regression:

  1. Create TRex config file: sudo ./dpdk_setup_ports.py -i

  2. Run TRex daemon: sudo ./trex_daemon_server start

  3. Make a copy of directory with setup parameters: automation/regression/setups/trex07

  4. Update yaml files in that directory if needed

  5. Run full regression:
    ./run_regression --cfg ./automation/regression/setups/<new dir>

Note
  • Running specific test:
    ./run_regression --cfg ./automation/regression/setups/<new dir> -t <part of test name>

  • Running only stateless tests can be done without waiting for TRex server to be brought up each time:

    • Run in one shell the interactive server: sudo ./t-rex-64 -i

    • Run in another shell the regression with flags: --stl --no-daemon

  • Specifying setup directory can be done only once with environment variable SETUP_DIR, for example:
    export SETUP_DIR=trex07