William Lee Irwin III <[EMAIL PROTECTED]> asks about true SMP
>> cmpxchg and then taking a blocking lock sounds like the 2-tier locking
>> supported with Linux' new futex system calls. I wonder how they chose
>> to block in the older GHC RTS.
On Mon, Oct 13, 2003 at 12:02:52PM -0400, Jan-Willem Ma
William Lee Irwin III <[EMAIL PROTECTED]> asks about true SMP
haskell.
> On Mon, Oct 13, 2003 at 11:13:56AM +0200, Wolfgang Thaller wrote:
> > The reason why we currently do not take advantage of SMP is that the
> > Haskell Heap is a shared data structure which is modified whenever a
> > thunk (a
Apologies if you receive multiple copies of this message.
**
*** Fourth Workshop on ***
***Language Descriptions, Tools and Applications ***
*** LDTA 2004
On Mon, 13 Oct 2003, Wolfgang Thaller wrote:
> > Do you have some experience or knowledge about Parallel Haskell? And
Parallel Haskell runs, but there are problems. Unless someone has slipped
something past me, there is no parallel implementation for Release 6 yet,
so if you want to tinker w
TPLP Special Issue on
Specification, Analysis and Verification of Reactive Systems
http://www.cs.utwente.nl/~etalle/specialissue.html
Motivations and Goals
The huge increase in interconnectivity we have witnessed in the last
decade h
Hello,
just as an addition to the discussion (one week ago or so) about Haskell
being defined as a non-strict rather than lazy language: in that context
it struck me as odd that Section 6.2 of the Report says `seq` is used to
avoid "unneeded laziness". The only other uses of "lazy" seem to appear
Do you have some experience or knowledge about Parallel Haskell? And
what you mentioned in you previous email is all about Concurrent
Haskell
or about the both?
Everything I said was about Concurrent Haskell. I have no experience
with Parallel Haskell. All the binaries available on the GHC web pa
Wolfgang,
According to the User Guide of GHC 6.1 that GHC supports both Concurrent
Haskell and Parallel Haskell. And Concurrent Haskell and Parallel
Haskell have very different purpose.
To my understanding about the document and your reply, it's Concurrent
Haskell who uses Threads to process task
William Lee Irwin III wrote:
>> That's a painful-sounding state of affairs, though not entirely
>> unexpected. It would be interesting to hear of "BKL breakup" efforts
>> for Haskell runtime systems, though anymore I'm totally ignorant of
>> what the devil is going on in userspace except database-o
William Lee Irwin III wrote:
On Sat, Oct 11, 2003 at 10:58:04PM +0200, Wolfgang Thaller wrote:
You should also note that no Haskell implementation currently supports
SMP; even when multiple kernel threads are used, there is a mutual
exclusion lock on the Haskell heap, so a multithreaded Haskell pr
On Sat, Oct 11, 2003 at 10:58:04PM +0200, Wolfgang Thaller wrote:
> If you compile the bleeding-edge GHC from the CVS HEAD, you'll get
> something else; while "most" threads (those created using "forkIO") are
> still light-weight threads that are scheduled in just one kernel
> thread, you can al
11 matches
Mail list logo
