No worries, I think I figured it out. The idea is to have the relevant hardware e.g. storage or NIC and the respective application that writes to or reads from in the same quadrant if not possible (no cores left) then in the neighbour quadrants but definitely not in the DIAGONAL quadrant. So for...
Yes, you are right there is 8 CCDs CDD0 up to CCD7.
These CDDs are configured in couples (I think AMD calls them quadrants) where they share the I/O hub and UMC memory links so technically it should be the most efficient for the respective workloads to run in the same quadrant.
There is a performance penalty if an application runs on cores that are on e.g. two distant CCDs I reckon they also call them chiplets.
I am looking at AMD Milan 7543 32-core model. I reckon it comprises of 4x 8-core CCDs.
In the BIOS you can make all on a single NUMA0 or 2 or 4 NUMA...
I think I found the correct syntax for NMCLI
nmcli con add type ethernet con-name EthernetPF ifname ens2f0
nmcli con modify EthernetPF sriov.total-vfs 3 sriov.autoprobe-drivers false
nmcli con modify EthernetPF sriov.vfs '0 mac=00:11:22:33:44:55 vlans=10, 1 trust=true spoof-check=false'
The thing is when I use the nmcli command the new port looks different.
When I run
nmcli con show the connection created with the commands above look like this
NAME: Wired connection 2, UUID, TYPE: Ethernet, DEVICE: ens2f0v1
but with command nmcli con add type vlan con-name VLAN100 dev ens2f0...
I hope you are doing well during these a bit strange times.
I stumbled upon this issue where the only way to configure some of the settings I can do through ip set link command.
This is to do with virtual adapters with VLANs with vf and proto 802.1Q parameters.
This requires bringing...