Browse thread
Raising an old issue : true concurrency in OCaml [Xavier, Damien, any]
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | Oliver Bandel <oliver@f...> |
| Subject: | Re: [Caml-list] Raising an old issue : true concurrency in OCaml [Xavier, Damien, any] |
On Thu, Apr 07, 2005 at 11:47:46PM +0200, Yoann Fabre wrote: [...] > My point is the following (let's be blatant): I'm afraid any pure-OCaml > program will be limited to at most 50% of the CPU power on about 50% of the > machines in the next five years ; and probably 25/30% on the remaining 40% > of medium to high-end machines. [...] Maybe I'm not on the right track, but do you speak about multiprocessor machines? Isn't it the job of the system kernel to provide parallelism to your application? Why should the user do coding low-level hardware-stuff in the user-space programs? This does not make sense to me. The OS should be able to hide special treatment of multiprocessor architectures or CPU-internal modifications from the user and do all this parallelism stuff transparently. On Linux for example: don't forget to compile your kernel with SMP-options and so on. So, if I've overseen something, let me know it. Ciao, Oliver