--- wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn	2015/10/27 07:15:35	1.6
+++ wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn	2018/01/18 23:11:56	1.10
@@ -22,11 +22,11 @@
   <td>TX_LOCK(spin mutex) + sc_stopping flag</td>
   <td>CORE_LOCK(spin mutex)+sc_stopping flag</td>
   <td>use CORE_LOCK(spin mutex) and TX_LOCK(spin mutex) partially</td>
-  <td>No</td>
+  <td>Yes by default. It can be changed by kernel options. See wm.4.</td>
   <td>TX and RX differently</td>
   <td>TX_LOCK(mutex) and check sc_stopping in the beginning</td>
   <td>Yes</td>
-  <td>RX only</td>
+  <td>TX and RX</td>
   <td></td>
 </tr>
 <tr>
@@ -75,14 +75,14 @@
   <td></td>
 </tr>
 <tr>
-  <th>bcm53xx_eth</th>
+  <th>bcmeth(4)</th>
   <td>in attach()</td>
   <td>lock, hwlock</td>
   <td>not taken?</td>
   <td>not taken. Set flag with atomic_or_uint() and call softintr_schedule()</td>
   <td>not taken?</td>
   <td>splnet()</td>
-  <td>Yes</td>
+  <td>Yes. The interrupt handler calls softint or workqueue depending on the load.</td>
   <td>sc_hwlock is for hard interrput. sc_lock is for software interrupt. TX and RX use the same lock</td>
   <td>callout isn't used</td>
   <td></td>