#1741: Threaded RTS must use processor affinity and processor information
----------------------------+-----------------------------------------------
Reporter: guest | Owner:
Type: task | Status: new
Priority: normal | Milestone: 6.10 branch
Component: Runtime System | Version: 6.6.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: Multiple
Os: Multiple |
----------------------------+-----------------------------------------------
Changes (by tibbe):
* cc: [EMAIL PROTECTED] (added)
Comment:
Replying to [comment:2 simonmar]:
> One problem with setting `-N` to something other than 1 by default is
that `System.Posix.forkProcess` only works with `-N1`, so if you use that
function then you need to fix `-N1` somehow (probably with a hook). I'm
not sure I want to contemplate making `forkProcess` work for larger values
of N. I suspect `forkProcess` is rare, and we might want to deprecate it
anyway. POSIX already puts pretty severe restrictions on what you can do
in the child process after `fork()` in a threaded program, so it's not
clear that we should be providing it at the Haskell level.
I really need to be able to fork in the threaded RTS to daemonize my
process. I imagine that other server programs need to do the same.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1741#comment:8>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs