Simple RMT

This repository is an example of a generic Reconfigurable Match Tables architecture, which illustrates the methodology and approach towards system level design using the PFPSim Framework. The RMT architecture is based on this paper (pdf).

Getting Started:

Prerequisites:

To start exploring this example, the PFPSim Framework is required.

• PFPSim Library and the PFPSim P4 fork
• pfpgen
• pfpdb

Downloading the example

To complete the exercise you will need to clone the repository:

git clone https://github.com/pfpsim/simple-rmt.git

Building the Example:

PFPSim Workflow:

The PFPSim workflow is described in more detail here, but the following is a quick summary.

1. Write structural code in a FAD file.
2. Run pfpgen on your FAD design, which creates:
   • SystemC code for the structural part of the model.
   • Skeleton code for behavioural description of components of the model.
   • Project setup using CMake for build management.
3. Write behavioural code in C++ for components in the design.
4. Simulate.

cd simple-rmt
# Run pfpgen to generate structural code
pfpgen rmt.fad
cd rmt/build
cmake ../src
make

A quick overview of what we just did - Project Setup.

• rmt.fad is the blueprint of how things are built and connected to each other.
• pfpgen converts your structural description into human readable and compilable SystemC code - it literally does 50% of the work for you.
• You (the user) fill in the behavioural skeletons by providing the logic of the modules described in the FAD file in C++.
• Use the generated CMake configuration to build the simulation model.
  • The build directory is generated for out of source builds.
  • The Directory Layout looks something like this:

.
└── rmt
    ├── build             ---------------- Your build directory
    |
    ├── build_static      ---------------- Runtime Configuration Files
    │   ├── Configs
    │   └── validation
    └── src               ---------------- Source Code
        ├── behavioural   ---------------- Behavioural Source Files
        │   └── common
        ├── structural    ---------------- Structural generated code
        └── tries         ---------------- PFPSIM Trie Library
            └── src

Behavioural code for all components is provided in this example and can be found under rmt/src/behavioural/. A complete description of the model is coming soon on our wiki. (#TODO)

Running the Example:

First link all of the config files from rmt/build_static/ into your build directory. You can also just copy them if you want to modify them without affecting the originals.

# From the build dir
ln -s ../build_static/* ./

Simulating:

We provide a convenient wrapper script to simplify the process of running the model:

# Run the Model
./runme.sh normal

####Inputs required by the Model: The simulation model takes many command line arguments to specify its configuration (hence the wrapper script).

• -c <config directory> path to module configuration files
• -X* User Arguments that the user has to specify.
  • -Xp4 <program.json> Compiled P4 application in JSON format. Produced by the P4 compiler.
  • -Xtpop <table-population.txt> Match Action Table population file. See table.txt for the format of this file.
  • -Xin <input.pcap> Input pcap file that is used to generate test traffic for the model.
  • -Xvalidation-out <output.pcap> Pcap file that logs the output of the model. This can be used for functional validation against our P4 validation model.
• -v <level> Verbosity Level, valid verbosity Levels:
  • normal
  • minimal
  • p4profile
  • profile
  • debugger
  • debug

Debugging using pfpdb:

To debug the RMT model with pfpdb, run

#Debug the Model
pfpdb rmt-sim --args "-Xp4 simple_router.json -Xtpop table.txt -v minimal -Xin Configs/irmtt.pcap -Xvalidation-out output.pcap" -v

pfpdb <executable name> --args "<args given to the executable >" -v

Building with Debug Symbols:

This will add debug symbols to your compiled binary ; available for debugging in a debugger like gdb.

cd rmt/build
cmake -DCMAKE_BUILD_TYPE=DEBUG ../src

Building without pfpdb

If you don't plan on using pfpdb. Components required by pfpdb can be compiled out, by specifying the PFPSIMDEBUGGER flag to cmake as

cd rmt/build
cmake -DPFPSIMDEBUGGER=ON|OFF

by default this flag is set to ON

Its status can be checked as:

 $ cd rmt/build
 $ cmake ../src
-- Searching for SystemC
...
...
-- PFPSIM DEBUGGER FLAG IS ON
...
...

Built With

• A whole lot of Coffee and Ice tea 😉.

Contributing

If you'd like to contribute code back to simple-rmt, please fork this github repository and send us a pull request! Please make sure that your contribution passes our continuous integration build.

Any contribution to the C++ core code must respect the coding guidelines as stated on the wiki. We rely heavily on the Google C++ Style Guide, with some differences listed in this repository's wiki. Our Travis builds include running cpplint to ensure correct style and formatting.

Support

If you need help using this project, please send us an email at pfpsim.help@gmail.com - we'd be happy to hear from you!

If you think you've found a bug, or would like to request a new feature, please open an issue using github - we're always trying to improve PFPSim!

License

This project is licensed under the GPLv2 - see LICENSE for details

Authors

Copyright (C) 2016 Concordia Univ., Montreal

• Samar Abdi
• Umair Aftab
• Gordon Bailey
• Faras Dewal
• Shafigh Parsazad
• Eric Tremblay

Copyright (C) 2016 Ericsson

• Bochra Boughzala