You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The up4.bess script uses the utils.py to set processor affinity for all processes running on the system. An issue can arise if the script is run a second time, as the parent of whatever called the script has had its own affinity rules modified.
For example, given a CPU set of [0-7] cores, and I am in an interactive shell where I can execute bessctl.
It then uses that to carve out as many CPUs as workers needed. Given 1 worker, this means the CPU affinity set is [1-7]. It then sets that mask on every process, including itself.
On second run, when it asks for the current process's affinity list, it will receive [1-7], and will reduce that by one, leaving [2-7] as the new mask to set for every process it can.
The text was updated successfully, but these errors were encountered:
The
up4.bess
script uses theutils.py
to set processor affinity for all processes running on the system. An issue can arise if the script is run a second time, as the parent of whatever called the script has had its own affinity rules modified.For example, given a CPU set of
[0-7]
cores, and I am in an interactive shell where I can execute bessctl.On the first run, it gets the current process's affinity list: https://github.com/omec-project/upf/blob/master/conf/utils.py#L131 This would result in
[0-7]
cores being available.It then uses that to carve out as many CPUs as workers needed. Given 1 worker, this means the CPU affinity set is [1-7]. It then sets that mask on every process, including itself.
On second run, when it asks for the current process's affinity list, it will receive
[1-7]
, and will reduce that by one, leaving[2-7]
as the new mask to set for every process it can.The text was updated successfully, but these errors were encountered: