Home
last modified time | relevance | path

Searched refs:spent (Results 1 – 41 of 41) sorted by relevance

/linux-4.4.14/Documentation/ABI/testing/
Dprocfs-diskstats14 7 - time spent reading (ms)
18 11 - time spent writing (ms)
20 13 - time spent doing I/Os (ms)
21 14 - weighted time spent doing I/Os (ms)
Dsysfs-block10 4 - time spent reading (ms)
14 8 - time spent writing (ms)
16 10 - time spent doing I/Os (ms)
17 11 - weighted time spent doing I/Os (ms)
154 being spent in the kernel. This allows one to turn off
Dsysfs-class-scsi_tape16 Shows the total amount of time spent waiting for all I/O
23 To determine the amount of time spent waiting for other I/O
Dsysfs-class-devfreq52 specific device. It shows the time spent in each state and
/linux-4.4.14/Documentation/device-mapper/
Dstatistics.txt16 provided: total time spent reading and writing. When the histogram
156 4. the number of milliseconds spent reading
160 8. the number of milliseconds spent writing
162 10. the number of milliseconds spent doing I/Os
163 11. the weighted number of milliseconds spent doing I/Os
166 12. the total time spent reading in milliseconds
167 13. the total time spent writing in milliseconds
/linux-4.4.14/Documentation/
Diostats.txt69 Field 4 -- # of milliseconds spent reading
70 This is the total number of milliseconds spent by all reads (as
78 Field 8 -- # of milliseconds spent writing
79 This is the total number of milliseconds spent by all writes (as
84 Field 10 -- # of milliseconds spent doing I/Os
86 Field 11 -- weighted # of milliseconds spent doing I/Os
89 (field 9) times the number of milliseconds spent doing I/O since the
Dcpu-load.txt6 the average time system spent in a particular state, for example:
17 system spent 10.01% of the time doing work in user space, 2.92% in the
Dirqflags-tracing.txt35 irq-flags-tracing is spent in this state: look at the lockdep
/linux-4.4.14/Documentation/cgroups/
Dcpuacct.txt37 user: Time spent by tasks of the cgroup in user mode.
38 system: Time spent by tasks of the cgroup in kernel mode.
Dblkio-controller.txt225 - Total amount of time the IOs for this cgroup spent waiting in the
228 measure of total time the cgroup spent waiting but rather a measure of
230 this metric does not include the time spent waiting for service once
260 cumulative total of the amount of time spent by each IO in that cgroup
270 spent idling for one of the queues of the cgroup. This is in
277 This is the amount of time spent by the IO scheduler idling for a
/linux-4.4.14/Documentation/scheduler/
Dsched-stats.txt51 7) sum of all time spent running by tasks on this processor (in jiffies)
52 8) sum of all time spent waiting to run by tasks on this processor (in
146 1) time spent on the cpu
147 2) time spent waiting on a runqueue
Dsched-rt-group.txt52 CPU time is divided by means of specifying how much time can be spent running
Dsched-design-CFS.txt77 for": the (small) time it just spent using the physical CPU is added to
/linux-4.4.14/Documentation/cpu-freq/
Dcpufreq-stats.txt53 This gives the amount of time spent in each of the frequencies supported by
55 will mean this CPU spent <time> usertime units of time at <frequency>. Output
/linux-4.4.14/arch/powerpc/
DKconfig.debug44 the amount of time spent in hypervisor calls. Wall time spent in
45 each call is always calculated, and if available CPU cycles spent
/linux-4.4.14/drivers/net/ethernet/sfc/
Defx.c249 int spent; in efx_process_channel() local
259 spent = efx_nic_process_eventq(channel, budget); in efx_process_channel()
260 if (spent && efx_channel_has_rx_queue(channel)) { in efx_process_channel()
276 return spent; in efx_process_channel()
289 int spent; in efx_poll() local
298 spent = efx_process_channel(channel, budget); in efx_poll()
300 if (spent < budget) { in efx_poll()
334 return spent; in efx_poll()
Dfarch.c1288 int spent = 0; in efx_farch_ev_process() local
1291 return spent; in efx_farch_ev_process()
1317 if (++spent == budget) in efx_farch_ev_process()
1324 spent = budget; in efx_farch_ev_process()
1357 return spent; in efx_farch_ev_process()
Def10.c2661 int spent = 0; in efx_ef10_ev_process() local
2664 return spent; in efx_ef10_ev_process()
2690 spent += efx_ef10_handle_rx_event(channel, &event); in efx_ef10_ev_process()
2691 if (spent >= quota) { in efx_ef10_ev_process()
2695 spent = quota; in efx_ef10_ev_process()
2702 spent = quota; in efx_ef10_ev_process()
2704 } else if (++spent == quota) { in efx_ef10_ev_process()
2710 if (++spent == quota) in efx_ef10_ev_process()
2727 return spent; in efx_ef10_ev_process()
/linux-4.4.14/fs/btrfs/
DKconfig56 plenty of additional CPU cycles are spent. Enabling this
/linux-4.4.14/Documentation/cpuidle/
Dsysfs.txt83 * time : Total time spent in this idle state (in microseconds)
/linux-4.4.14/tools/perf/Documentation/
Dperf-timechart.txt30 There are also poll bars which show how much time application spent
/linux-4.4.14/Documentation/locking/
Dlockstat.txt50 avg - average time spent waiting on this lock
/linux-4.4.14/arch/powerpc/kvm/
DKconfig118 exit, and interrupt handling code, plus time spent in the guest
/linux-4.4.14/Documentation/scsi/
Din2000.txt137 spent a lot of time testing this. You might try 'ENABLE_CLUSTERING'
Dst.txt175 2. io_ns - The amount of time spent waiting (in nanoseconds) for all I/O
184 6. read_ns - The amount of time (in nanoseconds) spent waiting for read
188 9. write_ns - The amount of time (in nanoseconds) spent waiting for write
Dncr53c8xx.txt413 Example above: 369.94 seconds spent for data transfer
417 Example above: 183.09 seconds spent disconnected
422 Example above: 1.32 seconds spent for post processing
/linux-4.4.14/Documentation/filesystems/
Dxfs-self-describing-metadata.txt45 Hence most of the time spent on forensic analysis is spent doing basic
Dntfs.txt73 (from 9:43 minutes on average down to 7:53). The time spent in user space
74 was unchanged but the time spent in the kernel was decreased by a factor of
Dproc.txt323 blkio_ticks time spent waiting for block IO
1291 lines. These numbers identify the amount of time the CPU has spent performing
Dxfs-delayed-logging-design.txt141 no time is spent in this document trying to convince the reader that the
/linux-4.4.14/Documentation/timers/
Dhrtimers.txt14 to solve this'), and spent a considerable effort trying to integrate
/linux-4.4.14/kernel/trace/
DKconfig177 This option measures the time spent in irqs-off critical
201 This option measures the time spent in preemption-off critical
/linux-4.4.14/Documentation/trace/
Dtracepoint-analysis.txt323 At a glance, it looks like the time is being spent copying pixmaps to
Dftrace.txt254 track of the time spent in those functions. The histogram
/linux-4.4.14/Documentation/development-process/
D4.Coding252 should not be used all of the time. But some time spent learning the
307 Some time spent installing and using these compilers will help avoid
D3.Early-stage6 line of code is written. Some time spent in early planning and
D5.Posting122 done. When done properly, though, it is time well spent.
/linux-4.4.14/Documentation/vm/
Dtranshuge.txt263 tracer to record how long was spent in __alloc_pages_nodemask and
/linux-4.4.14/Documentation/mtd/
Dnand_ecc.txt706 again there are also much less cycles spent there.
/linux-4.4.14/init/
DKconfig346 statistics about user, system and idle time spent on per jiffies
440 Collect information on time spent by a task waiting for system
/linux-4.4.14/arch/x86/
DKconfig721 accounting. Time spent executing other tasks in parallel with