Add a slew of new items to the network locking todo list.
Submitted by: rwatson, glebius
This commit is contained in:
parent
bdc75acd55
commit
ff1d5c7f4e
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=26079
1 changed files with 127 additions and 1 deletions
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
|
||||
<!ENTITY base CDATA "..">
|
||||
<!ENTITY date "$FreeBSD: www/en/smp/index.sgml,v 1.156 2005/10/04 22:23:43 simon Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/smp/index.sgml,v 1.157 2005/10/18 17:12:48 jhb Exp $">
|
||||
<!ENTITY title "FreeBSD SMP Project">
|
||||
<!ENTITY email 'freebsd-smp'>
|
||||
<!ENTITY % navincludes SYSTEM "../includes.navdevelopers.sgml"> %navincludes;
|
||||
|
@ -2280,6 +2280,20 @@
|
|||
<td> 01 July 2005 </td>
|
||||
<td> &status.wip; </td>
|
||||
|
||||
<tr>
|
||||
<td> Research and select options for inbound network stack parallelism. Direct dispatch is one option currently being considered. </td>
|
||||
<td> &a.rwatson; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.wip; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Locking for polling(4). </td>
|
||||
<td> &a.pjd;, &a.glebius; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.wip; </td>
|
||||
</tr>
|
||||
|
||||
<!-- Not Started -->
|
||||
|
||||
<tr>
|
||||
|
@ -2297,6 +2311,118 @@
|
|||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Further cleanup of socket state machine in order to facilitate finishing socking locking of state transitions. </td>
|
||||
<td> &a.rwatson; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Lock KAME IPSEC. </td>
|
||||
<td> </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Only one of our ATM stacks is MPSAFE, the other two should be deleted or fixed. </td>
|
||||
<td> </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Lock ND6 (IPv6 Neighbor Discovery). </td>
|
||||
<td> &a.gnn; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Lock IPv6 multicast address lists. </td>
|
||||
<td> </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Lock IPv4 and IPv6 global address lists. </td>
|
||||
<td> </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Continued cleanup of the stack/device driver ownership and locking for struct ifnet needs to be done. Most fields are now either locked or assigned ownership. Some fields, such as if_flags, need a bit more cleanup due to device drivers modifying stack-owned fields. </td>
|
||||
<td> &a.rwatson; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> BPF locking needs some cleanup, there are some race conditions there relating to interface removal. </td>
|
||||
<td> </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> When interfaces are torn down, there are a number of races (not all associated with SMPng) that need to be thought about. </td>
|
||||
<td> </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Lock if_vlan and inter-layer multicast address manipulation and synchronization in if_vlan. </td>
|
||||
<td> &a.glebius;, &a.yar; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Further investigate locking in in_gif and in6_gif. </td>
|
||||
<td> </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> FAST_IPSEC and KAME IPSEC's PF_KEY support likely needs an asynchronous dispatch to prevent socket lock ordering issues similar to what was done for PF_ROUTE. </td>
|
||||
<td> &a.rwatson; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Investigate how to eliminate the use of ACCEPT_LOCK(), which currently prevents races in the tear-down of sockets. </td>
|
||||
<td> &a.rwatson; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Fix SMP problems with netgraph restructuring. </td>
|
||||
<td> &a.glebius; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> Verify locking in netgraph nodes and improve where necessary. </td>
|
||||
<td> &a.glebius; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td> More finely-grained locking for pf(4). </td>
|
||||
<td> &a.glebius; </td>
|
||||
<td> 19 October 2005 </td>
|
||||
<td> &status.new; </td>
|
||||
</tr>
|
||||
|
||||
</table>
|
||||
|
||||
<a name="issues"></a>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue