IXG(4)

NAME
ixg - Intel(R) 10Gb Ethernet driver

SYNOPSIS
ixg* at pci? dev ? function ?

DESCRIPTION
The ixg driver provides support for PCI 10Gb Ethernet adapters based on the Intel(R) 82598EB, 82599, X540 and X550 Ethernet Controllers. The driver supports Jumbo Frames, TCP Segmentation Offload (TSO).

For questions related to hardware requirements, refer to the documentation supplied with your Intel 10GbE adapter. All hardware requirements listed apply to use with NetBSD.

Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility configures the adapter to receive and transmit Jumbo Frames. On NetBSD, the maximum MTU size for Jumbo Frames is 9000 bytes.

This driver version supports VLANs. For information on enabling VLANs, see ifconfig(8).

DIAGNOSTICS

ixg%d: Unable to allocate bus resource: memory A fatal initialization error has occurred.

ixg%d: Unable to allocate bus resource: interrupt A fatal initialization error has occurred.

ixg%d: watchdog timeout -- resetting The device has stopped responding to the network, or there is a problem with the network connection (cable).

SUPPORT
For general information and support, go to the Intel support website at: http://www.intel.com/support/.

OPTIONS
The ixg driver doesn't use the common MCLGET(9) interface and use the driver specific cluster allocation mechanism. If it's exhausted, the evcnt(9) counter "ixgX qY Rx no jumbo mbuf" is incremented. If this is observed, the number can be changed by the following config parameter:

IXGBE_JCLNUM_MULTI
    The number of RX jumbo buffers (clusters) per queue is calculated by IXGBE_JCLNUM_MULTI * (number of rx descriptors). The total number of clusters per queue is available via the hw.ixgN.num_jcl_per_queue sysctl(7).

SEE ALSO
arp(4), ixv(4), netintro(4), vlan(4), ifconfig(8)

HISTORY
The ixg device driver comes from FreeBSD, where it is called ixgbe. It first appeared in NetBSD 6.0.

AUTHORS
The ixg driver was written by Intel Corporation <freebsdnic@mailbox.intel.com>. It was imported from FreeBSD into NetBSD by David Young <dyoung@NetBSD.org>.

BUGS
The hardware supports a maximum MTU of 16114 bytes, but the NetBSD port of the driver supports only 9000 bytes.