| /linux-4.4.14/Documentation/device-mapper/ |
| D | statistics.txt | 76 that took 0-10 ms to complete, b is the number of requests
77 that took 10-20 ms to complete, c is the number of requests
78 that took 20-30 ms to complete and d is the number of
79 requests that took more than 30 ms to complete.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | mpc52xx.txt | 34 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
|
| /linux-4.4.14/Documentation/trace/ |
| D | events-nmi.txt | 15 INFO: NMI handler took too long to run: 9.207 msecs
|
| D | ftrace.txt | 1427 the kworker with a nice priority of -20 (not very nice), took
1494 Running this on an idle system, we see that it only took 5 microseconds
|
| /linux-4.4.14/Documentation/i2c/ |
| D | fault-codes | 116 This is returned by drivers when an operation took too much
119 SMBus adapters may return it when an operation took more
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockdep-design.txt | 114 took any hardirq-unsafe lock in the past.
116 - if a new softirq-safe lock is discovered, we check whether it took
120 hardirq-safe lock took it in the past.
123 softirq-safe lock took it in the past.
|
| D | lockstat.txt | 52 acquisitions - number of times we took the lock
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | fscache.txt | 320 between 0 jiffies and HZ-1 jiffies a variety of tasks took to run. The
326 OP RUNS Length of time a call to process an operation took
327 OBJ RUNS Length of time a call to process an object event took
331 Each row shows the number of events that took a particular range of times.
|
| D | cachefiles.txt | 465 between 0 jiffies and HZ-1 jiffies a variety of tasks took to run. The
474 Each row shows the number of events that took a particular range of times.
|
| D | netfs-api.txt | 583 is also possible for the PG_fscache_write bit to be cleared when no write took
|
| /linux-4.4.14/arch/sh/kernel/cpu/sh5/ |
| D | switchto.S | 71 st.q r0, (14*8), r14 ! for unwind, want to look as though we took a trap at
|
| /linux-4.4.14/arch/arm/kernel/ |
| D | entry-header.S | 106 @ of the saved xPSR specifies if stack aligning took place. In this case
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-trace.txt | 145 time it took for fault to be handled!
|
| D | perf-report.txt | 299 This allows to examine the path the program took to each sample.
|
| D | intel-pt.txt | 40 for example two or three orders of magnitude longer than it took to collect.
|
| /linux-4.4.14/Documentation/ |
| D | hwspinlock.txt | 188 * we took the lock, do our thing now, but do NOT sleep
223 * we took the lock, do our thing now, but do NOT sleep
|
| D | robust-futexes.txt | 154 [which it currently does for !pshared robust mutexes], and that took 256
|
| /linux-4.4.14/kernel/trace/ |
| D | Kconfig | 548 it took to write to the tracepoint and the next iteration that
550 will report the time it took to do the previous tracepoint.
580 it recorded and give a rough estimate of how long each iteration took.
|
| /linux-4.4.14/arch/arc/kernel/ |
| D | entry-compact.S | 366 ; Special considerations needed for the context which took L2 intr
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | isp.doc | 108 For example, if the 68060 hardware took a "Unimplemented Integer Instruction"
|
| D | fpsp.doc | 100 For example, if the 68060 hardware took a "Line-F Emulator" exception
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-isku | 95 epoch in which the last configuration took place.
|
| /linux-4.4.14/fs/reiserfs/ |
| D | README | 140 implemented allocate on flush before us for XFS, and generously took
|
| /linux-4.4.14/Documentation/scsi/ |
| D | FlashPoint.txt | 101 message after 11pm one evening, and the meeting took place the next
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 1493 # fmove out took an unimplemented data type exception.
2038 # The opclass two PACKED instruction that took an "Unimplemented Data Type"
2469 # PC of instruction that took the exception is the PC in the frame
2956 # PC of instruction that took the exception is the PC in the frame
3076 # facc_out_{b,w,l}() - store to memory took access error (opcl 3) #
|
| D | fpsp.S | 1494 # fmove out took an unimplemented data type exception.
2039 # The opclass two PACKED instruction that took an "Unimplemented Data Type"
2470 # PC of instruction that took the exception is the PC in the frame
2957 # PC of instruction that took the exception is the PC in the frame
3077 # facc_out_{b,w,l}() - store to memory took access error (opcl 3) #
|
| /linux-4.4.14/drivers/infiniband/hw/qib/ |
| D | qib_iba7322.c | 1380 int took, multi, n = 0; in err_decode() local
1395 took = min_t(size_t, msp->sz - (size_t)1, len); in err_decode()
1396 memcpy(msg, msp->msg, took); in err_decode()
1397 len -= took; in err_decode()
1398 msg += took; in err_decode()
1411 took = scnprintf(msg, len, "_%d", idx); in err_decode()
1412 len -= took; in err_decode()
1413 msg += took; in err_decode()
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 259 The code works, but is not terribly efficient. On my system it took
560 linux code 1 million times, this took about 1 second on my system.
|
| /linux-4.4.14/Documentation/crypto/ |
| D | descore-readme.txt | 149 speedups but which did obfuscate everything. so i took the test data
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 5.Posting | 83 discrete, self-contained changes, not the path you took to get to those
|
| /linux-4.4.14/tools/power/cpupower/po/ |
| D | de.po | 155 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | it.po | 155 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | cs.po | 158 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | fr.po | 155 msgid "%s took %.5f seconds and exited with status %d\n"
|
| D | pt.po | 153 msgid "%s took %.5f seconds and exited with status %d\n"
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | ext4.txt | 339 number of milliseconds it took to zero out the
|
| D | xfs-delayed-logging-design.txt | 176 The solution is relatively simple - it just took a long time to recognise it.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | RTFP.txt | 2343 Day-one bug in Tree RCU that took forever to track down.
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 4563 Laurent Bonnaud <Laurent.Bonnaud at inpg.fr> took the old grotty
|