| /dpdk/drivers/net/ipn3ke/ |
| H A D | ipn3ke_representor.c | 659 statistics += statistics_hi; in ipn3ke_rpst_read_64bits_statistics_register() 660 statistics = statistics << IPN3KE_REGISTER_WIDTH; in ipn3ke_rpst_read_64bits_statistics_register() 661 statistics += statistics_lo; in ipn3ke_rpst_read_64bits_statistics_register() 662 return statistics; in ipn3ke_rpst_read_64bits_statistics_register() 673 uint64_t statistics; in ipn3ke_rpst_read_25g_lineside_stats_registers() local 1415 statistics += statistics_hi; in ipn3ke_rpst_read_36bits_statistics_register() 1416 statistics = statistics << IPN3KE_REGISTER_WIDTH; in ipn3ke_rpst_read_36bits_statistics_register() 1418 return statistics; in ipn3ke_rpst_read_36bits_statistics_register() 1428 uint64_t statistics = 0; in ipn3ke_rpst_read_10g_lineside_stats_registers() local 1492 stats->obytes = statistics; in ipn3ke_rpst_read_10g_lineside_stats_registers() [all …]
|
| /dpdk/doc/guides/contributing/ |
| H A D | design.rst | 79 requirements for preventing ABI changes when implementing statistics. 82 Mechanism to allow the application to turn library statistics on and off 94 Prevention of ABI changes due to library statistics support 98 library API should not be affected by whether the collection of statistics 101 statistics counters and the statistics related API functions are always built 105 When the collection of statistics counters for the current library is turned 110 Motivation to allow the application to turn library statistics on and off 125 Library-level statistics counters can be relevant or not for specific 130 accounting, logging, application-level statistics, etc. In this case, 151 * Number of libraries used by the current application that have statistics [all …]
|
| /dpdk/doc/guides/tools/ |
| H A D | proc_info.rst | 9 statistics, resetting port statistics, printing DPDK memory information and 29 The stats parameter controls the printing of generic port statistics. If no 33 The xstats parameter controls the printing of extended port statistics. If no 37 The stats-reset parameter controls the resetting of generic port statistics. If 41 The xstats-reset parameter controls the resetting of extended port statistics. 52 configurations and statistics.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | metrics_lib.rst | 14 Metrics themselves are statistics that are not generated by PMDs. Metric 23 that is intended for global statistics that are not associated with any 171 Bit-rate statistics library 176 These statistics are reported via the metrics library using the 187 statistics can be obtained by querying the metrics library. 215 calculated statistics. For instance if per-second statistics are 236 Latency statistics library 239 The latency statistics library calculates the latency of packet 242 the jitter in processing delay. These statistics are then reported 251 statistics can be obtained by querying the metrics library. [all …]
|
| H A D | poll_mode_drv.rst | 168 * Initialize statistics counters 395 The extended statistics API allows a PMD to expose all statistics that are 406 application to be flexible in how it retrieves statistics. 455 lookup of specific statistics. Performant lookup means two things; 458 * Allow requesting of only the statistics of interest 473 statistics. 483 returns all statistics that are available. 492 set of statistics that it requests. This "set" of statistics allows the app to 496 First step is to get all statistics names and list them: 542 ids of those statistics by looking up the name as follows: [all …]
|
| H A D | pcapng_lib.rst | 40 to write statistics information into the output file. 41 The summary statistics information is automatically added
|
| H A D | dmadev.rst | 115 The statistics from a dmadev device can be got via the statistics functions, 116 i.e. ``rte_dma_stats_get()``. The statistics returned for each device instance are:
|
| H A D | graph_lib.rst | 26 - Low overhead statistics collection infrastructure. 51 - Disable node statistics (using ``RTE_LIBRTE_GRAPH_STATS`` config option) 227 Get the node statistics using graph cluster 233 Introduced a graph cluster object for statistics. 236 to get the aggregate node statistics. 238 An example statistics output from ``rte_graph_cluster_stats_get()``
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | eventdev_pipeline.rst | 46 * ``-D``: dump statistics on exit 72 configuration, and some runtime statistics like packets per second. On exit the 73 worker statistics are printed, along with a full dump of the PMD statistics if 106 At runtime, the statistics of the consumer are printed, stating the number of 146 statistics that the PMD provides. The statistics provided depend on the PMD
|
| H A D | vmdq_forwarding.rst | 37 In Linux* user space, the application can display statistics with the number of packets received on… 38 To have the application display the statistics, send a SIGHUP signal to the running application pro… 118 the VMDq Forwarding sample application can display statistics showing the number of packets read fr… 123 To generate the statistics output, use the following command: 129 Please note that the statistics output will appear on the terminal where the vmdq_app is running,
|
| H A D | vmdq_dcb_forwarding.rst | 46 In Linux* user space, the application can display statistics with the number of packets received on… 47 To have the application display the statistics, send a SIGHUP signal to the running application pro… 138 the VMDQ and DCB Forwarding sample application can display statistics showing the number of packets… 143 To generate the statistics output, use the following command: 149 Please note that the statistics output will appear on the terminal where the vmdq_dcb_app is runnin…
|
| H A D | server_node_efd.rst | 76 lookup. If a match occurs then statistics are updated for flows serviced by 168 access to the shared ring, parameters and statistics. 196 Finally, note that both processes updates statistics, such as transmitted, received 201 :start-after: Display recorded statistics. 8< 202 :end-before: >8 End of displaying the recorded statistics.
|
| H A D | dist_app.rst | 97 final statistics to the user. 131 The main function will print statistics on the console every second. These 132 statistics include the number of packets enqueued and dequeued at each stage 133 in the application, and also key statistics per worker, including how many
|
| H A D | pipeline.rst | 15 The CLI can also be used to update the pipeline tables or poll the pipeline statistics. 118 …om given table of a specific pipeline owned by the current data plane thread, read statistics, etc.
|
| /dpdk/lib/ipsec/ |
| H A D | ipsec_telemetry.c | 83 sa->statistics.count); in handle_telemetry_cmd_ipsec_sa_stats() 86 sa->statistics.bytes - in handle_telemetry_cmd_ipsec_sa_stats() 87 (sa->statistics.count * sa->hdr_len)); in handle_telemetry_cmd_ipsec_sa_stats() 90 sa->statistics.errors.count); in handle_telemetry_cmd_ipsec_sa_stats()
|
| /dpdk/doc/guides/nics/ |
| H A D | hns3.rst | 24 - Port hardware statistics 234 HNS3 supports various methods to report statistics: 236 Port statistics can be queried using ``rte_eth_stats_get()``. The number 242 Extended statistics can be queried using ``rte_eth_xstats_get()``. The extended 243 statistics expose a wider set of counters counted by the device. The extended 244 port statistics contains packets statistics per queue, Mac statistics, HW reset 247 Finally per-flow statistics can by queried using ``rte_flow_query`` when attaching
|
| H A D | fm10k.rst | 151 The FM10000 NICs expose a set of statistics via the PCI BARs. These statistics 154 while the byte counting registers are 48 bits. As a result, the statistics must 160 for in the statistics, it is necessary to read statistic regularly. It is 161 suggested to read stats every 20 seconds, which will ensure the statistics
|
| H A D | kni.rst | 157 ---------------------- Forward statistics for port 0 ---------------------- 162 ---------------------- Forward statistics for port 1 ---------------------- 167 +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
|
| H A D | mvpp2.rst | 174 MVPP2 PMD supports the following extended statistics: 577 3. Gather statistics. 590 - MTR object enabled statistics 647 - bitmask indicating which statistics counters will be read 717 3 - Enable statistics for both number of transmitted packets and bytes. 737 1 - Enable statistics counter for number of transmitted packets. 757 1 - Enable statistics counter for number of transmitted packets. 777 1 - Enable statistics counter for number of transmitted packets.
|
| H A D | atlantic.rst | 18 - Port statistics
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | features_overview.rst | 99 queue statistics 100 Support virtio queue statistics query.
|
| H A D | mlx5.rst | 110 to get error information, or query vdpa statistics counter to know error type 116 The device statistics counter persists in reconfiguration until the device gets
|
| /dpdk/doc/guides/vdpadevs/features/ |
| H A D | mlx5.ini | 21 queue statistics = Y
|
| H A D | default.ini | 40 queue statistics =
|
| /dpdk/examples/pipeline/examples/ |
| H A D | meter.spec | 9 ; The "meter stats" CLI command can be used to read the packet and byte statistics counters of any
|