How cisco/exanic-software works
Main Components
a. Hardware Layer:
• ExaNIC ultra-low-latency network cards (e.g., ExaNIC X25, X100, etc.)
b. Kernel-Space Components:
• Linux Kernel (the environment in which the card is integrated).
• Kernel modules (in the “modules” directory): These include two sets – one for the “exanic” driver and one for “exasock” which accelerates sockets operations.
c. User-Space Libraries:
• libexanic (in libs/exanic) – to access low-level card functionality.
• exasock library (in libs/exasock) – for applications to bypass the standard kernel networking stack.
d. Utilities & Control Applications:
• Tools such as exanic-config, exanic-capture, exanic-clock-sync, exanic-fwupdate (found in the “util” directory), which allow configuration, capture, clock synchronization, and firmware updates.
e. Example Applications and Performance Test Tools:
• Examples (located in “examples” with subdirectories for advanced usage, exasock examples, filters, and devkit examples).
• The “perf-test” directory indicates stand-alone performance measurement tools.
f. Packaging & Deployment:
• Packaging scripts and spec files (found in “debian”, “redhat”, “exanic.spec”) help with distribution and installation.
Establish Relationships and Interactions
• Inside the Kernel layer, include connections between the Linux network stack and the loaded kernel modules (exanic and exasock drivers).
• Utilities (exanic-config, capture, clock-sync, fwupdate) as separate components interfacing with the libraries (or directly with the driver interfaces) to perform configuration, monitoring, and management.
• Example applications, demonstrating how developers can interact, with communication paths connecting them to the user-space libraries.
• For the performance testing tools, illustrate how they feed data into the system/integrate with the libraries or drivers to measure latency and throughput.
Recognize Architectural Patterns and Technologies
• Layered architecture – from hardware up through kernel modules to user applications.
• Extensibility points: the driver separation (modules), the dedicated libraries (libexanic and exasock) and the examples demonstrating custom filtering, FPGA-based reconfiguration (as indicated in README), and performance testing.
• Integration with standard Linux networking APIs while also providing custom APIs for high-performance operations.