Intel Chief Evangelist Comments on Linux Scheduler

ByeByeWintel writes "James Reinders is Intel's Chief Evangelist for Intel's Software Development Products. In a recent interview on Devx.com he stated: 'If I could get ONE wish fulfilled would be for OS scheduling to focus on processes, and not threads, for scheduling. And demand that processes manage their scheduling of threads ... There is a lot of opportunity for operating systems to offer these types of control in the 'running of applications' interfaces. I'd like an OS to let me specify the 'world' my application runs in (which processors, how many, etc.) These interfaces are available in Windows at run time (the task manager will let you adjust where a running task can go).'"

Comments

So do it

[QuantumG]

I hear Intel has some engineers who you could get to implement this. If you don't completely botch it, you might even get it into Linus' tree.

It's Free Software, you can add whatever you want.

Re:So do it

[teknognome]

It's elitist and arrogant when directed at a regular user, but when it's directed at some official person of a company that does contribute to Linux projects, it's a bit different.

Slashdot would be kicked out of Journalism School

[headkase]

Not only is it obvious that the submitter didn't read the article but by posting it its obvious that the 'editor' didn't either! Jebus! It's about a library template that Intel provides to developers! Linux gets a passing mention on the second page but other than that coincidence the writeup has nothing to do with the real article! And then there are people tagging the article as 'clueless' - I hope they meant the submitter because if they meant the article then ironically they would have been showing their own 'cluelessness'.
This is the first time I've felt a need to complain about /.'s integrity btw even though I've seen more articles fly-by that shouldn't have over the years.

Re:You think maybe they have other things to do?

[xenocide2]

Either way is ok, there's nothing wrong with saying "We are all about DIY, if you aren't willing to do it, don't expect other people to), you just have to recognise that is a viewpoint inconsistent with "We believe this is something everyone could and should use." There's nothing necessarily incompatible with those viewpoints. The point isn't necessarily "write it yourself," but to take ownership of the need and get it done, perhaps by paying others. You can then go about writing to others and say "You should use this stuff, and we can help make it better for your needs." Its a silly belief that other people are going to fix your problem for free if you sit there wishing loud enough. Open source projects are truly successful not when you take responsibility for listening to what people want, but allowing the public to take ownership in the software that could address their needs.