From f6a7f48298721801b1430d6490cfa723b7ffebcb Mon Sep 17 00:00:00 2001 From: Robert Watson Date: Sun, 7 Dec 2003 17:17:48 +0000 Subject: [PATCH] Update some 5.2 references to 5.3, update locking description. --- en/releases/5.3R/todo.sgml | 23 ++++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-) diff --git a/en/releases/5.3R/todo.sgml b/en/releases/5.3R/todo.sgml index a4012362cf..78114feca5 100644 --- a/en/releases/5.3R/todo.sgml +++ b/en/releases/5.3R/todo.sgml @@ -1,7 +1,7 @@ - + %includes; %developers; @@ -117,7 +117,15 @@ &status.wip; &a.marcel; Userland bits implemented, kernel bits not implemented. Required for - 5.2-RELEASE. + 5.3-RELEASE. + + + + KSE support for sparc64 + &status.wip; + &a.marcel; + Userland bits implemented, kernel bits not implemented. Required for + 5.3-RELEASE. @@ -126,12 +134,9 @@ &a.sam; Significant parts of the network stack (especially IPv4 and IPv6) now have fine-grained locking of their data structures. - However, it is not yet possible for the netisr threads to run - without Giant, due to dependencies on sockets, routing, etc. - A 5.2-RELEASE goal is to have the network stack running largely - without Giant, which should substantially improve performance - of the stack, as well as other system components by reducing - contention on Giant. + By 5.3-RELEASE, it is necessary to have the vast majority of + network code running without Giant, including sockets, permitting + complete local<->remote delivery without grabbing Giant. @@ -144,7 +149,7 @@ developer, but also because it's an instability that could show up under other high load and heavy use of KQueues. See PR kern/57945 for a proposed patch and details. This appear to be - the product of a locking problem, and must be fixed for 5.2. + the product of a locking problem, and must be fixed for 5.3.