You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, RSS is generally 2 or 4 tuple hashed, has the following problems:
It isn't consistent for the lifetime of all QUIC connections, when there is a change in the tuple (NAT rebinding, migration).
It doesn't allow for any customization of the load balancing; it's effectively random.
Proposed solution
We need to design/implement a new HW offload for QUIC aware RSS, where the NIC uses the connection ID (CID) to load balance instead. We should document the offload on https://github.com/microsoft/net-offloads.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature you'd like supported
Currently, RSS is generally 2 or 4 tuple hashed, has the following problems:
Proposed solution
We need to design/implement a new HW offload for QUIC aware RSS, where the NIC uses the connection ID (CID) to load balance instead. We should document the offload on https://github.com/microsoft/net-offloads.
Additional context
No response
The text was updated successfully, but these errors were encountered: