hurd/faq/smp: Add some more links, and rationale.

1 files changed, 10 insertions, 2 deletions

diff --git a/hurd/faq/smp.mdwn b/hurd/faq/smp.mdwn
index e48b6b66..af748454 100644
--- a/hurd/faq/smp.mdwn
+++ b/hurd/faq/smp.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2009, 2011 Free Software Foundation, Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
 id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -12,6 +12,14 @@ License|/fdl]]."]]"""]]
 
 The Hurd servers themselves are multithreaded, so they should be able to take benefit of the parallelism brought by SMP/Multicore boxes. This has however never been tested yet because of the following.
 
-Mach used to be running on SMP boxes like the [[http://en.wikipedia.org/wiki/Intel_iPSC/860 | iPSC 860]], so has an infrastructure for running on them.  It has however not (yet) been ported to nowadays' SMP standards like ACPI etc.  The plan is to try Xen SMP support first.
+[[microkernel/Mach]] used to be running on SMP boxes like the [[!wikipedia
+Intel_iPSC/860]], so principally has the required infrastructure.  It has
+however not yet been enhanced to support nowadays' SMP standards like ACPI,
+etc.  Also, [[GNU Mach|microkernel/mach/gnumach]]'s Linux device driver glue
+code likely isn't SMP-safe.  As this glue code layer is not used in the
+[[microkernel/mach/gnumach/ports/Xen]] port of GNU Mach, the plan is to try it
+in this enviroment first.
+
+[[!tag open_issue_gnumach open_issue_xen]]
 
 That is why for now GNU/Hurd will only uses one logical processor (i.e. one core or one thread, depending on the socket type).