How thustorage/term works
Project type and purpose
• TeRM is a systems‐level research artifact that extends RDMA‐attached memory by transparently paging cold pages out to SSD.
• It comprises a patched kernel driver for RDMA NICs, a userspace shared library (libterm/libpdp) that LD_PRELOADs into RDMA apps, the original RDMA applications (octopus, xstore), a memcached metadata service, and an experimental harness (ae/).
File structure
• Top‐level directories:
• ae/ – Artifact Evaluation: scripts, experiment drivers, generated binaries
• app/ – Sample RDMA applications (octopus, xstore) with bug fixes
• driver/ – Patches and prebuilt archives for the RDMA/NIC kernel module
• libterm/ – Userspace library (libpdp.so) and micro‐kernel module (kmod) source
• Key patterns:
• Hooking/interposition (LD_PRELOAD) in libpdp.so to override ibverbs calls
• Kernel module patch for on‐demand paging (ODP) and SSD back‐end
• Experiment automation via shell and Python scripts in ae/scripts
• Configuration:
• CMakeLists.txt for building libterm
• TOML and XML under ae/bin and app for workload configs
• Shell scripts for memcached reset, CPU affinity, driver build
Insights from the README
• Architecture described:
• Client RDMA programs mmap an SSD device and register it as an ODP MR
• libpdp.so intercepts ibv_reg_mr and transparently pages to SSD via the patched driver
• Memcached synchronizes cluster metadata (addresses, ports)
• Dependencies: OFED driver, memcached, Boost/Glog/GFlags libs
• Usage: LD_PRELOAD, environment vars (PDP_server_mmap_dev, PDP_is_server, etc.)
Detail
• Component’s role and interfaces
• Experiment harness separately to indicate where benchmarking and automation occur