3 ms·
Is the per-packet processing in Wireguard stateless? As in, no sequential packet numbering in the crypto, etc? If yes, then you should be able to get the kerne
by yencabulator 4y ago
Is the per-packet processing in Wireguard stateless? As in, no sequential packet numbering in the crypto, etc?
If yes, then you should be able to get the kernel to spread your incoming traffic across cores with minimal contention and coordination, with multiqueue tuntap:
https://www.kernel.org/doc/html/latest/networking/tuntap.html#multiqueue-tuntap-interface https://www.kernel.org/doc/html/latest/networking/tuntap.htm...
https://lwn.net/Articles/459270/ https://lwn.net/Articles/459270/
- raggi 4y agoAbsolutely multiqueue is on the list. What that would in theory allow us to solve well is rss/xss. As mentioned above, we would still have to fan out crypto, which means we need to solve for numa aware queue processing, which isn’t immediately solvable with the current go runtime APIs. Lots of interesting things to work on!