#1741: Threaded RTS must use processor affinity and processor information
----------------------------+-----------------------------------------------
Reporter: guest | Owner:
Type: task | Status: new
Priority: normal | Milestone: 6.8 branch
Component: Runtime System | Version: 6.6.1
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Testcase: | Architecture: Multiple
Os: Multiple |
----------------------------+-----------------------------------------------
Comment (by guest):
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.
Does anyone have opinion about it?
I think that if someone want to use -threaded option, he want to use more
than 2-core normally. So setting -N to 1 by default isn't good solution.
I think that writing about this problem on Haddock
System.Posix.forkProcess document, and then deprecating `forkProcess` is
better solution. Because if someone can't find `forkProcess` problem in
document, he cann't decide to use `forkProcess` or not. His program works
well with default -N1, but he suddenly encounts problem when setting
option -N to parallelize his program. That isn't good.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1741#comment:3>
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
