Associate network connections with NUMA nodes
● Allocate local memory to back media files when
they are DMA’ed from disk
● Allocate local memory for TLS crypto destination
buffers & do SW crypto locally
● Run kTLS workers, RACK / BBR TCP pacers with
domain affinity
● Choose local lagg(4) egress port
All of this is upstream!
Basically, everything is about “pinning” the hardware on a low level.
You pin the network adapters to be handled by a specific set of cores.
You pin the filesystem to handle specific sets of files on specific cores.
You then ensure the router in the rack to distribute the http requests to the network ports exactly in the way that they always arrive on the network adapters that have those files pinned.
It’s not much different from partitioning / sharding and “smart” load balancing a cluster of servers, it’s just on a lower level of abstraction.
here it is without acronyms, though not much clearer:
- Associate network connections with "Non-Uniform Memory Architecture" nodes [(a compute core with faster access to some memory, disks, and network-interface-cards)]
- Allocate local memory to back media files when they are direct-memory-access'ed [(directly copied to memory)] from disk
- Allocate local memory for transport-layer-security cryptography destination buffers & do software cryptography locally
- Run kernel-transport-layer-security workers, "Recent Acknowledgment" / "Bottleneck Bandwidth and Round-Trip-Time" Transmission-Control-Protocol pacers with domain affinity
This sounds like some alien language