DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1059] proc-info -- 0x10 --xstats  do not show the correct statistics
Date: Mon, 25 Jul 2022 10:03:13 +0000	[thread overview]
Message-ID: <bug-1059-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=1059

            Bug ID: 1059
           Summary: proc-info -- 0x10 --xstats  do not show the correct
                    statistics
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: 779198444@qq.com
  Target Milestone: ---

when call dpdk-proc-info -- 0x10 --xstats
it show the following message

###### NIC extended statistics for port 4  #########
####################################################
rx_good_packets: 0
tx_good_packets: 0
rx_good_bytes: 0
tx_good_bytes: 0
rx_missed_errors: 0
rx_errors: 0
tx_errors: 0
rx_mbuf_allocation_errors: 0
rx_crc_errors: 0
rx_align_errors: 0
rx_symbol_errors: 0
rx_missed_packets: 0
tx_single_collision_packets: 0
tx_multiple_collision_packets: 0
tx_excessive_collision_packets: 0
tx_late_collisions: 0
tx_total_collisions: 0
tx_deferred_packets: 0
tx_no_carrier_sense_packets: 0
rx_carrier_ext_errors: 0
rx_length_errors: 0
rx_xon_packets: 0
tx_xon_packets: 0
rx_xoff_packets: 0
tx_xoff_packets: 0
rx_flow_control_unsupported_packets: 0
rx_size_64_packets: 0
rx_size_65_to_127_packets: 0
rx_size_128_to_255_packets: 0
rx_size_256_to_511_packets: 0
rx_size_512_to_1023_packets: 0
rx_size_1024_to_max_packets: 0
rx_broadcast_packets: 0
rx_multicast_packets: 0
rx_undersize_errors: 0
rx_fragment_errors: 0
rx_oversize_errors: 0
rx_jabber_errors: 0
rx_management_packets: 0
rx_management_dropped: 0
tx_management_packets: 0
rx_total_packets: 0
tx_total_packets: 0
rx_total_bytes: 0
tx_total_bytes: 0
tx_size_64_packets: 0
tx_size_65_to_127_packets: 0
tx_size_128_to_255_packets: 0
tx_size_256_to_511_packets: 0
tx_size_512_to_1023_packets: 0
tx_size_1023_to_max_packets: 0
tx_multicast_packets: 0
tx_broadcast_packets: 0
tx_tso_packets: 0
tx_tso_errors: 0
rx_sent_to_host_packets: 0
tx_sent_by_host_packets: 0
rx_code_violation_packets: 0
interrupt_assert_count: 0
####################################################
Cannot close started device (port 0)
Cannot close started device (port 1)
Cannot close started device (port 2)
Cannot close started device (port 3)
Cannot close started device (port 4)

while my realy active port is port 0,and when i use the 18.05 static linked
dpdk-procinfo,it perfomance like this:


EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_18418_1ca2b26784c9a
EAL: Selected IOVA mode 'PA'
EAL: Probe PCI driver: net_e1000_igb (8086:1539) device: 0000:01:00.0 (socket
0)
EAL: Probe PCI driver: net_e1000_igb (8086:1539) device: 0000:02:00.0 (socket
0)
EAL: Probe PCI driver: net_e1000_igb (8086:1539) device: 0000:03:00.0 (socket
0)
EAL: Probe PCI driver: net_e1000_igb (8086:1539) device: 0000:04:00.0 (socket
0)
EAL: Probe PCI driver: net_e1000_igb (8086:1539) device: 0000:05:00.0 (socket
0)
###### NIC extended statistics for port 0  #########
####################################################
rx_good_packets: 575003997
tx_good_packets: 0
rx_good_bytes: 167108158830
tx_good_bytes: 0
rx_missed_errors: 1053260836
rx_errors: 0
tx_errors: 0
rx_mbuf_allocation_errors: 1007413345
rx_crc_errors: 0
rx_align_errors: 0
rx_symbol_errors: 0
rx_missed_packets: 1053260536
tx_single_collision_packets: 0
tx_multiple_collision_packets: 0
tx_excessive_collision_packets: 0
tx_late_collisions: 0
tx_total_collisions: 0
tx_deferred_packets: 0
tx_no_carrier_sense_packets: 0
rx_carrier_ext_errors: 0
rx_length_errors: 0
rx_xon_packets: 0
tx_xon_packets: 892174
rx_xoff_packets: 0
tx_xoff_packets: 1054152715
rx_flow_control_unsupported_packets: 0
rx_size_64_packets: 70505511
rx_size_65_to_127_packets: 369577561
rx_size_128_to_255_packets: 36315460
rx_size_256_to_511_packets: 11032467
rx_size_512_to_1023_packets: 12071014
rx_size_1024_to_max_packets: 75501984
rx_broadcast_packets: 33533668
rx_multicast_packets: 6365832
rx_undersize_errors: 0
rx_fragment_errors: 0
rx_oversize_errors: 0
rx_jabber_errors: 0
rx_management_packets: 0
rx_management_dropped: 0
tx_management_packets: 0
rx_total_packets: 1628264571
tx_total_packets: 1055044925
rx_total_bytes: 283445230373
tx_total_bytes: 63302695756
tx_size_64_packets: 0
tx_size_65_to_127_packets: 0
tx_size_128_to_255_packets: 0
tx_size_256_to_511_packets: 0
tx_size_512_to_1023_packets: 0
tx_size_1023_to_max_packets: 0
tx_multicast_packets: 0
tx_broadcast_packets: 0
tx_tso_packets: 0
tx_tso_errors: 0
rx_sent_to_host_packets: 31492
tx_sent_by_host_packets: 0
rx_code_violation_packets: 0
interrupt_assert_count: 1
..........
####################################################
###### NIC extended statistics for port 4  #########
####################################################
rx_good_packets: 0
tx_good_packets: 0
rx_good_bytes: 0
tx_good_bytes: 0
rx_missed_errors: 0
rx_errors: 0
tx_errors: 0
rx_mbuf_allocation_errors: 0
rx_crc_errors: 0
rx_align_errors: 0
rx_symbol_errors: 0
rx_missed_packets: 0
tx_single_collision_packets: 0
tx_multiple_collision_packets: 0
tx_excessive_collision_packets: 0
tx_late_collisions: 0
tx_total_collisions: 0
tx_deferred_packets: 0
tx_no_carrier_sense_packets: 0
rx_carrier_ext_errors: 0
rx_length_errors: 0
rx_xon_packets: 0
tx_xon_packets: 0
rx_xoff_packets: 0
tx_xoff_packets: 0
rx_flow_control_unsupported_packets: 0
rx_size_64_packets: 0
rx_size_65_to_127_packets: 0
rx_size_128_to_255_packets: 0
rx_size_256_to_511_packets: 0
rx_size_512_to_1023_packets: 0
rx_size_1024_to_max_packets: 0
rx_broadcast_packets: 0
rx_multicast_packets: 0
rx_undersize_errors: 0
rx_fragment_errors: 0
rx_oversize_errors: 0
rx_jabber_errors: 0
rx_management_packets: 0
rx_management_dropped: 0
tx_management_packets: 0
rx_total_packets: 0
tx_total_packets: 0
rx_total_bytes: 0
tx_total_bytes: 0
tx_size_64_packets: 0
tx_size_65_to_127_packets: 0
tx_size_128_to_255_packets: 0
tx_size_256_to_511_packets: 0
tx_size_512_to_1023_packets: 0
tx_size_1023_to_max_packets: 0
tx_multicast_packets: 0
tx_broadcast_packets: 0
tx_tso_packets: 0
tx_tso_errors: 0
rx_sent_to_host_packets: 0
tx_sent_by_host_packets: 0
rx_code_violation_packets: 0
interrupt_assert_count: 0
####################################################

by reading the code ,there just need to change one symbol
here is the solution:
in app/proc-info/main.c
-                       enabled_port_mask = 1ul << i;
+                       enabled_port_mask += 1ul << i;

the same problem found in 22.03

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2022-07-25 10:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-1059-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).