![]() |
||||||
|
|
The affinity tool
The P3 update from Intel spells it out very nice So far, i've seen this happen all too often on the following motherboards (configured for smp use) abit bp6, vp6 and asus cuv4x-d, curdls The workaround is to 'bind' a device to a specific processor with a tool called the affinity tool that has been around since NT4, and can be downloaded at microsoft. As the readme in the affinity package states: "This Interrupt-Affinity Filter (IntFiltr)
allows a user to change the Using this utility, you can direct any
device's interrupts to a specific And the HowWorks tells something about the effect of the tool "As a result, lower drivers (which
use entries in this resource list when Wich means that a low-level driver will always get its information (or 'data') from one processor; thus avoiding the loss of cache coherancy. You need to copy intrfiltr.sys to /winnt/system32/drivers/ and add the registry key to start the device after boot. Next you use the GUI intfiltr.exe to configure the devices.
Click on the device (in this example a ps/2 mouse) and click on 'set mask'
Click on CPU 0 or CPU 1 to disable the dual ability of the device, click on ok, and klick on ok when the program wants to add the new information into the system. You'll see when you've added several devices that used
to lock out in 100% stress conditions to stay stable, and not lose connection Thanks to twobombs for writing this up;) |
| ||||
|
All trademarks used are properties of
their respective owners.
All rights reserved. Copyright ©2000 & 2001 by VP6-Board.com | ||||||