#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 |
----------------------------+-----------------------------------------------
Comment (by bos):
Having `forkProcess` be broken by default would be unfortunate, I agree.
Perhaps a new link-phase option, say `-multicore`, could be added that
would both use the threaded RTS and cause `-N/k/` to be set automatically.
It could be explicitly documented as breaking `forkProcess`.
Alternatively, if there were some documented means for people to add a
little hunk of code that would set the number of capabilities and other
RTS options to use before the RTS parses them, that would do the trick.
That would also let an enterprising coder configure a system-appropriate
maximum heap size, and other such goodness. I wonder if just adding a
static initializer would be enough.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1741#comment:6>
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
