{"id":5263,"date":"2025-08-01T12:21:23","date_gmt":"2025-08-01T10:21:23","guid":{"rendered":"https:\/\/perso.uclouvain.be\/tom.barbette\/?p=5263"},"modified":"2025-08-07T12:16:16","modified_gmt":"2025-08-07T10:16:16","slug":"asni","status":"publish","type":"post","link":"https:\/\/perso.uclouvain.be\/tom.barbette\/asni\/","title":{"rendered":"ASNI: Rethinking Packet I\/O for High-Performance Networking"},"content":{"rendered":"\n

Accepted paper to be presented at CoNEXT’25<\/em> ; Nikita Tyunyayev (UCLouvain), Cl\u00e9ment Delzotti (UCLouvain)<\/em>, Haggai Eran (NVIDIA) and Tom Barbette (UCLouvain)<\/em><\/p>\n\n\n\n

In recent years, bypassing the Linux kernel networking stack has become a common strategy to accelerate packet processing. Techniques like DPDK eliminate kernel overhead, enabling network functions to run at much higher speeds. However, these solutions do not fundamentally change how packets are exchanged between the Network Interface Controller (NIC) and the CPU.<\/p>\n\n\n\n

At the core of this communication are descriptors: NIC-specific metadata structures that reference memory buffers and encapsulate information such as VLAN tags, flow IDs, tunnel IDs, timestamps, and L3\/L4 protocol information. Because descriptor formats vary across NIC vendors, both the Linux networking stack and user-space drivers like DPDK must translate these proprietary formats into a generic representation. This translation consumes substantial CPU resources, even though most of the metadata is typically unused by applications. Additionally, applications often perform further metadata transformations themselves. X-Change<\/strong> addresses some of those inefficiencies by proposing a unified model that merges driver-level and application-level metadata.<\/p>\n\n\n\n

Ens\u014d introduced a streaming interface that eliminates pointer indirection by delivering packets as a continuous array. While this improves performance through better memory locality and reduced overhead, it introduces challenges when packets need to be processed out of order, requiring costly copying operations. <\/p>\n\n\n\n

\"Comparing<\/a>
Comparing I\/O processing models<\/figcaption><\/figure>\n\n\n\n

Introducing ASNI: Application-Specific Network Interface <\/strong><\/p>\n\n\n\n

In our CoNEXT 2025 paper, we present ASNI, a new approach that builds upon, rather than replaces, the traditional packetized interface. ASNI delivers packets in large, contiguous buffers, each capable of holding multiple packets and their metadata, organized in a format tailored to the specific needs of the application. By offloading the majority of the driver datapath from the CPU to the NIC, ASNI significantly reduces CPU overhead. <\/p>\n\n\n\n

Our design brings three key benefits <\/p>\n\n\n\n