summaryrefslogtreecommitdiff
path: root/open_issues/multiprocessing.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-11-25 11:55:21 +0100
committerThomas Schwinge <thomas@schwinge.name>2010-11-25 11:55:21 +0100
commit1e67a761cbfa94a69cec2f5709d23d7983cd0fc1 (patch)
tree0ae6ccf8bc14c0d171cff97c94de6a28c8b417d0 /open_issues/multiprocessing.mdwn
parent31a442c4b59c41eb6aa15b6a66af93955b302c62 (diff)
Talk about advantages, challenges, how many developers, why so few developers.
Diffstat (limited to 'open_issues/multiprocessing.mdwn')
-rw-r--r--open_issues/multiprocessing.mdwn18
1 files changed, 9 insertions, 9 deletions
diff --git a/open_issues/multiprocessing.mdwn b/open_issues/multiprocessing.mdwn
index 7b4f2611..224c0826 100644
--- a/open_issues/multiprocessing.mdwn
+++ b/open_issues/multiprocessing.mdwn
@@ -11,7 +11,7 @@ License|/fdl]]."]]"""]]
[[!tag open_issue_hurd]]
We would expect that fine-grained, compartmentalized systems, that is,
-microkernel-based multi-server systems in particular, would be ideal condidates
+microkernel-based multi-server systems in particular, would be ideal candidates
for applying multiprocessing. That is, however, only true from a first and
inexperienced point of view: there are many difficulties.
@@ -19,14 +19,14 @@ inexperienced point of view: there are many difficulties.
IRC, #hurd, August / September 2010
<marcusb> silver_hook: because multi-server systems depend on inter-process
- communication, and inter-process communication is many times more expensive
- across cpus
- <marcusb> silver_hook: so you either force interrelated work on the same cpu,
- or suffer heavy penalties. and in a typical fine-grained object system, all
- objects are interconnected!
- <marcusb> silver_hook: resources in today's systems, even in a single node with
- one cpu, but more so in a network, are very non-uniform. scheduling these
- resources efficiently is a huge problem. restricting the resource
+ communication, and inter-process communication is many times more
+ expensive across cpus
+ <marcusb> silver_hook: so you either force interrelated work on the same
+ cpu, or suffer heavy penalties. and in a typical fine-grained object
+ system, all objects are interconnected!
+ <marcusb> silver_hook: resources in today's systems, even in a single node
+ with one cpu, but more so in a network, are very non-uniform. scheduling
+ these resources efficiently is a huge problem. restricting the resource
distribution policies in the way microkernel systems tend to do is posing
serious research challenges