Home
last modified time | relevance | path

Searched refs:took (Results 1 – 25 of 58) sorted by relevance

123

/linux-6.12.1/Documentation/admin-guide/device-mapper/
Dstatistics.rst82 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-6.12.1/arch/arm/kernel/
Dentry-v7m.S46 @ If we took the interrupt while running in the kernel, we may already
Dentry-header.S107 @ of the saved xPSR specifies if stack aligning took place. In this case
Dentry-armv.S46 @ If we took the interrupt while running in the kernel, we may already
/linux-6.12.1/Documentation/arch/powerpc/
Dmpc52xx.rst38 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
/linux-6.12.1/Documentation/trace/
Devents-nmi.rst17 INFO: NMI handler took too long to run: 9.207 msecs
Dtimerlat-tracer.rst102 thread took 7597 ns, and the qxl:21 device IRQ took 7139 ns. Finally,
103 the cc1 thread noise took 9909 ns of time before the context switch.
Dosnoise-tracer.rst167 it took place one millisecond before.
/linux-6.12.1/Documentation/i2c/
Dfault-codes.rst128 This is returned by drivers when an operation took too much
131 SMBus adapters may return it when an operation took more
/linux-6.12.1/Documentation/userspace-api/media/v4l/
Dvidioc-g-ctrl.rst93 applications took over control of the device function this control
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/ti/
Dcpsw.rst271 // (I took at https://www.spinics.net/lists/netdev/msg460869.html)
278 // (I took at https://www.spinics.net/lists/netdev/msg460869.html)
558 // (I took at https://www.spinics.net/lists/netdev/msg460869.html)
/linux-6.12.1/Documentation/locking/
Dlockstat.rst66 - number of times we took the lock
Dlockdep-design.rst176 took any hardirq-unsafe lock in the past.
178 - if a new softirq-safe lock is discovered, we check whether it took
182 hardirq-safe lock took it in the past.
185 softirq-safe lock took it in the past.
Dhwspinlock.rst353 * we took the lock, do our thing now, but do NOT sleep
388 * we took the lock, do our thing now, but do NOT sleep
/linux-6.12.1/arch/arc/kernel/
Dentry-compact.S337 ; Special considerations needed for the context which took L2 intr
/linux-6.12.1/arch/m68k/ifpsp060/
Dfpsp.doc100 For example, if the 68060 hardware took a "Line-F Emulator" exception
Disp.doc108 For example, if the 68060 hardware took a "Unimplemented Integer Instruction"
/linux-6.12.1/Documentation/ABI/obsolete/
Dsysfs-driver-hid-roccat-isku95 epoch in which the last configuration took place.
/linux-6.12.1/fs/reiserfs/
DREADME130 implemented allocate on flush before us for XFS, and generously took
/linux-6.12.1/Documentation/arch/x86/
Dmicrocode.rst138 While this took care of device or external interrupts, IPIs including
/linux-6.12.1/Documentation/scsi/
DFlashPoint.rst114 message after 11pm one evening, and the meeting took place the next
/linux-6.12.1/Documentation/admin-guide/media/
Ddvb_intro.rst165 Here's the output of the dvbv5 tools from a channel scan took from
/linux-6.12.1/arch/m68k/ifpsp060/src/
Dpfpsp.S1493 # 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-6.12.1/drivers/infiniband/hw/qib/
Dqib_iba7322.c1350 int took, multi, n = 0; in err_decode() local
1364 took = min_t(size_t, msp->sz - (size_t)1, len); in err_decode()
1365 memcpy(msg, msp->msg, took); in err_decode()
1366 len -= took; in err_decode()
1367 msg += took; in err_decode()
1380 took = scnprintf(msg, len, "_%d", idx); in err_decode()
1381 len -= took; in err_decode()
1382 msg += took; in err_decode()
/linux-6.12.1/kernel/trace/
DKconfig885 it took to write to the tracepoint and the next iteration that
887 will report the time it took to do the previous tracepoint.
917 it recorded and give a rough estimate of how long each iteration took.

123