Move routing socket queue depth item from show stopper to testing,
since the queue depth may now be configured using the tunable/ sysctl net.route.netisr_maxqlen.
This commit is contained in:
parent
c1ec14ba78
commit
127609e00a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=22216
1 changed files with 16 additions and 16 deletions
|
@ -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.61 2004/09/02 16:48:17 kensmith Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/releases/5.3R/todo.sgml,v 1.62 2004/09/03 03:21:23 scottl Exp $">
|
||||
<!ENTITY title "FreeBSD 5.3 Open Issues">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
|
||||
|
@ -172,21 +172,6 @@
|
|||
<td>Synaptics updates to the psm(4) driver have resulted in poor
|
||||
interactivity for taps and button press events for some users.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Increased and configurable netisr queue max depth for routing
|
||||
sockets</td>
|
||||
<td>&status.wip;</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 in CVS HEAD, and needs to be
|
||||
merged to RELENG_5 after testing.</td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
<h3>Desired features for 5.3-RELEASE</h3>
|
||||
|
@ -561,6 +546,21 @@
|
|||
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>
|
||||
|
||||
</table>
|
||||
|
||||
&footer;
|
||||
|
|
Loading…
Reference in a new issue