Searched refs:took (Results 1 – 25 of 46) sorted by relevance
12
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 82 that took 0-10 ms to complete, b is the number of requests
83 that took 10-20 ms to complete, c is the number of requests
84 that took 20-30 ms to complete and d is the number of
85 requests that took more than 30 ms to complete.
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | mpc52xx.rst | 38 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
|
| /Linux-v5.4/Documentation/trace/ |
| D | events-nmi.rst | 17 INFO: NMI handler took too long to run: 9.207 msecs
|
| /Linux-v5.4/Documentation/i2c/ |
| D | fault-codes.rst | 124 This is returned by drivers when an operation took too much
127 SMBus adapters may return it when an operation took more
|
| /Linux-v5.4/Documentation/locking/ |
| D | lockdep-design.rst | 173 took any hardirq-unsafe lock in the past.
175 - if a new softirq-safe lock is discovered, we check whether it took
179 hardirq-safe lock took it in the past.
182 softirq-safe lock took it in the past.
|
| D | lockstat.rst | 66 - number of times we took the lock
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-g-ctrl.rst | 102 applications took over control of the device function this control
|
| /Linux-v5.4/Documentation/networking/device_drivers/ti/ |
| D | cpsw.txt | 248 // (I took at https://www.spinics.net/lists/netdev/msg460869.html)
254 // (I took at https://www.spinics.net/lists/netdev/msg460869.html)
513 // (I took at https://www.spinics.net/lists/netdev/msg460869.html)
|
| /Linux-v5.4/arch/sh/kernel/cpu/sh5/ |
| D | switchto.S | 68 st.q r0, (14*8), r14 ! for unwind, want to look as though we took a trap at
|
| /Linux-v5.4/arch/arm/kernel/ |
| D | entry-header.S | 107 @ of the saved xPSR specifies if stack aligning took place. In this case
|
| /Linux-v5.4/arch/arc/kernel/ |
| D | entry-compact.S | 352 ; Special considerations needed for the context which took L2 intr
|
| /Linux-v5.4/Documentation/ |
| D | hwspinlock.txt | 342 * we took the lock, do our thing now, but do NOT sleep
377 * we took the lock, do our thing now, but do NOT sleep
|
| D | robust-futexes.txt | 158 [which it currently does for !pshared robust mutexes], and that took 256
|
| /Linux-v5.4/arch/m68k/ifpsp060/ |
| D | fpsp.doc | 100 For example, if the 68060 hardware took a "Line-F Emulator" exception
|
| D | isp.doc | 108 For example, if the 68060 hardware took a "Unimplemented Integer Instruction"
|
| /Linux-v5.4/kernel/trace/ |
| D | Kconfig | 684 it took to write to the tracepoint and the next iteration that
686 will report the time it took to do the previous tracepoint.
716 it recorded and give a rough estimate of how long each iteration took.
|
| /Linux-v5.4/Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-isku | 95 epoch in which the last configuration took place.
|
| /Linux-v5.4/Documentation/scsi/ |
| D | FlashPoint.txt | 101 message after 11pm one evening, and the meeting took place the next
|
| /Linux-v5.4/fs/reiserfs/ |
| D | README | 140 implemented allocate on flush before us for XFS, and generously took
|
| /Linux-v5.4/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) #
|
| /Linux-v5.4/drivers/infiniband/hw/qib/ |
| D | qib_iba7322.c | 1372 int took, multi, n = 0; in err_decode() local
1386 took = min_t(size_t, msp->sz - (size_t)1, len); in err_decode()
1387 memcpy(msg, msp->msg, took); in err_decode()
1388 len -= took; in err_decode()
1389 msg += took; in err_decode()
1402 took = scnprintf(msg, len, "_%d", idx); in err_decode()
1403 len -= took; in err_decode()
1404 msg += took; in err_decode()
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-trace.txt | 248 time it took for fault to be handled!
|
| /Linux-v5.4/Documentation/driver-api/mtd/ |
| D | nand_ecc.rst | 282 The code works, but is not terribly efficient. On my system it took
594 linux code 1 million times, this took about 1 second on my system.
|
12
