Page MenuHomeFreeBSD

make lacp's use_numa hashing aware of send tags
ClosedPublic

Authored by gallatin on Feb 23 2020, 9:27 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Feb 11, 12:16 PM
Unknown Object (File)
Sun, Feb 9, 1:14 AM
Unknown Object (File)
Wed, Jan 29, 3:15 PM
Unknown Object (File)
Wed, Jan 22, 3:27 PM
Unknown Object (File)
Dec 29 2024, 7:16 AM
Unknown Object (File)
Dec 25 2024, 12:04 AM
Unknown Object (File)
Oct 30 2024, 2:05 AM
Unknown Object (File)
Sep 30 2024, 9:00 PM
Subscribers

Details

Reviewers
hselasky
jhb
rrs
Group Reviewers
transport
Summary

When I did the use_numa support, I missed the fact that there is a separate hash function for send tag nic selection. So when use_numa is enabled, ktls offload does not work properly, as it dos not reliably allocate a send tag on the proper egress nic since different egress nics are selected for send-tag allocation and packet transmit. To fix this, this change:

  • refectors lacp_select_tx_port_by_hash() and lacp_select_tx_port() to make lacp_select_tx_port_by_hash() always called by lacp_select_tx_port()
  • pre-shifts flowids to convert them to hashes when calling lacp_select_tx_port_by_hash()
  • add a numa_domain field to if_snd_tag_alloc_params
  • plumb the numa domain into places where we allocate send tags

In testing with NIC TLS setup on a NUMA machine, I see thousands of output errors before the patch when enabling kern.ipc.tls.ifnet.permitted=1. After the change, I see no errors, and I see the NIC sysctl counters showing active TLS offload sessions.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 29561