os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update some 5.2 references to 5.3, update locking description.

Browse source
This commit is contained in:
Robert Watson 2003-12-07 17:17:48 +00:00
parent 3bdfc31636
commit f6a7f48298
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=19093
1 changed files with 14 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
en/releases/5.3R/todo.sgml
View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.3R/todo.sgml,v 1.4 2003/12/07 16:34:38 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.3R/todo.sgml,v 1.5 2003/12/07 17:12:45 rwatson Exp $">
<!ENTITY title "FreeBSD 5.3 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -117,7 +117,15 @@
<td>&status.wip;</td>
<td>&a.marcel;</td>
<td>Userland bits implemented, kernel bits not implemented. Required for
5.2-RELEASE.</td>
5.3-RELEASE.</td>
</tr>
<tr>
<td>KSE support for sparc64</td>
<td>&status.wip;</td>
<td>&a.marcel;</td>
<td>Userland bits implemented, kernel bits not implemented. Required for
5.3-RELEASE.</td>
</tr>
<tr>
@ -126,12 +134,9 @@
<td>&a.sam;</td>
<td>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.</td>
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.</td>
</tr>
<tr>
@ -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.</td>
the product of a locking problem, and must be fixed for 5.3.</td>
</tr>
<tr>