Indicate RX checksum offload and set validation result
always as valid thus saving some CPU cycles on software validation.
Since we have authenticated encryption, we can be sure that
checksums weren't altered on the wire.
Before NetAdapterCx 2.1, checksum offload support indication
doesn't distinguish between TX and RX. This means if we want to
indicate RX checksum offload, we have to calculate checkums on TX
path, too.
Complexity of TX checksum calculation doesn't justify performace
gain, so additional Debug/Release-Win11 build configurations were created
which target NetAdapterCx 2.1 and newer. This can be used on
Windows 11 and Windows Server 2022 (kernel 10.0.20348 and newer).
Indicate RX checksum offload and set validation result always as valid thus saving some CPU cycles on software validation. Since we have authenticated encryption, we can be sure that checksums weren't altered on the wire.
Before NetAdapterCx 2.1, checksum offload support indication doesn't distinguish between TX and RX. This means if we want to indicate RX checksum offload, we have to calculate checkums on TX path, too.
Complexity of TX checksum calculation doesn't justify performace gain, so additional Debug/Release-Win11 build configurations were created which target NetAdapterCx 2.1 and newer. This can be used on Windows 11 and Windows Server 2022 (kernel 10.0.20348 and newer).
Signed-off-by: Lev Stipakov lev@openvpn.net