Quote from nitro:
http://lambcutlet.org/gallery/Tyan_S4880
can't wait 'till it actually comes out.
nitro
![]()
Corvus,Quote from corvus:
Can you imagine the heat that thing puts out fully loaded?
Quote from nitro:
Corvus,
Are you an expert on the following?
Say you have a Quad machine, or even a dual. I want to tell Windows to run the TCP/IP stack on one CPU and to never context switch anything onto that CPU, in other words, I want to set the affinity of the TCP/IP stack to a particular CPU (probably CPU 0).
Do you know if this is a smart thing to do? I can do it in the Task Manager, but I am not sure if it is a smart thing to do.
My guess is that this is a smart thing to do if you have a >= QUAD machine, but not so smart on a dual.
Second part of my question is: Assuming it is a smart thing to do, what about raising the Base Prioity of the TCP/IP stack from the default of "normal" to "high" or even "realtime" ?

Hmmmm,Quote from weewilly:
i think you're not supposed to use cpu affinity for processes that share interrupts. i think you can starve service requests for other processes in that event. check out this info on imagecfg.exe:
http://www.jsiinc.com/subh/tip3500/rh3542.htm
wee
Hmmm,Quote from corvus:
My guess is that interrupt handling would always take place on the 0 CPU, regardless, but I don't know for sure...I have not had the luxury of this problem.
I also wouldn't raise the priority of anything to realtime...that allows you to DoS yourself. Nor would I raise the stack priority above normal for TCP/IP, because TCP/IP I/O is an activity filled with a world of waiting on the network hardware and the other half of the channel. Let the other processes that are actively chomping on stuff in memory run.