Xilinx Alveo X3522 User Manual page 55

Hide thumbs Also See for Alveo X3522:
Table of Contents

Advertisement

Table 8: Ethtool -S Output (cont'd)
Field
port_rx_nodesc_drops
port_pm_discard_vfifo_full
port_rxdp_q_disabled_packets
port_rxdp_di_dropped_packets
port_ctpio_underflow_fail
port_ctpio_success
ptp_invalid_sync_windows
ptp_skipped_sync
ptp_tx_dropped_timestamp
pps_fw
pps_in_count
pps_in_offset_mean
pps_in_offset_last
pps_in_offset_max
pps_in_offset_min
pps_in_period_mean
pps_in_period_last
pps_in_period_max
pps_in_period_min
pps_in_bad
pps_in_oflow
tx_stop_queue
evq_time_sync_events
evq_error_events
UG1523 (v1.0) October 18, 2022
Alveo X3522 User Guide
Number of packets dropped by the network adapter because of a lack of RX
descriptors in the RX queue.
Packets can be dropped by the NIC when there are insufficient RX descriptors in
the RX queue to allocate to the packet. This problem occurs if the receive rate is
very high and the network adapter receive cycle process has insufficient time
between processing to refill the queue with new descriptors.
A number of different steps can be tried to resolve this issue:
Disable the irqbalance daemon in the OS
Distribute the traffic load across the available CPU/cores by setting
rss_cpus=cores. Refer to Receive Side Scaling section
Increase receive queue size using ethtool.
Count of the number of packets dropped because of a lack of main packet
memory on the adapter to receive the packet into.
Increments when the filter indicates the packet should be delivered to a specific
RX queue which is currently disabled due to configuration error or error
condition.
Number of packets dropped because the filters indicate the packet should be
dropped. Can happen because:
the packet does not match any filter.
the matched filter indicates the packet should be dropped.
When the host fails to push packet bytes fast enough to match the adapter port
speed.
The packet is truncated and data transmitted as a poisoned packet.
Number of successful CTPIO TX events.
Number of times that the PTP window (pre and post time sample) is
unexpectedly large.
Number of times that PTP synchronization is skipped due to repeated
invalid_sync_windows.
Number of transmitted PTP packets dropped because of timestamp.
Number of PPS pulses received from firmware.
Number of external PPS pulses received.
Mean offset of the PPS pulse from the adapter clock, in nanoseconds.
Last offset of the PPS pulse from the adapter clock, in nanoseconds.
Maximum offset of the PPS pulse from the adapter clock, in nanoseconds.
Minimum offset of the PPS pulse from the adapter clock, in nanoseconds.
Mean period between successive PPS pulses, in nanoseconds.
Last period between successive PPS pulses, in nanoseconds.
Maximum period between successive PPS pulses, in nanoseconds.
Minimum period between successive PPS pulses, in nanoseconds.
Number of bad PPS periods.
Number of PPS overflows.
Number of times the transmit queue has been stopped because space was not
available.
Number of time sync events received.
Number of error events received.
Chapter 8: Statistics and Logging
Description
www.xilinx.com
Send Feedback
55

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents