Friday, January 21, 2000 3:47 PM
Ian Soboroff <firstname.lastname@example.org> wrote :
> in the vast majority of cases, i suspect it's easier and probably
> better to redesign the app than redesign the scheduler. that said,
> the improvements already done are quite good and needed.
why You all speak about worse designed multithreaded apps.
Every technology bad applied is worse !
Suppose You have a rendering job to be done.
It can be subdivided in a highly parallel system with distinct threads that
can run together :
1) Viewing transformation
3) Scan conversion
6) Frame output
just to keep it simple.
Now can someone tell me why I would not split my job into threads ?
You can state that I don't have benfits in uniprocessor systems.
But I have in SMP, that is, IMHO, the future of computing technology.
You can find the needs of parallelism starting from CPUs executions units up
complex software systems up to daily work organization.
And if the OS is the bottleneck of parallelism we must try to improve it,
not to avoid multithreading.
Even if modern CPU architectures like IA64 which leave to high tuned
the work of parallelize ( I don' know if this word is correct ;) ) the code,
I think that
the software designer can do even better, or at least improve, the compiler
-- All this stuff is IMVHO
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:25 EST