ethernet/intel/ixgbe.rst

232 the DCB features (multiple traffic classes utilizing Priority Flow Control and
235 When DCB is enabled, network traffic is transmitted and received through
236 multiple traffic classes (packet buffers in the NIC). The traffic is associated
238 in the VLAN tag. When SR-IOV is not enabled, each traffic class is associated
240 pairs for a given traffic class depends on the hardware configuration. When
243 receive/transmit descriptor queue pairs. When multiple traffic classes are
245 each traffic class. When a single traffic class is configured in the hardware,
246 the pools contain multiple queue pairs from the single traffic class.
248 The number of VFs that can be allocated depends on the number of traffic
249 classes that can be enabled. The configurable number of traffic classes for
251 0 - 15 VFs = Up to 8 traffic classes, depending on device support
252 16 - 31 VFs = Up to 4 traffic classes
253 32 - 63 VFs = 1 traffic class
256 the DCB features with the constraint that each traffic class will only use a
258 queue pairs per traffic class.
351 Sideband Perfect Filters are used to direct traffic that matches specified
363   <queue> - the queue to direct traffic towards (-1 discards the matched traffic)
372 The following example matches TCP traffic sent from 192.168.0.1, port 5300,
397 To create filters that direct traffic to a specific Virtual Function, use the
404 specifies to direct traffic to Virtual Function 7 (8 minus 1) into queue 2 of
408 route traffic that otherwise would not have been sent to the specified Virtual
462 shown that by coalescing Rx traffic into larger chunks of data, CPU
476 the VLAN priority tag (802.1p) to filter traffic. That means that there are 8
477 different priorities that traffic can be filtered into. It also enables