Warning, error found in article optimisations.
Original text:
Code: Select all
NV_FAH_CPU_AFFINITY is used to set the affinity of the core. It is not normally set up, unless you have trouble with program conflicts (performance degraded by sharing a CPU core with another program). Acceptable values are 0 to 15 (numerical values) ... this is actually a binary mask such that each bit represents a CPU: CPU3, CPU2, CPU1, CPU0. A value of 1 allows access to the CPU in question, and a value of 0 prohibits access. A numeric value 0 is the default: it allows access to all cores, letting Windows manage affinities, or it locks all the cores on the latest CPU, the following option enabled in the advanced settings of the client. If you use this variable in a custom configuration, it is recommended to enable the client option "do not lock cores to specific CPU" in the configuration.
I think this is auto translated,
A numeric value 0 is the default: it allows access to all cores, letting Windows manage affinities, or it locks all the cores on the latest CPU, the following option enabled in the advanced settings of the client.
It's also wrong ( if I understand the entire sentence correctly ).
First off all, the gpu client with locked affinities using built in options do not all use core3 on a quad, the first gpu client uses core3, the second core2 and I imagine this goes on like core1, core0, core3, core2 ect.
It's dynamic, not staticly bound to the last core.
Merci FAH-Addict!
) ... so please report them if you catch one.