Linked by Thom Holwerda on Wed 25th Jul 2007 13:48 UTC, submitted by Moochman
Thread beginning with comment 258132
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Their marketing material almost implies that the library itself goes through the trouble of implementing yet another scheduler in addition to the one the OS already has.
Ohhh, another M:N threading model. When are they going to learn that userspace thread scheduling just doesn't perform very well? Why can't they just split the process into threads and let the kernel schedule them?
Ohhh, another M:N threading model. When are they going to learn that userspace thread scheduling just doesn't perform very well? Why can't they just split the process into threads and let the kernel schedule them?
How so? M:N threading is complex to implement, but when done right, it can out perform the competition. Take Tru64 for instance, which uses M:N threading.
Its one of those things in the IT world, great on paper, a real bitch to implement in real life, but when done well, does perform well.






Member since:
2006-01-06
I'm not sure what you mean.
Intel currently sells their compiler for $$$. It's not a bad compiler. I'm not sure it would be to their advantage to open source.
Their compiler is optimized for their cpus and the x86 market isn't just a one horse race, although generally amd cpus also get a boost from the intel compiler.
From a cross platform/cross system standpoint gcc is still the best compiler out there, supporting generally well many different architectures and OS's.
One thing REALLY annoying about this library is that there's plenty of access to a bunch of marketing fluff, but you have to go through the mess of downloading the code in order to look at any examples. I'd like to see some hard core simple examples of how to use their stuff. Their marketing material almost implies that the library itself goes through the trouble of implementing yet another scheduler in addition to the one the OS already has.
Edited 2007-07-25 16:39 UTC