Home
last modified time | relevance | path

Searched refs:statistics (Results 1 – 25 of 212) sorted by relevance

123456789

/Linux-v5.4/kernel/sched/
Ddebug.c392 PN_SCHEDSTAT(se->statistics.wait_start); in print_cfs_group_stats()
393 PN_SCHEDSTAT(se->statistics.sleep_start); in print_cfs_group_stats()
394 PN_SCHEDSTAT(se->statistics.block_start); in print_cfs_group_stats()
395 PN_SCHEDSTAT(se->statistics.sleep_max); in print_cfs_group_stats()
396 PN_SCHEDSTAT(se->statistics.block_max); in print_cfs_group_stats()
397 PN_SCHEDSTAT(se->statistics.exec_max); in print_cfs_group_stats()
398 PN_SCHEDSTAT(se->statistics.slice_max); in print_cfs_group_stats()
399 PN_SCHEDSTAT(se->statistics.wait_max); in print_cfs_group_stats()
400 PN_SCHEDSTAT(se->statistics.wait_sum); in print_cfs_group_stats()
401 P_SCHEDSTAT(se->statistics.wait_count); in print_cfs_group_stats()
[all …]
/Linux-v5.4/Documentation/ABI/testing/
Dsysfs-class-net-statistics1 What: /sys/class/<iface>/statistics/collisions
9 What: /sys/class/<iface>/statistics/multicast
17 What: /sys/class/<iface>/statistics/rx_bytes
26 What: /sys/class/<iface>/statistics/rx_compressed
35 What: /sys/class/<iface>/statistics/rx_crc_errors
44 What: /sys/class/<iface>/statistics/rx_dropped
54 What: /sys/class/<iface>/statistics/rx_fifo_errors
63 What: /sys/class/<iface>/statistics/rx_frame_errors
73 What: /sys/class/<iface>/statistics/rx_length_errors
82 What: /sys/class/<iface>/statistics/rx_missed_errors
[all …]
Dsysfs-block-zram73 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.
/Linux-v5.4/Documentation/accounting/
Dcgroupstats.rst6 http://lkml.org/lkml/2007/4/11/187 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.
25 To extract cgroup statistics a utility very similar to getdelays.c
Ddelay-accounting.rst17 and makes these statistics available to userspace through
25 delay statistics aggregated for all tasks (or threads) belonging to a
30 aggregate delay statistics into arbitrary groups. To enable this, delay
31 statistics of a task are available both during its lifetime as well as on its
41 statistics. The delay accounting functionality populates specific fields of
55 When a task exits, records containing the per-task statistics
57 task of a thread group, the per-tgid statistics are also sent. More details
61 commands to be run and the corresponding delay statistics to be displayed. It
Dtaskstats.rst2 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 …]
/Linux-v5.4/Documentation/media/uapi/dvb/
Ddvb-fe-read-status.rst13 Querying frontend status and statistics
18 tuner lock status and provide statistics about the quality of the
24 Signal statistics are provided via
29 Most statistics require the demodulator to be fully locked
31 :ref:`Frontend statistics indicators <frontend-stat-properties>` for
Dfe-get-property.rst46 ``FE_GET_PROPERTY`` ioctls. The supported properties and statistics
66 - This ioctl is used to get properties and statistics from the
69 - No properties are changed, and statistics aren't reset.
/Linux-v5.4/Documentation/locking/
Dlockstat.rst8 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.
184 Line 48 shows statistics for the second subclass (/1) of &rq->lock class
[all …]
/Linux-v5.4/Documentation/cpu-freq/
Dcpufreq-stats.txt2 CPU frequency and voltage scaling statistics in the Linux(TM) kernel
20 cpufreq-stats is a driver that provides CPU frequency statistics for each CPU.
21 These statistics are provided in /sysfs as a bunch of read_only interfaces. This
24 Various statistics will form read_only files under this directory.
32 cpufreq stats provides following statistics (explained in detail below).
37 All the statistics will be from the time the stats driver has been inserted
117 [*] CPU frequency translation statistics
123 "CPU frequency translation statistics" (CONFIG_CPU_FREQ_STAT) provides the
124 statistics which includes time_in_state, total_trans and trans_table.
127 will be able to see the CPU frequency statistics in /sysfs.
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Dstatistics.rst2 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 …]
/Linux-v5.4/Documentation/powerpc/
Dvcpudispatch_stats.txt11 /proc/powerpc/vcpudispatch_stats can be used to obtain statistics
13 collecting the statistics, while writing '0' disables the statistics.
18 The statistics themselves are available by reading the procfs file
23 1. total vcpu dispatches since the beginning of statistics collection
34 The final 3 numbers represent statistics in relation to the home node of
61 statistics were enabled. 4126 of those dispatches were on the same
/Linux-v5.4/Documentation/ABI/stable/
Dsysfs-bus-xen-backend34 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
/Linux-v5.4/drivers/net/wireless/intel/iwlwifi/dvm/
Drx.c155 le32_to_cpu(priv->statistics.rx_ofdm.plcp_err) + in iwlagn_good_plcp_health()
157 le32_to_cpu(priv->statistics.rx_ofdm_ht.plcp_err); in iwlagn_good_plcp_health()
248 rx_info = &priv->statistics.rx_non_phy; in iwlagn_rx_calc_noise()
316 accum_stats((__le32 *)&priv->statistics._name, \ in iwlagn_accumulative_statistics()
367 spin_lock(&priv->statistics.lock); in iwlagn_rx_statistics()
383 priv->statistics.num_bt_kills = stats->rx.general.num_bt_kills; in iwlagn_rx_statistics()
384 le32_add_cpu(&priv->statistics.accum_num_bt_kills, in iwlagn_rx_statistics()
402 spin_unlock(&priv->statistics.lock); in iwlagn_rx_statistics()
406 change = common->temperature != priv->statistics.common.temperature || in iwlagn_rx_statistics()
408 (priv->statistics.flag & STATISTICS_REPLY_FLG_HT40_MODE_MSK); in iwlagn_rx_statistics()
[all …]
Dcalib.c670 spin_lock_bh(&priv->statistics.lock); in iwl_sensitivity_calibration()
671 rx_info = &priv->statistics.rx_non_phy; in iwl_sensitivity_calibration()
672 ofdm = &priv->statistics.rx_ofdm; in iwl_sensitivity_calibration()
673 cck = &priv->statistics.rx_cck; in iwl_sensitivity_calibration()
676 spin_unlock_bh(&priv->statistics.lock); in iwl_sensitivity_calibration()
700 spin_unlock_bh(&priv->statistics.lock); in iwl_sensitivity_calibration()
981 spin_lock_bh(&priv->statistics.lock); in iwl_chain_noise_calibration()
983 rx_info = &priv->statistics.rx_non_phy; in iwl_chain_noise_calibration()
987 spin_unlock_bh(&priv->statistics.lock); in iwl_chain_noise_calibration()
994 !!(priv->statistics.flag & STATISTICS_REPLY_FLG_BAND_24G_MSK); in iwl_chain_noise_calibration()
[all …]
/Linux-v5.4/Documentation/media/kapi/
Ddtv-frontend.rst110 :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 …]
/Linux-v5.4/tools/kvm/kvm_stat/
Dkvm_stat.txt58 Press any other key to refresh statistics immediately.
73 retrieve statistics from tracepoints
77 retrieve statistics from debugfs
85 limit statistics to one virtual machine (pid)
89 limit statistics to one virtual machine (guest name)
/Linux-v5.4/drivers/base/
Dtransport_class.c158 if (!error && tcont->statistics) in transport_add_class_device()
159 error = sysfs_create_group(&classdev->kobj, tcont->statistics); in transport_add_class_device()
225 if (tcont->statistics) in transport_remove_classdev()
226 sysfs_remove_group(&classdev->kobj, tcont->statistics); in transport_remove_classdev()
/Linux-v5.4/Documentation/media/uapi/v4l/
Dpixfmt-meta-intel-ipu3.rst35 3A statistics
38 The IPU3 ImgU 3A statistics accelerators collect different statistics over
39 an input Bayer frame. Those statistics are obtained from the "ipu3-imgu [01] 3a
44 The statistics collected are AWB (Auto-white balance) RGBS (Red, Green, Blue and
73 Both 3A statistics and pipeline parameters described here are closely tied to
/Linux-v5.4/Documentation/scheduler/
Dsched-stats.rst17 statistics for each cpu listed, and there may well be more than one
37 CPU statistics
45 Next three are schedule() statistics:
52 Next two are try_to_wake_up() statistics:
57 Next three are statistics describing scheduling latency:
65 Domain statistics
75 The next 24 are a variety of load_balance() statistics in grouped into types
126 Next three are active_load_balance() statistics:
132 Next three are sched_balance_exec() statistics:
138 Next three are sched_balance_fork() statistics:
[all …]
/Linux-v5.4/Documentation/networking/
Dgen_stats.txt1 Generic networking statistics for netlink users
8 gnet_stats_basic TCA_STATS_BASIC Basic statistics
10 gnet_stats_queue TCA_STATS_QUEUE Queue statistics
24 Update statistics, in dequeue() methods only, (while owning qdisc->running)
74 Locks are taken before writing and released once all statistics have
/Linux-v5.4/Documentation/block/
Dstat.rst2 Block layer statistics in /sys/block/<dev>/stat
7 The stat file provides several statistics about the state of block
11 Why are there multiple statistics in a single file? Doesn't sysfs
15 By having a single file, the kernel can guarantee that the statistics
17 statistics were exported as multiple files containing one statistic
/Linux-v5.4/Documentation/media/v4l-drivers/
Domap3isp.rst76 statistics (AEWB, AF and histogram) subdevs.
88 Each of the statistics subdevs is able to produce events. An event is
89 generated whenever a statistics buffer can be dequeued by a user space
98 ioctls. If there is an error calculating the statistics, there will be an
99 event as usual, but no related statistics buffer. In this case
109 statistics collection are examples of such.
196 The statistics subdevs do offer more dynamic configuration options than the
200 The statistics blocks always get the input image data from the CCDC (as the
201 histogram memory read isn't implemented). The statistics are dequeueable by
202 the user from the statistics subdev nodes using private IOCTLs.
/Linux-v5.4/Documentation/admin-guide/
Diostats.rst2 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 eleven fields of statistics, each meaning exactly the same things.
131 almost a non-issue. When the statistics are read, the per-CPU counters
144 in 2.4. Consequently, you'll see a different statistics output on 2.6+ for
176 disk and partition statistics are consistent again. Since we still don't
192 In 2.6+, all disk statistics were removed from ``/proc/stat``. In 2.4, they
/Linux-v5.4/tools/perf/Documentation/
Dperf-kmem.txt20 'perf kmem stat' to report kernel memory statistics.
37 Show per-callsite statistics
40 Show per-allocation statistics

123456789