In D53100#1214836, @gallatin wrote:

In D53100#1214833, @akiyano_amazon.com wrote:

I built and installed the latest kernel with this patchset in AWS and ran a network sanity check with iperf and all looks good.

turned on net.inet.tcp.input_verify_hash with sysctl net.inet.tcp.input_verify_hash=1

ran traffic

lookede at

sysctl net.inet.tcp.input_nohash
sysctl net.inet.tcp.input_badhash

and both were 0

no prints to dmesg

commit lgtm.

Thank you so much for quick and complete testing. Much appreciated!

I built and installed the latest kernel with this patchset in AWS and ran a network sanity check with iperf and all looks good.

Thank you for submitting this patch.
Can you please provide a commit message that explains this change.
For example questions that immediately arise:

1. What "newly exposed RSS hash key API" you are talking about (link to the commits that added this API)?
2. Why it is ok to remove the #ifdef RSS?
3. Why do you also remove the #ifdef RSS in ena_datapath.c?
4. How did you test the change?

Added default: clause to switch to handle case of illegal values set to force_large_llq_header

Fixed comments by cperciva@ I got via mail, since I accidentally turned comments off here:

Fixed comments by cperciva@ that I got via email since I blocked accidentally comments here