| Either this is bad journalism or the "architect" is really high. Because proposed re-architecture makes absolutely no sense. The article starts with an obvious observation, being that scheduling (in its largest meaning) often is crap in real (Windows?) systems. It concludes with complete meaningless bullshit where applications, now renamed, would have a dedicated CPU. What the point? Doing hard real-time? What does that even concretely means for "runtimes" of have a "dedicated" CPU (wich, given the complexity of modern architectures, would not really be in a strict fashion) and to do resource management thanks to metadata inserted by the compiler? What is really needed is more effective ways for applications to sends tips to the kernel about what is going on, what should run at high priority, what should be cached, what should not be, and so over. Forbidding some programs to use some cores because you have many makes little sense as a way to re-architecture an operating system. Because it already happens anyway on current designs (not really forbidden, but when you have few services consuming less than 1 percent of 1 core in the background, and/or running with extremely low priority they will be near to unnoticeable, and truly unnoticeable from the point of view of the user). To get a responsive word processor no matter an anti-virus is loaded or not, a simple solution can work really well now; priorities of scheduling. Given that really background priorities are among the rare things that works fairly well under windows (like 10x better than with a vanilla Linux kernel), if the "architect" is experiencing random slow down of Word because of his "antivirus", its because his "antivirus" is total utter crap, not because a new "architecture" of OS is needed. |