From 11d3902442d767e7e228c2c660cc7af01042bab7 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlyLVajq_XluZ1wvTunv9vbM_kx1H0nd6Q" Date: Sat, 16 Mar 2013 22:44:12 +0100 Subject: Remove an erroneous comment about DragonFlyBSD threading --- open_issues/multiprocessing.mdwn | 6 ------ 1 file changed, 6 deletions(-) (limited to 'open_issues') 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 -- cgit v1.2.3 From 879372ff8a5a5ffbb9150c5250acb87fb552c48f Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlyLVajq_XluZ1wvTunv9vbM_kx1H0nd6Q" Date: Sun, 17 Mar 2013 00:48:39 +0100 Subject: --- open_issues/address_space_memory_mapping_entries.mdwn | 2 ++ 1 file changed, 2 insertions(+) (limited to 'open_issues') 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 a bare linked list which makes faults and page cache lookups even slower + +A red-black tree was added to VM maps to speed up lookups. -- cgit v1.2.3 From 8144abc77f808f66f477499d22d375a9b7c32d39 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlyLVajq_XluZ1wvTunv9vbM_kx1H0nd6Q" Date: Sun, 17 Mar 2013 00:54:33 +0100 Subject: Mention that setitimer is fixed --- open_issues/alarm_setitimer.mdwn | 1 + 1 file changed, 1 insertion(+) (limited to 'open_issues') 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 -- cgit v1.2.3 From 025dac132f2da52e7a83429b5bcf7e879bb10f0d Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlyLVajq_XluZ1wvTunv9vbM_kx1H0nd6Q" Date: Sun, 17 Mar 2013 00:59:53 +0100 Subject: Correct a confusing statement about the threading model --- open_issues/anatomy_of_a_hurd_system.mdwn | 3 +++ 1 file changed, 3 insertions(+) (limited to 'open_issues') 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. is it M:N ? libthreads, actually yes + +Actually, the Hurd has never used an M:N model. Both libthreads (cthreads) and libpthread use an 1:1 model. + nice is the task scheduler in the kernel ? the kernel thread scheduler, yes, of course -- cgit v1.2.3 From 4fb182a18e7a7e7e6ff7e5a128459c05a61de188 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlyLVajq_XluZ1wvTunv9vbM_kx1H0nd6Q" Date: Sun, 17 Mar 2013 01:20:31 +0100 Subject: Add a reference to Singularity showing safe address space sharing --- open_issues/benefits_of_a_native_hurd_implementation.mdwn | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'open_issues') 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 [...] 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). + 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 -- cgit v1.2.3