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

Remove the netisr max queue depth item at the request of the maintainer.

Browse source
This commit is contained in:
Scott Long 2004-09-17 18:20:00 +00:00
parent debe3f1ef6
commit ee4f439e24
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=22389
1 changed files with 1 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
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.78 2004/09/16 20:28:05 ru Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.3R/todo.sgml,v 1.79 2004/09/17 18:18:43 blackend Exp $">
<!ENTITY title "FreeBSD 5.3 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
@ -562,21 +562,6 @@
complete local<->remote delivery without grabbing Giant.</td>
</tr>
<tr>
<td>Increased and configurable netisr queue max depth for routing
sockets</td>
<td>&status.untested;</td>
<td>&a.rwatson;</td>
<td>As part of the MPSAFE network stack work, delivery of routing socket
messages was moved to queued dispatch via netisr rather than direct
dispatch from the routing code. However, the risks of lost routing
messages for routing daemons are high; respond by increasing the max
depth beyond a default interface max depth of 50 to 128, and allow it
to be user-configured. This change is now present in CVS HEAD and
RELENG_5.</td>
</tr>
<tr>
<td>kld support for amd64</td>
<td>&status.untested;</td>