• Linux
• CMake 3.12+
• A C Compiler
• pkg-config
• time -> /usr/bin/time not built-in time command (optional)
• libnuma (optional)
• libibverbs (optional)
• rpmbuild (optional)
• dpkg-buildpackage (optional)

mkdir build
cd build
cmake ..
make
sudo make install

By default, XDD is installed in /usr/bin. In order to change the installation path, use -DCMAKE_INSTALL_PREFIX=<new path> during the configure step.

If CMake discovers libnuma, it will be enabled as a feature in XDD. It can be turned off with -DWITH_NUMA=OFF.

If CMake discovers libibverbs, it will be enabled as a feature in XDD. It can be turned off with -DWITH_VERBS=OFF.

XDD will be built for use with FlameGraph by compiling with -fno-omit-frame-pointer. This can be disabled with -DWITH_FLAMEGRAPH=Off.

To build RPM and DEB packages, make sure rpmbuild or dpkg-buildpackage was discovered by CMake and run make package. The package file will be placed in the root build directory. Note that CPack does not seem to be able to handle having both package builders installed at the same time.

In XDD, the number of threads is often governed by the queue depth option or the thread count option. The number of threads than may be created is system dependent. For example, on my laptop I can only create 916 threads before the system returns a "resource busy or unavailable" error. It's not just a simple memory limitation necessarily either (i.e. reducing the pthread stack size doesn't automatically increase the number of threads you can create). In general, the number of threads that can be initialized by XDD is limited by the system rather than XDD. This is mainly interesting when using fork-thread type access patterns.