diff options
| author | https://www.google.com/accounts/o8/id?id=AItOawlyLVajq_XluZ1wvTunv9vbM_kx1H0nd6Q <Richard@web> | 2013-03-16 22:44:12 +0100 |
|---|---|---|
| committer | GNU Hurd web pages engine <web-hurd@gnu.org> | 2013-03-16 22:44:12 +0100 |
| commit | 11d3902442d767e7e228c2c660cc7af01042bab7 (patch) | |
| tree | 6d45536b3f4986e74a6c93e6672c712016b98987 /open_issues/multiprocessing.mdwn | |
| parent | 6e9a7901223e4de14e3c953be177e6f26a3d03d3 (diff) | |
Remove an erroneous comment about DragonFlyBSD threading
Diffstat (limited to 'open_issues/multiprocessing.mdwn')
| -rw-r--r-- | open_issues/multiprocessing.mdwn | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/open_issues/multiprocessing.mdwn b/open_issues/multiprocessing.mdwn index 562ccd83..e420610e 100644 --- a/open_issues/multiprocessing.mdwn +++ b/open_issues/multiprocessing.mdwn @@ -54,12 +54,6 @@ IRC, freenode, #hurd, 2011-07-26 < braunr> thread migration already takes into account smt, cores, and numa < braunr> it's hard to do something better < braunr> (here, thread migration means being dispatched on another cpu) - < braunr> some systems like dragonflybsd go as far as to pin threads on one - processor for their entire lifetime - < braunr> in order to have rcu-like locking almost everywhere - < braunr> (you could argue it's less efficient since in the worst case - everything runs on the same cpu, but it's very unlikely, and in practice - most patterns are well balanced) debian-hurd list |