Minor(?) detail with OPNsense 25.1.1 and setting " vm.numa.disabled"

Started by Gary7, February 20, 2025, 02:47:42 AM

Previous topic - Next topic
OPNsense 24.7.5
This update also disables NUMA by default which can bring a boost in network throughput on affected systems. 
system: default to vm.numa.disabled=1


OPNsense 25.1.1
execute: sysctl vm.numa.disabled and the value is vm.numa.disabled: 0
I've added "vm.numa.disabled" to Tunables and verified that vm.numa.disabled="1" is in /boot/loader.conf
After reboot, the value is still vm.numa.disabled: 0

Since I have an APU2D4, I would like to explicitly disable NUMA.
Am I missing something?


An APU2D4 does not have NUMA, so there's nothing to disable.
Deciso DEC750
People who think they know everything are a great annoyance to those of us who do. (Isaac Asimov)

Setting correct sysctl/tunable policies across all hardware is so hard to pull off without noise like this.

Functionally, it's fine.


Sorry,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

Thank you for the clarification. I didn't know if the setting had any effect on a non-NUMA CPU.
I apologize for the noise.

No worries, these reports are very much appreciated. When numa isn't attached the sysctl isn't attached either so it simply complains about that.


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT