I wrote a compiler mothafucka -- we are different species.
LoseThos is Identity Mapped and multitasking. My compiler calls MALLOC for memory and puts the code there. My scheduler saves regs and loads-in the next set of regs. What's hard about this? You got your head up your ass with Linux on the brain. Ba ha. Imagine China inventing something!!
LoseThos is master-slave multicore. Core 0 can farm-out jobs to other cores. Sure other cores can have multiple task. The scheduler never shuffles them around. Fucken monkeys -- why would you do SMP? Mine's got locks for file access from all cores, but it's not SMP.
Blue-eyed monkeys are still monkeys. Some people are morons who will never understand originality. The fuck you thinking doing SMP? That's retarded and you've been caught plagarizing shit nobody in their right mind would do! Cores should be heterogeneous in hardware, too -- it's obvious.
Satan and Santorum. I'm playing to impress God, not man.
God says... classics giveth brightness curiosity liveth Tobias obedience net certainly serve distances decked daemon dreaded dens temporately Firmament necessary elders don't_even_think_about_it hold_on_a_minute captive murmured earthly I_quit watery pronouncing PRINT unruly
Just think about heterogeneous CPU's. You could have the other cores being like something out of a GPU. I think I'd rather have 100 floating point units than 4 cores. A few identical cores are good, but a bunch of little ones in addition to a few sounds better.
For servers you can benefit from SMP but on a home system master/slave.