Print this page
11641 spelling mistakes in section 7d of the manual
*** 34,44 ****
Provider Interface (DLPI) which is documented in dlpi(7P). For most
consumers, the use of libdlpi(3LIB), is recommended.
Each instance is assigned a unique ascending integer identifier. A
device which has multiple ports may appear to the system as separate
! instances. The system does not provide a guarnatee on how these will be
presented. Using this instance identifier, one can determine the exact
character-special file to open. For example, the first instance
enumerated in the system, with id 0, would be named i40e0. It exists in
the file system at /dev/net/i40e0.
--- 34,44 ----
Provider Interface (DLPI) which is documented in dlpi(7P). For most
consumers, the use of libdlpi(3LIB), is recommended.
Each instance is assigned a unique ascending integer identifier. A
device which has multiple ports may appear to the system as separate
! instances. The system does not provide a guarantee on how these will be
presented. Using this instance identifier, one can determine the exact
character-special file to open. For example, the first instance
enumerated in the system, with id 0, would be named i40e0. It exists in
the file system at /dev/net/i40e0.
*** 79,89 ****
the device. The default MTU is 1500.
mr_enable
Minimum: 0 | Maximum: 1
! The mr_enable proeprty determines whether or not support for
multiple rings is enabled for the device. The default is always
to enable them. It is not recommended to to disable them.
rx_ring_size
Minimum: 64 | Maximum: 4096
--- 79,89 ----
the device. The default MTU is 1500.
mr_enable
Minimum: 0 | Maximum: 1
! The mr_enable property determines whether or not support for
multiple rings is enabled for the device. The default is always
to enable them. It is not recommended to to disable them.
rx_ring_size
Minimum: 64 | Maximum: 4096
*** 123,151 ****
tx_hcksum_enable
Minimum: 0 | Maximum: 1
The tx_hcksum_enable property controls whether or not the device
! enables support for hardware checksuming of outgoing packets.
The default is to always enable support for this. Turning it off
will increase latency and decrease throughput when transmitting
packets, but should be done if a hardware bug is suspected.
rx_hcksum_enable
Minimum: 0 | Maximum: 1
The rx_hcksum_enable property controls whether or not the device
! enables support for hardware checksuming of incoming packets.
The default is to always enable support for this. Turning it off
will increase latency and decrease throughput when receiving
packets, but should be done if a hardware bug is suspected.
rx_dma_threshold
Minimum: 0 | Maximum: INT32_MAX | Runtime Property:
! _rx_dma_treshold
! The rx_dma_treshold indicates the size in bytes of a received
frame, including all of its headers, at which the driver should
not copy the frame but instead bind DMA memory. By setting this
property to its minimum, all frames will be processed with DMA
binding. By setting this property to its maximum, all frames
will be processed by copying the frame.
--- 123,151 ----
tx_hcksum_enable
Minimum: 0 | Maximum: 1
The tx_hcksum_enable property controls whether or not the device
! enables support for hardware checksumming of outgoing packets.
The default is to always enable support for this. Turning it off
will increase latency and decrease throughput when transmitting
packets, but should be done if a hardware bug is suspected.
rx_hcksum_enable
Minimum: 0 | Maximum: 1
The rx_hcksum_enable property controls whether or not the device
! enables support for hardware checksumming of incoming packets.
The default is to always enable support for this. Turning it off
will increase latency and decrease throughput when receiving
packets, but should be done if a hardware bug is suspected.
rx_dma_threshold
Minimum: 0 | Maximum: INT32_MAX | Runtime Property:
! _rx_dma_threshold
! The rx_dma_threshold indicates the size in bytes of a received
frame, including all of its headers, at which the driver should
not copy the frame but instead bind DMA memory. By setting this
property to its minimum, all frames will be processed with DMA
binding. By setting this property to its maximum, all frames
will be processed by copying the frame.
*** 164,178 ****
The i40e driver is only supported on x86 systems at this time.
FILES
/dev/net/i40e* Per-instance character device.
! /kernel/drv/i40e 32-bit device driver (x86).
! /kernel/drv/amd64/i40e 64-bit device driver (x86).
- /kernel/drv/i40e.conf Driver configuration file.
-
SEE ALSO
dladm(1M), snoop(1M), driver.conf(4), dlpi(7P)
! illumos May 23, 2018 illumos
--- 164,176 ----
The i40e driver is only supported on x86 systems at this time.
FILES
/dev/net/i40e* Per-instance character device.
! /kernel/drv/amd64/i40e Device driver (x86)
! /kernel/drv/i40e.conf Driver configuration file
SEE ALSO
dladm(1M), snoop(1M), driver.conf(4), dlpi(7P)
! illumos January 10, 2020 illumos