| /Documentation/networking/ |
| D | statistics.rst | 4 Interface statistics
10 This document is a guide to Linux network interface statistics.
12 There are three main sources of interface statistics in Linux:
14 - standard interface statistics based on
16 - protocol-specific statistics; and
17 - driver-defined statistics available via ethtool.
19 Standard interface statistics
22 There are multiple interfaces to reach the standard statistics.
44 Queue statistics argument
47 Queue statistics are accessible via the netdev netlink family.
[all …]
|
| D | gen_stats.rst | 4 Generic networking statistics for netlink users
12 gnet_stats_basic TCA_STATS_BASIC Basic statistics
14 gnet_stats_queue TCA_STATS_QUEUE Queue statistics
30 Update statistics, in dequeue() methods only, (while owning qdisc->running)::
83 Locks are taken before writing and released once all statistics have
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-mdio | 1 What: /sys/bus/mdio_bus/devices/.../statistics/
2 What: /sys/class/mdio_bus/.../statistics/
7 This folder contains statistics about global and per
8 MDIO bus address statistics.
10 What: /sys/bus/mdio_bus/devices/.../statistics/transfers
18 What: /sys/bus/mdio_bus/devices/.../statistics/errors
19 What: /sys/class/mdio_bus/.../statistics/errors
26 What: /sys/bus/mdio_bus/devices/.../statistics/writes
27 What: /sys/class/mdio_bus/.../statistics/writes
34 What: /sys/bus/mdio_bus/devices/.../statistics/reads
[all …]
|
| D | sysfs-class-net-statistics | 1 What: /sys/class/net/<iface>/statistics/collisions
9 What: /sys/class/net/<iface>/statistics/multicast
17 What: /sys/class/net/<iface>/statistics/rx_bytes
26 What: /sys/class/net/<iface>/statistics/rx_compressed
35 What: /sys/class/net/<iface>/statistics/rx_crc_errors
44 What: /sys/class/net/<iface>/statistics/rx_dropped
54 What: /sys/class/net/<iface>/statistics/rx_errors
62 What: /sys/class/net/<iface>/statistics/rx_fifo_errors
71 What: /sys/class/net/<iface>/statistics/rx_frame_errors
81 What: /sys/class/net/<iface>/statistics/rx_length_errors
[all …]
|
| D | sysfs-class-fc_host | 1 What: /sys/class/fc_host/hostX/statistics/fpin_cn_yyy
9 What: /sys/class/fc_host/hostX/statistics/fpin_li_yyy
17 What: /sys/class/fc_host/hostX/statistics/fpin_dn_yyy
|
| D | sysfs-class-fc_remote_ports | 1 What: /sys/class/fc_remote_ports/rport-X:Y-Z/statistics/fpin_cn_yyy
9 What: /sys/class/fc_remote_ports/rport-X:Y-Z/statistics/fpin_li_yyy
17 What: /sys/class/fc_remote_ports/rport-X:Y-Z/statistics/fpin_dn_yyy
|
| D | sysfs-block-zram | 73 statistics not accounted by block layer. For example,
75 block layer statistics file format.
82 statistics (orig_data_size, compr_data_size, etc.) in a format
83 similar to block layer statistics file format.
122 statistics (bd_count, bd_reads, bd_writes) in a format
123 similar to block layer statistics file format.
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 6 https://lore.kernel.org/r/461CF883.2030308@sw.ru and implements per cgroup statistics as
9 Per cgroup statistics infrastructure re-uses code from the taskstats
12 extend per cgroup statistics, by adding members to the cgroupstats
16 statistics on interesting events), should be very easy to add. Currently
17 user space requests for statistics by passing the cgroup path.
18 Statistics about the state of all the tasks in the cgroup is returned to
25 To extract cgroup statistics a utility very similar to getdelays.c
|
| D | delay-accounting.rst | 21 and makes these statistics available to userspace through
29 delay statistics aggregated for all tasks (or threads) belonging to a
34 aggregate delay statistics into arbitrary groups. To enable this, delay
35 statistics of a task are available both during its lifetime as well as on its
45 statistics. The delay accounting functionality populates specific fields of
60 When a task exits, records containing the per-task statistics
62 task of a thread group, the per-tgid statistics are also sent. More details
66 commands to be run and the corresponding delay statistics to be displayed. It
|
| D | taskstats.rst | 2 Per-task statistics interface
7 per-process statistics from the kernel to userspace.
11 - efficiently provide statistics during lifetime of a task and on its exit
30 To get statistics during a task's lifetime, userspace opens a unicast netlink
32 The response contains statistics for a task (if pid is specified) or the sum of
33 statistics for all tasks of the process (if tgid is specified).
35 To obtain statistics for tasks which are exiting, the userspace listener
37 one of the cpus in the cpumask, its per-pid statistics are sent to the
48 for reporting delay accounting statistics. Users can register cpumasks,
81 the task/process for which userspace wants statistics.
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dvb-fe-read-status.rst | 6 Querying frontend status and statistics
11 tuner lock status and provide statistics about the quality of the
17 Signal statistics are provided via
22 Most statistics require the demodulator to be fully locked
24 :ref:`Frontend statistics indicators <frontend-stat-properties>` for
|
| D | fe-get-property.rst | 39 ``FE_GET_PROPERTY`` ioctls. The supported properties and statistics
59 - This ioctl is used to get properties and statistics from the
62 - No properties are changed, and statistics aren't reset.
|
| /Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 2 DM statistics
5 Device Mapper supports the collection of I/O statistics on user-defined
6 regions of a DM device. If no regions are defined no statistics are
11 Individual statistics will be collected for each step-sized area within
14 The I/O statistics counters for each step-sized area of a region are
28 must be supplied when querying statistics about the region, deleting the
30 request and process statistics for the same DM device without stepping
33 The creation of DM statistics will allocate memory via kmalloc or
35 memory may be allocated by DM statistics. The admin can see how much
176 statistics does not want to lose any statistics (those updated
[all …]
|
| /Documentation/arch/powerpc/ |
| D | vcpudispatch_stats.rst | 4 VCPU Dispatch Statistics
14 /proc/powerpc/vcpudispatch_stats can be used to obtain statistics
16 collecting the statistics, while writing '0' disables the statistics.
21 The statistics themselves are available by reading the procfs file
27 1. total vcpu dispatches since the beginning of statistics collection
39 The final 3 numbers represent statistics in relation to the home node of
68 statistics were enabled. 4126 of those dispatches were on the same
|
| /Documentation/cpu-freq/ |
| D | cpufreq-stats.rst | 15 2. Statistics Provided (with example)
22 cpufreq-stats is a driver that provides CPU frequency statistics for each CPU.
23 These statistics are provided in /sysfs as a bunch of read_only interfaces. This
26 Various statistics will form read_only files under this directory.
32 2. Statistics Provided (with example)
35 cpufreq stats provides following statistics (explained in detail below).
41 All the statistics will be from the time the stats driver has been inserted
126 [*] CPU frequency translation statistics
132 "CPU frequency translation statistics" (CONFIG_CPU_FREQ_STAT) provides the
133 statistics which includes time_in_state, total_trans and trans_table.
[all …]
|
| /Documentation/driver-api/media/ |
| D | dtv-frontend.rst | 110 :ref:`DVBv5 statistics <dvbv5_stats>` via ``.read_status``.
111 Yet, there are a number of callbacks meant to get statistics for
166 Digital TV Frontend statistics
173 :ref:`statistics <frontend-stat-properties>` meant to help tuning the device
176 For each statistics measurement, the driver should set the type of scale used,
177 or ``FE_SCALE_NOT_AVAILABLE`` if the statistics is not available on a given
178 time. Drivers should also provide the number of statistics for each type.
190 And, when the statistics got updated, set the scale::
195 .. [#f2] For ISDB-T, it may provide both a global statistics and a per-layer
196 set of statistics. On such cases, len should be equal to 4. The first
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-intel-ipu3.rst | 12 3A statistics
15 The IPU3 ImgU 3A statistics accelerators collect different statistics over
16 an input Bayer frame. Those statistics are obtained from the "ipu3-imgu [01] 3a
21 The statistics collected are AWB (Auto-white balance) RGBS (Red, Green, Blue and
50 Both 3A statistics and pipeline parameters described here are closely tied to
|
| D | metafmt-rkisp1.rst | 65 3A and histogram statistics
68 The ISP1 device collects different statistics over an input Bayer frame.
69 Those statistics are obtained from the :ref:`rkisp1_stats <rkisp1_stats>`
79 The statistics collected are Exposure, AWB (Auto-white balance), Histogram and
80 AF (Auto-focus). See :c:type:`rkisp1_stat_buffer` for details of the statistics.
82 The 3A statistics and configuration parameters described here are usually
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-xen-backend | 34 What: /sys/bus/xen-backend/devices/vbd-*/statistics/f_req
41 What: /sys/bus/xen-backend/devices/vbd-*/statistics/oo_req
49 What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_req
56 What: /sys/bus/xen-backend/devices/vbd-*/statistics/rd_sect
63 What: /sys/bus/xen-backend/devices/vbd-*/statistics/wr_req
70 What: /sys/bus/xen-backend/devices/vbd-*/statistics/wr_sect
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 2 Scheduler Statistics
22 statistics for each cpu listed, and there may well be more than one
42 CPU statistics
50 Next three are schedule() statistics:
57 Next two are try_to_wake_up() statistics:
62 Next three are statistics describing scheduling latency:
70 Domain statistics
80 The next 24 are a variety of sched_balance_rq() statistics in grouped into types
131 Next three are active_load_balance() statistics:
137 Next three are sched_balance_exec() statistics:
[all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | omap3isp-uapi.rst | 20 statistics (AEWB, AF and histogram) subdevs.
32 Each of the statistics subdevs is able to produce events. An event is
33 generated whenever a statistics buffer can be dequeued by a user space
42 ioctls. If there is an error calculating the statistics, there will be an
43 event as usual, but no related statistics buffer. In this case
53 statistics collection are examples of such.
140 The statistics subdevs do offer more dynamic configuration options than the
144 The statistics blocks always get the input image data from the CCDC (as the
145 histogram memory read isn't implemented). The statistics are dequeueable by
146 the user from the statistics subdev nodes using private IOCTLs.
|
| /Documentation/locking/ |
| D | lockstat.rst | 2 Lock Statistics
8 As the name suggests, it provides statistics on locks.
48 With these hooks we provide the following statistics:
86 Lock statistics are enabled via CONFIG_LOCK_STAT.
91 Enable collection of statistics::
95 Disable collection of statistics::
99 Look at the current lock statistics::
139 This excerpt shows the first two lock class statistics. Line 01 shows the
142 statistics. These statistics come in two parts; the actual stats separated by a
148 con-bounces point is missing in the statistics.
[all …]
|
| D | locktorture.rst | 103 Number of seconds between statistics-related printk()s.
105 Setting the interval to zero causes the statistics to
127 Statistics chapter
130 Statistics are printed in the following format::
138 primitive a second "Reads" statistics line is printed.
|
| /Documentation/admin-guide/ |
| D | iostats.rst | 2 I/O statistics fields
6 more extensive disk statistics have been introduced to help measure disk
44 each snapshot of your disk statistics.
46 In 2.4, the statistics fields are those after the device name. In
47 the above example, the first field of statistics would be 446216.
52 15 fields of statistics, each meaning exactly the same things.
141 almost a non-issue. When the statistics are read, the per-CPU counters
157 in 2.4. Consequently, you'll see a different statistics output on 2.6+ for
189 disk and partition statistics are consistent again. Since we still don't
205 In 2.6+, all disk statistics were removed from ``/proc/stat``. In 2.4, they
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 107 Ethtool is supported. Driver statistics and internal errors can be taken using:
133 The driver exports debug information such as internal statistics,
136 A user may use the ethtool support to get statistics:
137 e.g. using: ethtool -S ethX (that shows the statistics counters)
143 6. Statistics Support
146 The controller and driver support a mix of IEEE standard defined statistics,
147 RFC defined statistics, and driver or Altera defined statistics. The four
148 specifications containing the standard definitions for these statistics are
156 The statistics supported by the TSE and the device driver are as follows:
159 Section 5.2.2.1.2. This statistics is the count of frames that are successfully
[all …]
|