WinAFC: A new affinity changer

[baobab13]

Now some results:-

C:\FAH\FahCore_*.exe := PAIR0 [assign=2,resource=CPUUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\FAH2\FahCore_*.exe := PAIR1 [assign=2,resource=CPUUSE,policy=PSEUDOBALANCED,pri ority=idle]
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU*\Fahcore_*.exe := ALL [priority=belownormal]

OC, just another note to say that these rules are equivalent to the ones that you used before.

PAIR0 is a shorthand for writing PAIR0::CPU0 + PAIR0::CPU1 (2 CPUs in total).
For the sake of generality let's assume you specify the 'assign' attribute with a value of N and you have M CPUs in the CPU mask.

If N = M, you tell the program to assign all CPUs listed in the CPU mask to all matching processes. In this case the attributes 'resource' and 'policy' are ignored. If N = M, the program does not have to compute resource consumption for matching processes, does not sort the processes by said resource consumption, and does not have to allocate the cores using some fancy policy.
The program just sets the affinity mask of all matching processes to include all CPUs listed in the CPU mask.

So those rules are equivalent to just saying:

C:\FAH\FahCore_*.exe := PAIR0 [priority=idle]						
C:\FAH2\FahCore_*.exe := PAIR1 [priority=idle]						
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU*\Fahcore_*.exe := ALL [priority=belownormal]

Attributes 'resource' and 'policy' are meaningful only when N < M. Note that N cannot be greater than M.

Edit: If you want to test a different config, I would test this one:

C:\FAH\FahCore_*.exe := PAIR0 [assign=1,resource=CPUUSE,policy=PSEUDOBALANCED,priority=idle]
C:\FAH2\FahCore_*.exe := PAIR1 [assign=1,resource=CPUUSE,policy=PSEUDOBALANCED,priority=idle]
C:\Documents and Settings\MIKE\Application Data\Folding@home-GPU*\Fahcore_*.exe := PAIR0::CPU1+PAIR1::CPU1 [priority=belownormal]

If your OS is XP and not Vista, then I recommend replacing resource=cpuuse with resource=memuse for both SMP profiles.