Merge branch 'master' of braunbox:~hurd-web/hurd-web

5 files changed, 12 insertions, 6 deletions

diff --git a/open_issues/address_space_memory_mapping_entries.mdwn b/open_issues/address_space_memory_mapping_entries.mdwn
index caf447dd..10494cc5 100644
--- a/open_issues/address_space_memory_mapping_entries.mdwn
+++ b/open_issues/address_space_memory_mapping_entries.mdwn
@@ -17,3 +17,5 @@ IRC, freenode, #hurd, 2011-05-07
       linked list
     <braunr> a bare linked list
     <braunr> which makes faults and page cache lookups even slower
+
+A red-black tree was added to VM maps to speed up lookups.
diff --git a/open_issues/alarm_setitimer.mdwn b/open_issues/alarm_setitimer.mdwn
index 5999808c..a1c8a7d3 100644
--- a/open_issues/alarm_setitimer.mdwn
+++ b/open_issues/alarm_setitimer.mdwn
@@ -22,6 +22,7 @@ for a signal, while on GNU/Hurd it gets a new alarm and exits.
 
 [[alrm.c]]
 
+This issue was recently fixed (around January 2013).
 
 # IRC, freenode, #hurd, 2012-07-29
 
diff --git a/open_issues/anatomy_of_a_hurd_system.mdwn b/open_issues/anatomy_of_a_hurd_system.mdwn
index 3e585876..a461d71b 100644
--- a/open_issues/anatomy_of_a_hurd_system.mdwn
+++ b/open_issues/anatomy_of_a_hurd_system.mdwn
@@ -173,6 +173,9 @@ Need more stuff like that.
     <abique> is it M:N ?
     <youpi> libthreads, actually
     <youpi> yes
+
+Actually, the Hurd has never used an M:N model. Both libthreads (cthreads) and libpthread use an 1:1 model.
+
     <abique> nice
     <abique> is the task scheduler in the kernel ?
     <youpi> the kernel thread scheduler, yes, of course
diff --git a/open_issues/benefits_of_a_native_hurd_implementation.mdwn b/open_issues/benefits_of_a_native_hurd_implementation.mdwn
index afdcfb73..12201f51 100644
--- a/open_issues/benefits_of_a_native_hurd_implementation.mdwn
+++ b/open_issues/benefits_of_a_native_hurd_implementation.mdwn
@@ -120,6 +120,12 @@ IRC, #hurd, 2010-12-28
     [...]
     <braunr> kilobug: right, a monolithick kernel is less folt-tolerant than a
       well designed/implemented microkernel based os
+
+It turns out that it is perfectly possible to isolate services running in the
+same address space, as it was done in projects such as Singularity, the idea
+being that the code is verified through static analysis when installed (but
+this requires a language other than C).
+
     <kilobug> braunr: well, the Hurd is buggy nowadays, but things like an
       ext2fs translator doing a segfault and being restarted is a
       fault-tolerance that would be almost impossible to have in Linux
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