How emmericp/ixy works
• Application Layer:
• “app” directory as the high-level entry point with the applications (ixy-fwd, ixy-pcap, ixy-pktgen). These examples demonstrate different packet processing use cases (forwarding, packet generation, etc.).
• Driver Layer:
• Support/Utility Components:
• Shared modules such as “interrupts”, “memory”, “pci”, “stats”, and the VFIO library (libixy-vfio). These provide foundational services like memory management (including hugepages support), interrupt handling, and PCI device enumeration/control.
Relationships and Interactions
• Start from an Application example (e.g., ixy-fwd) invoking library calls that manage packet reception and forwarding.
• Calls interacting with both the driver-specific modules (ixgbe or virtio) and the lower-level hardware abstraction layers.
• Link the low-level modules (memory, PCI, and interrupts) with the driver layer — since they set up buffers, configure NIC registers, handle DMA descriptors, and manage interrupt requests.
Architectural Patterns and Design Principles
• Modular and Layered Architecture:
• The separation into application, driver, and utilities clearly follows modular design principles; each component is responsible for a distinct part of the overall system.
• Low-Level Direct Hardware Access:
• That there is no kernel-space dependency for networking – the driver runs entirely in user space. Thus, illustrate how “ixy” bypasses the kernel’s typical network stack.
• Simplicity for Educational Purpose:
Incorporate Specific Technologies and “IOMMU/VFIO” Path
• For systems that use VFIO (and IOMMU), include an alternate path:
Capturing Essential Details
• Every module from the file tree that contributes to system functionality is represented.