Intel® Ethernet 800 Series Application Device Queues (ADQ)

Software Developer's Guide

ID Date Version Classification
626536 04/03/2023 Public
Document Table of Contents
Document Table of Contents
Legal and Disclaimers Revision History Introduction Selecting Applications for ADQ Acceleration Adapting Applications to Take Advantage of ADQ Resources SO_REUSEPORT Patch - NGINX
Legal and Disclaimers
Revision History
Introduction
Introduction Application Device Queues (ADQ) Technology
Application Device Queues (ADQ) Technology
Application Device Queues (ADQ) Technology Option 1: Application Dependent Polling (ADQ1.0) Option 2: Application Independent Polling Method (ADQ2.0) Comparison of Polling Methods
Option 1: Application Dependent Polling (ADQ1.0)
Option 2: Application Independent Polling Method (ADQ2.0)
Comparison of Polling Methods
Selecting Applications for ADQ Acceleration
Adapting Applications to Take Advantage of ADQ
Adapting Applications to Take Advantage of ADQ SO_INCOMING_NAPI_ID Approach for Applications Written in C Programming Language SO_ATTACH_REUSEPORT_CBPF Approach SO_INCOMING_NAPI_ID Approach for Java-Based Applications
SO_INCOMING_NAPI_ID Approach for Applications Written in C Programming Language
SO_INCOMING_NAPI_ID Approach for Applications Written in C Programming Language Example Application: Memcached Design and Implementation
Example Application: Memcached Design and Implementation
Example Application: Memcached Design and Implementation Default Design Change Necessary for ADQ Enablement
Default Design
Change Necessary for ADQ Enablement
SO_ATTACH_REUSEPORT_CBPF Approach
SO_ATTACH_REUSEPORT_CBPF Approach Example Application: NGINX Design and Implementation
Example Application: NGINX Design and Implementation
Example Application: NGINX Design and Implementation Default Design Change Necessary for ADQ Enablement
Default Design
Change Necessary for ADQ Enablement
SO_INCOMING_NAPI_ID Approach for Java-Based Applications
Resources
SO_REUSEPORT Patch - NGINX
SO_REUSEPORT Patch - NGINX
SO_REUSEPORT Patch - NGINX

Change Necessary for ADQ Enablement

To align application worker threads to network adapter queues, the select application worker thread step from the default design above can be changed to perform load balancing of connections to worker threads via NAPI_​ID rather than round-robin. following is the pseudo code for this change:

Query socket option (SO_INCOMUNG_NAPI_ID) on accepted connection Select thread based on NAPI-ID if existing association of THREAD to NAPI_ID -> Select the associated thread else -> Select next available thread from thread pool and set up NAPI_ID to THREAD association

For more information, refer to the Memcached patch submitted at either of the following locations:

SO_ATTACH_REUSEPORT_CBPF Approach