Support Center > Search Results > SecureKnowledge Details
Although CoreXL Affinity was configured to assign only a specific process to certain CPU cores, some interfaces are still being assigned to those CPU cores
Symptoms

  • Although CoreXL Affinity was configured to assign only a specific process to certain CPU cores, some interfaces are still being assigned to those CPU cores.

    Example:

    • The process "temain" was assigned to CPU 2 and CPU 3 in the $FWDIR/conf/fwaffinity.conf file (either manually, or by running the "fw ctl affinity -s -n <process_name> <cpu ids>" command):

      n temain 3 2

    • Output of "fw ctl affinity -l -r -v" command shows that some interfaces are also assigned to CPU 2 and CPU 3:

      [Expert@HostName:0]# fw ctl affinity -l -r -v
CPU 0:  eth2 (irq 83)
CPU 1:  eth3 (irq 59)
CPU 2:  eth1 (irq 75)
        temain
CPU 3:  eth0 (irq 67)
        temain
CPU 4:  fw_3
CPU 5:  fw_2
CPU 6:  fw_1
CPU 7:  fw_0
All:    in.geod in.msd fwd rad mpdaemon usrchkd vpnd in.acapd cpd cprid

    • Output of "$FWDIR/scripts/fwaffinity_used_cpus" script returns a list of CPU cores that are considered as "available to handle IRQs", which contains CPU 2 and CPU 3:

      2
3
4
5
6
7
  • This issue will not happen if manual sim affinity is used
Cause

This issue occur on certain machines with a license limiting the number of CPU cores that can be used to a number less than the number of CPU cores on the machine.


Solution
 Note: To view this solution you need to Sign In .