Last Modified: Sep 13, 2023
Opened: Jun 13, 2022 Severity: 4-Minor
This may not impact performance in the tenant, but for tenant builds without this fix, upon initial deployment, the control plane will not be pinned correctly (should be pinned to odd-numbered cpus). Note: This pinning is inside the tenant virtual machine, not in the F5OS host. The datapath (TMM) will still be pinned correctly.
The datapath (TMM) threads run at elevated priority anyway, so would be protected from the control plane threads.
The BIG-IP tenant without this fix is initially deployed.
If this is bothersome, redeploy the tenant, and the problem will not reoccur.
Tenant platform determination no longer depends on a file that is not there on initial startup. The dmidecode utility is used instead.