svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
cxgbe(4)
To compile this driver into the kernel, place the following lines
in your kernel configuration file: To load the driver as a module
at boot time, place the following lines in t4fw_cfg_load="YES"
t5fw_cfg_load="YES" t6fw_cfg_load="YES" if_cxgbe_load="YES" The
driver provides support for PCI Express Ethernet adapters based
on the Chelsio Terminator 4, Terminator 5, and Terminator 6 ASICs
(T4, T5, and T6). The driver supports Jumbo Frames, Transmit/Re‐
ceive checksum offload, TCP segmentation offload (TSO), Large Re‐
ceive Offload (LRO), VLAN tag insertion/extraction, VLAN checksum
offload, VLAN TSO, and Receive Side Steering (RSS). For further
hardware information and questions related to hardware require‐
ments, see The driver uses different names for devices based on
the associated ASIC: Loader tunables with the hw.cxgbe prefix ap‐
ply to all cards. The driver provides sysctl MIBs for both ports
and parent devices using the names above. For example, a T5
adapter provides port MIBs under dev.cxl and adapter-wide MIBs
under dev.t5nex. References to sysctl MIBs in the remainder of
this page use dev.<port> for port MIBs and dev.<nexus> for
adapter-wide MIBs. For more information on configuring this de‐
vice, see The driver supports 100Gb and 25Gb Ethernet adapters
based on the T6 ASIC: Chelsio T6225-CR Chelsio T6225-SO-CR Chel‐
sio T62100-LP-CR Chelsio T62100-SO-CR Chelsio T62100-CR The dri‐
ver supports 40Gb, 10Gb and 1Gb Ethernet adapters based on the T5
ASIC: Chelsio T580-CR Chelsio T580-LP-CR Chelsio T580-LP-SO-CR
Chelsio T560-CR Chelsio T540-CR Chelsio T540-LP-CR Chelsio
T522-CR Chelsio T520-LL-CR Chelsio T520-CR Chelsio T520-SO Chel‐
sio T520-BT Chelsio T504-BT The driver supports 10Gb and 1Gb Eth‐
ernet adapters based on the T4 ASIC: Chelsio T420-CR Chelsio
T422-CR Chelsio T440-CR Chelsio T420-BCH Chelsio T440-BCH Chelsio
T440-CH Chelsio T420-SO Chelsio T420-CX Chelsio T420-BT Chelsio
T404-BT Tunables can be set at the prompt before booting the ker‐
nel or stored in There are multiple tunables that control the
number of queues of various types. A negative value for such a
tunable instructs the driver to create up to that many queues if
there are enough CPU cores available. Number of NIC tx queues
used for a port. The default is 16 or the number of CPU cores in
the system, whichever is less. Number of NIC rx queues used for
a port. The default is 8 or the number of CPU cores in the sys‐
tem, whichever is less. Number of TOE tx queues used for a port.
The default is 8 or the number of CPU cores in the system,
whichever is less. Number of TOE rx queues used for a port. The
default is 2 or the number of CPU cores in the system, whichever
is less. Number of virtual interfaces (VIs) created for each
port. Each virtual interface creates a separate network inter‐
face. The first virtual interface on each port is required and
represents the primary network interface on the port. Additional
virtual interfaces on a port are named using the Virtual Inter‐
face name from the table above. Additional virtual interfaces
use a single pair of queues for rx and tx as well an additional
pair of queues for TOE rx and tx. The default is 1. Timer index
value used to delay interrupts. The holdoff timer list has the
values 1, 5, 10, 50, 100, and 200 by default (all values are in
microseconds) and the index selects a value from this list.
holdoff_timer_idx_ofld applies to queues used for TOE rx. The
default value is 1 which means the timer value is 5us. Different
interfaces can be assigned different values at any time via the
dev.<port>.X.holdoff_tmr_idx and dev.<port>.X.hold‐
off_tmr_idx_ofld sysctls. Packet-count index value used to delay
interrupts. The packet-count list has the values 1, 8, 16, and
32 by default, and the index selects a value from this list.
holdoff_pktc_idx_ofld applies to queues used for TOE rx. The de‐
fault value is -1 which means packet counting is disabled and in‐
terrupts are generated based solely on the holdoff timer value.
Different interfaces can be assigned different values via the
dev.<port>.X.holdoff_pktc_idx and dev.<port>.X.hold‐
off_pktc_idx_ofld sysctls. These sysctls work only when the in‐
terface has never been marked up (as done by ifconfig up). Num‐
ber of entries in a transmit queue's descriptor ring. A buf_ring
of the same size is also allocated for additional software queu‐
ing. See The default value is 1024. Different interfaces can be
assigned different values via the dev.<port>.X.qsize_txq sysctl.
This sysctl works only when the interface has never been marked
up (as done by ifconfig up). Number of entries in a receive
queue's descriptor ring. The default value is 1024. Different
interfaces can be assigned different values via the
dev.<port>.X.qsize_rxq sysctl. This sysctl works only when the
interface has never been marked up (as done by ifconfig up).
Permitted interrupt types. Bit 0 represents INTx (line inter‐
rupts), bit 1 MSI, and bit 2 MSI-X. The default is 7 (all al‐
lowed). The driver selects the best possible type out of the al‐
lowed types. PCIe Relaxed Ordering. -1 indicates the driver
should determine whether to enable or disable PCIe RO. 0 dis‐
ables PCIe RO. 1 enables PCIe RO. 2 indicates the driver should
not modify the PCIe RO setting. The default is -1. 0 prohibits
the driver from installing a firmware on the card. 1 allows the
driver to install a new firmware if internal driver heuristics
indicate that the new firmware is preferable to the one already
on the card. 2 instructs the driver to always install the new
firmware on the card as long as it is compatible with the driver
and is a different version than the one already on the card. The
default is 1. Number of padding bytes inserted before the begin‐
ning of an Ethernet frame in the receive buffer. The default
value is 0. A value of of 2 would ensure that the Ethernet pay‐
load (usually the IP header) is at a 4 byte aligned address. 0-7
are all valid values. A non-zero value ensures that writes from
the hardware to a receive buffer are padded up to the specified
boundary. The default is -1 which lets the driver pick a pad
boundary. 0 disables trailer padding completely. Controls the
hardware response to congestion. -1 disables congestion feedback
and is not recommended. 0 instructs the hardware to backpressure
its pipeline on congestion. This usually results in the port
emitting PAUSE frames. 1 instructs the hardware to drop frames
destined for congested queues. PAUSE frame settings. Bit 0 is
rx_pause, bit 1 is tx_pause, bit 2 is pause_autoneg. rx_pause =
1 instructs the hardware to heed incoming PAUSE frames, 0 in‐
structs it to ignore them. tx_pause = 1 allows the hardware to
emit PAUSE frames when its receive FIFO reaches a high threshold,
0 prohibits the hardware from emitting PAUSE frames. pause_au‐
toneg = 1 overrides the rx_pause and tx_pause bits and instructs
the hardware to negotiate PAUSE settings with the link peer. The
default is 7 (all three = 1). This tunable establishes the de‐
fault PAUSE settings for all ports. Settings can be displayed
and controlled on a per-port basis via the
dev.<port>.X.pause_settings sysctl. FEC (Forward Error Correc‐
tion) settings. 0 diables FEC. Bit 0 enables RS FEC, bit 1 en‐
ables BASE-R FEC (aka Firecode FEC). The default is -1 which
lets the driver pick a value. This tunable establishes the de‐
fault FEC settings for all ports. Settings can be displayed and
controlled on a per-port basis via the dev.<port>.X.fec sysctl.
Link autonegotiation settings. This tunable establishes the de‐
fault autonegotiation settings for all ports. Settings can be
displayed and controlled on a per-port basis via the
dev.<port>.X.autoneg sysctl. 0 disables autonegotiation. 1 en‐
ables autonegotiation. The default is -1 which lets the driver
pick a value. dev.<port>.X.autoneg is -1 for port and module
combinations that do not support autonegotiation. Allow the
hardware to deliver multiple frames in the same receive buffer
opportunistically. The default is -1 which lets the driver de‐
cide. 0 or 1 explicitly disable or enable this feature. 1 al‐
lows the driver to lay down one or more mbufs within the receive
buffer opportunistically. This is the default. 0 prohibits the
driver from doing so. Sizes of rx clusters. Each of these must
be set to one of the sizes available (usually 2048, 4096, 9216,
and 16384) and largest_rx_cluster must be greater than or equal
to safest_rx_cluster. The defaults are 16384 and 4096 respec‐
tively. The driver never attempts to allocate a receive buffer
larger than largest_rx_cluster and falls back to allocating
buffers of safest_rx_cluster size if an allocation larger than
safest_rx_cluster fails. Note that largest_rx_cluster merely es‐
tablishes a ceiling -- the driver is allowed to allocate buffers
of smaller sizes. Select a pre-packaged device configuration
file. A configuration file contains a recipe for partitioning
and configuring the hardware resources on the card. This tunable
is for specialized applications only and should not be used in
normal operation. The configuration profile currently in use is
available in the dev.<nexus>.X.cf and dev.<nexus>.X.cfcsum
sysctls. Disallowing capabilities provides a hint to the driver
and firmware to not reserve hardware resources for that feature.
Each of these is a bit field with a bit for each sub-capability
within the capability. This tunable is for specialized applica‐
tions only and should not be used in normal operation. The capa‐
bilities for which hardware resources have been reserved are
listed in dev.<nexus>.X.*caps sysctls. For general information
and support, go to the Chelsio support website at: If an issue is
identified with this driver with a supported adapter, email all
the specific information related to the issue to The device dri‐
ver first appeared in Support for T5 cards first appeared in and
Support for T6 cards first appeared in and The driver was written
by