diff options
Diffstat (limited to 'static/netbsd/man4/wm.4 4.html')
| -rw-r--r-- | static/netbsd/man4/wm.4 4.html | 179 |
1 files changed, 0 insertions, 179 deletions
diff --git a/static/netbsd/man4/wm.4 4.html b/static/netbsd/man4/wm.4 4.html deleted file mode 100644 index 0b887e5e..00000000 --- a/static/netbsd/man4/wm.4 4.html +++ /dev/null @@ -1,179 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">WM(4)</td> - <td class="head-vol">Device Drivers Manual</td> - <td class="head-rtitle">WM(4)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">wm</code> — <span class="Nd">Intel i8254x - Gigabit Ethernet driver</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<p class="Pp"><code class="Cd">wm* at pci? dev ? function ?</code></p> -<p class="Pp"> - <br/> - <code class="Cd">options WM_RX_PROCESS_LIMIT_DEFAULT</code> - <br/> - <code class="Cd">options WM_RX_INTR_PROCESS_LIMIT_DEFAULT</code></p> -<p class="Pp">Configuration of PHYs may also be necessary. See - <a class="Xr">mii(4)</a>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">The <code class="Nm">wm</code> device driver supports Gigabit - Ethernet interfaces based on the Intel i8254x family of Gigabit Ethernet - chips. The interfaces supported by the <code class="Nm">wm</code> driver - include:</p> -<ul class="Bl-bullet"> - <li>Intel i82542 1000BASE-X Ethernet</li> - <li>Intel i82543GC 1000BASE-X Ethernet</li> - <li>Intel i82543GC 1000BASE-T Ethernet</li> - <li>Intel i82544EI 1000BASE-T Ethernet</li> - <li>Intel i82544EI 1000BASE-X Ethernet</li> - <li>Intel i82544GC 1000BASE-T Ethernet</li> - <li>Intel i82544GC (LOM) 1000BASE-T Ethernet</li> - <li>Intel i82540EM 1000BASE-T Ethernet</li> - <li>Intel i82540EM (LOM) 1000BASE-T Ethernet</li> - <li>Intel i82540EP 1000BASE-T Ethernet</li> - <li>Intel i82541EI 1000BASE-T Ethernet</li> - <li>Intel i82541EI (Mobile) 1000BASE-T Ethernet</li> - <li>Intel i82541ER 1000BASE-T Ethernet</li> - <li>Intel i82541GI 1000BASE-T Ethernet</li> - <li>Intel i82541PI 1000BASE-T Ethernet</li> - <li>Intel i82545EM 1000BASE-T Ethernet</li> - <li>Intel i82545EM 1000BASE-X Ethernet</li> - <li>Intel i82545GB 1000BASE-T Ethernet</li> - <li>Intel i82545GB 1000BASE-X Ethernet</li> - <li>Intel i82545GM 1000BASE-T Ethernet</li> - <li>Intel i82546EB 1000BASE-T Ethernet (dual-port)</li> - <li>Intel i82546EB 1000BASE-X Ethernet (dual-port)</li> - <li>Intel i82546GB 1000BASE-T Ethernet (dual-port)</li> - <li>Intel i82546GB 1000BASE-X Ethernet (dual-port)</li> - <li>Intel i82547EI 1000BASE-T Ethernet (CSA)</li> - <li>Intel i82547GI 1000BASE-T Ethernet (CSA)</li> - <li>Intel i82571 1000BASE-T Ethernet (dual-port)</li> - <li>Intel i82572 1000BASE-T Ethernet</li> - <li>Intel i82573 1000BASE-T Ethernet</li> - <li>Intel i82575 1000BASE-T Ethernet</li> - <li>Intel i82576 Ethernet (Copper, Fiber)</li> - <li>Intel i80003 Ethernet (Copper, Fiber)</li> - <li>Intel i82801H (ICH8 LAN) 1000BASE-T Ethernet</li> - <li>Intel i82801I (ICH9 LAN) 1000BASE-T Ethernet</li> - <li>Intel i82801J (ICH10 LAN) 1000BASE-T Ethernet</li> - <li>Intel 82578 with Intel 5 series chipset (PCH)</li> - <li>Intel 82579 with Intel 6 or 7 series chipset (PCH2)</li> - <li>Intel 82580 Ethernet (Copper, Fiber)</li> - <li>Intel 82583 1000BASE-T Ethernet</li> - <li>Intel I350 Ethernet (Copper, Fiber)</li> - <li>Intel I354 (C2000 Internal) Ethernet (Copper, Fiber)</li> - <li>Intel I210 Ethernet (Copper, Fiber)</li> - <li>Intel I211 Ethernet</li> - <li>Intel I217 and I218 Ethernet</li> - <li>Intel I219 Ethernet (with Intel [123]00 series chipset)</li> -</ul> -<p class="Pp">In addition to Intel's own “PRO/1000” line of - Gigabit Ethernet interfaces, these chips also appear on some server systems, - processor evaluation boards, and in embedded systems.</p> -<p class="Pp">The i825[478]x supports IPv4/TCP/UDP checksumming and TCP - segmentation in hardware. The <code class="Nm">wm</code> driver supports - these features of the chip. At least for some chips (e.g. I219) hardware TCP - segmentation is slow, and slows down transmit performance when turned on. - See <a class="Xr">ifconfig(8)</a> for information on how to enable this - feature.</p> -<p class="Pp">Many chips supported by the <code class="Nm">wm</code> driver - support jumbo frames, however several chips do not support jumbo frames, - e.g. i82542, i82081H and 82567V. Jumbo frames can be configured via the - interface MTU setting. Selecting an MTU larger than 1500 bytes with the - <a class="Xr">ifconfig(8)</a> utility configures the adapter to receive and - transmit jumbo frames.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="OPTIONS"><a class="permalink" href="#OPTIONS">OPTIONS</a></h1> -<p class="Pp">The driver default behavior is to handle packets in interrupt - context, which reduces the CPU time available to user processes when under - heavy network load. The - <a class="permalink" href="#hw.wmX.txrx_workqueue"><i class="Em" id="hw.wmX.txrx_workqueue">hw.wmX.txrx_workqueue</i></a> - <a class="Xr">sysctl(8)</a> alters this behavior so that packets are handled - by a kernel thread, which executes at a lower priority. This gives user - processes more opportunity to be executed, at the expense of network - throughput.</p> -<p class="Pp">The following options can be set at build time:</p> -<div class="Bd-indent"> -<dl class="Bl-tag"> - <dt id="WM_RX_PROCESS_LIMIT_DEFAULT"><a class="permalink" href="#WM_RX_PROCESS_LIMIT_DEFAULT"><code class="Dv">WM_RX_PROCESS_LIMIT_DEFAULT</code></a></dt> - <dd>The maximum number of received packets processed in each - <a class="Xr">softint(9)</a> context. This option only affects multiqueue. - The value range is from zero to <code class="Dv">UINT_MAX</code>. The - default value is 100. When you increase this value, both the receive - latency and the receive throughput will increase.</dd> - <dt id="WM_TX_PROCESS_LIMIT_DEFAULT"><a class="permalink" href="#WM_TX_PROCESS_LIMIT_DEFAULT"><code class="Dv">WM_TX_PROCESS_LIMIT_DEFAULT</code></a></dt> - <dd>Transmit side of <code class="Dv">WM_RX_PROCESS_LIMIT_DEFAULT</code>.</dd> - <dt id="WM_RX_INTR_PROCESS_LIMIT_DEFAULT"><a class="permalink" href="#WM_RX_INTR_PROCESS_LIMIT_DEFAULT"><code class="Dv">WM_RX_INTR_PROCESS_LIMIT_DEFAULT</code></a></dt> - <dd>The maximum number of received packets processed in each hardware - interrupt context. This option only affects multiqueue. The value range is - from zero to <code class="Dv">UINT_MAX</code>. The default value is 0. - When you increase this value, both the receive latency and the receive - throughput will decrease.</dd> - <dt id="WM_TX_INTR_PROCESS_LIMIT_DEFAULT"><a class="permalink" href="#WM_TX_INTR_PROCESS_LIMIT_DEFAULT"><code class="Dv">WM_TX_INTR_PROCESS_LIMIT_DEFAULT</code></a></dt> - <dd>Transmit side of - <code class="Dv">WM_RX_INTR_PROCESS_LIMIT_DEFAULT</code>.</dd> - <dt id="WM_EVENT_COUNTERS"><a class="permalink" href="#WM_EVENT_COUNTERS"><code class="Dv">WM_EVENT_COUNTERS</code></a></dt> - <dd>Enable many event counters such as each Tx drop counter and Rx interrupt - counter. In 64 bit architectures, this is enabled by default. Caution: If - this flag is enabled, the number of evcnt entries increase very much.</dd> - <dt id="WM_DISABLE_EVENT_COUNTERS"><a class="permalink" href="#WM_DISABLE_EVENT_COUNTERS"><code class="Dv">WM_DISABLE_EVENT_COUNTERS</code></a></dt> - <dd>Disable event counters for 64 bit architectures.</dd> - <dt id="WM_DISABLE_MSI"><a class="permalink" href="#WM_DISABLE_MSI"><code class="Dv">WM_DISABLE_MSI</code></a></dt> - <dd>If this option is set non-zero value, this driver does not use msi. The - default value is 0.</dd> - <dt id="WM_DISABLE_MSIX"><a class="permalink" href="#WM_DISABLE_MSIX"><code class="Dv">WM_DISABLE_MSIX</code></a></dt> - <dd>If this option is set non-zero value, this driver does not use msix. The - default value is 0.</dd> -</dl> -</div> -<p class="Pp">Setting <code class="Dv">WM_RX_INTR_PROCESS_LIMIT_DEFAULT</code> - to zero means so-called polling mode, that is, once an interrupt occurs, the - driver keep processing received packets until - <code class="Dv">WM_RX_PROCESS_LIMIT_DEFAULT</code>. Polling mode increases - latency a little, however it suppresses performance degradation at high load - very well.</p> -<p class="Pp">If you want to disable polling mode (to use traditional interrupt - driven mode), you should set - <code class="Dv">WM_RX_PROCESS_LIMIT_DEFAULT</code> to zero and set - <code class="Dv">WM_RX_INTR_PROCESS_LIMIT_DEFAULT</code> to - <code class="Dv">UINT_MAX</code>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">arp(4)</a>, <a class="Xr">ifmedia(4)</a>, - <a class="Xr">mii(4)</a>, <a class="Xr">netintro(4)</a>, - <a class="Xr">pci(4)</a>, <a class="Xr">ifconfig(8)</a>, - <a class="Xr">sysctl(8)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">wm</code> driver first appeared in - <span class="Ux">NetBSD 1.6</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="AUTHORS"><a class="permalink" href="#AUTHORS">AUTHORS</a></h1> -<p class="Pp">The <code class="Nm">wm</code> driver was written by - <span class="An">Jason R. Thorpe</span> - <<a class="Mt" href="mailto:thorpej@wasabisystems.com">thorpej@wasabisystems.com</a>>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">EEE (Energy Efficiency Ethernet) is not currently supported.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 17, 2021</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |