| /linux-2.6.39/Documentation/powerpc/ |
| D | mpc52xx.txt | 34 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
|
| /linux-2.6.39/Documentation/ |
| 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 | 50 acquisitions - number of times we took the lock
|
| D | hwspinlock.txt | 181 * we took the lock, do our thing now, but do NOT sleep
216 * 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-2.6.39/Documentation/i2c/ |
| D | fault-codes | 119 This is returned by drivers when an operation took too much
122 SMBus adapters may return it when an operation took more
|
| /linux-2.6.39/Documentation/sparc/ |
| D | README-2.5 | 8 developed by Jakub Jelinek (I think... Obviously David S. Miller took
|
| /linux-2.6.39/arch/arm/plat-s3c24xx/ |
| D | dma.c | 164 int took; in s3c2410_dma_waitforload() local
176 took = chan->load_timeout - timeout; in s3c2410_dma_waitforload()
178 s3c2410_dma_stats_timeout(chan->stats, took); in s3c2410_dma_waitforload()
|
| /linux-2.6.39/Documentation/filesystems/caching/ |
| D | fscache.txt | 315 between 0 jiffies and HZ-1 jiffies a variety of tasks took to run. The
321 OP RUNS Length of time a call to process an operation took
322 OBJ RUNS Length of time a call to process an object event took
326 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 | 576 is also possible for the PG_fscache_write bit to be cleared when no write took
|
| /linux-2.6.39/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-2.6.39/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-2.6.39/fs/reiserfs/ |
| D | README | 140 implemented allocate on flush before us for XFS, and generously took
|
| /linux-2.6.39/Documentation/scsi/ |
| D | FlashPoint.txt | 101 message after 11pm one evening, and the meeting took place the next
|
| /linux-2.6.39/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-2.6.39/drivers/infiniband/hw/qib/ |
| D | qib_iba7322.c | 1290 int took, multi, n = 0; in err_decode() local
1303 took = scnprintf(msg, len, "%s", msp->msg); in err_decode()
1304 len -= took; in err_decode()
1305 msg += took; in err_decode()
1316 took = scnprintf(msg, len, "_%d", idx); in err_decode()
1317 len -= took; in err_decode()
1318 msg += took; in err_decode()
|
| /linux-2.6.39/Documentation/trace/ |
| D | ftrace.txt | 888 schedule took place to run sshd. When the interrupts were
889 enabled, we took an interrupt. On return from the interrupt
890 handler, the softirq ran. We took another interrupt while
950 Running this on an idle system, we see that it only took 4
|
| /linux-2.6.39/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-2.6.39/kernel/trace/ |
| D | Kconfig | 483 it recorded and give a rough estimate of how long each iteration took.
|
| /linux-2.6.39/Documentation/serial/ |
| D | specialix.txt | 210 took quite a while to figure out, so I'm not going to delete
|
| /linux-2.6.39/Documentation/crypto/ |
| D | descore-readme.txt | 149 speedups but which did obfuscate everything. so i took the test data
|
| /linux-2.6.39/Documentation/development-process/ |
| D | 5.Posting | 83 discrete, self-contained changes, not the path you took to get to those
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | ext4.txt | 365 number of milliseconds it took to zero out the
|