News for hackers. Stuff that matters.
Re:Forcing the CPU affinity can make a monothreaded process ... by drudru11 on Sunday December 09, 2012 @06:13PM (#4896591)
Sigh.

SGI had this in Ultrix in 1991-1992ish (maybe earlier).

Why? Their market was graphics. If anything non-essential prevented the system from rendering a frame, an attempt was made to run that on another processor.

I remember a 4 processor reality engine^2 that had four processors. 1 processor was dedicated to graphics. another to networking. I don't recall what the other 2 were for.

Re:Forcing the CPU affinity can make a monothreaded process ... by reeses on Sunday December 09, 2012 @09:17PM (#4897111)
SGI = IRIX, DEC = Ultrix

What you're thinking of is different from task/processor/thread affinity.

Regarding SGI, I'm guessing you're thinking about the Onyx, which would have put it about 1993+. The R4x00s that were in the machine were not powerful enough to drive the RE2 and IR boards on a shared basis. The scheduler on many of these machines (Ultrix and IRIX both, along with Unicos, etc.) all pretty much sucked at the time, with AIX being a notable exception in some environments, especially running under VM.

You still see dedicated task processors with the z-series and maybe i as well today.