| /linux-4.4.14/Documentation/usb/ |
| D | dwc3.txt | 9 until the command completes which is bad.
20 until the command completes.
|
| D | dma.txt | 113 each time an urb completes and then re-map it on during resubmission.
|
| /linux-4.4.14/Documentation/block/ |
| D | stat.txt | 38 These values increment when an I/O request completes.
52 counters are incremented when the I/O completes.
|
| D | writeback_cache_control.txt | 68 support required, the block layer completes empty REQ_FLUSH requests before
|
| D | biovecs.txt | 78 still using it, in case the original bio completes first, though. Using
|
| D | biodoc.txt | 567 end_that_request_first, i.e. every time the driver completes a part of the
880 to continue to use the vector descriptor (kvec) after i/o completes. Instead,
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | kcopyd.txt | 38 When the copy completes, kcopyd will call the user's completion routine,
|
| D | log-writes.txt | 21 This works by attaching all WRITE requests to a list once the write completes.
23 the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only
|
| D | snapshot.txt | 109 merging snapshot after it completes. The "snapshot" that hands over its
|
| /linux-4.4.14/drivers/staging/lustre/lustre/lov/ |
| D | lov_request.c | 79 int completes = atomic_read(&set->set_completes); in lov_set_finished() local
81 CDEBUG(D_INFO, "check set %d/%d\n", completes, set->set_count); in lov_set_finished()
83 if (completes == set->set_count) { in lov_set_finished()
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | gpio-restart.txt | 18 restart handler completes allowing other restart handlers to be attempted.
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 85 will be compacted. When it completes, memory will be freed
|
| /linux-4.4.14/Documentation/fb/ |
| D | deferred_io.txt | 19 completes the work associated with updating the framebuffer. this is
|
| /linux-4.4.14/drivers/gpu/drm/msm/ |
| D | NOTES | 22 pageflip after rendering completes (ie. have the kms/crtc code build
|
| /linux-4.4.14/Documentation/RCU/ |
| D | NMI-RCU.txt | 82 of it completes on all other CPUs.
|
| D | whatisRCU.txt | 181 section completes. For one thing, there might well be scheduling
|
| /linux-4.4.14/Documentation/virtual/kvm/arm/ |
| D | vgic-mapped-irqs.txt | 72 when the host ISR completes, but leaves the interrupt active until the guest
107 this information until the guest ISR completes. Therefore, the HW
|
| /linux-4.4.14/Documentation/arm/ |
| D | Interrupts | 156 "simple" handler (not "edge" nor "level"). After the handler completes,
|
| /linux-4.4.14/Documentation/ |
| D | kernel-per-CPU-kthreads.txt | 72 2. Build with CONFIG_HOTPLUG_CPU=y. After boot completes, force
128 2. Build with CONFIG_HOTPLUG_CPU=y. Once boot completes, force the
|
| D | padata.txt | 139 the previous one completes. When a task does complete, parallel() (or
|
| D | memory-barriers.txt | 378 time the barrier completes, the effects of all the stores prior to that
437 happen after it completes.
452 happen before it completes.
784 assertion can fail after the combined three-CPU example completes. If you
1128 before the read barrier completes anyway:
|
| D | xillybus.txt | 166 that read() or write() completes less bytes than requested. There is a
|
| D | md.txt | 565 A 'select' on this attribute will return when resync completes,
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | xfs-delayed-logging-design.txt | 82 the current batch completes. It is now common for a single current CPU core to
259 and then moved forward in the AIL when the log buffer IO completes for that
448 checkpoint commit completes, it is removed from the committing list. Because
594 counts, but as each checkpoint completes the pin count will retain the correct
707 <log buffer IO completes>
764 <log buffer IO completes>
|
| D | xfs.txt | 221 operation (create, unlink, etc) completes, the change to the
|
| D | autofs4-mount-control.txt | 131 a mount or expire operation completes a status is returned to the
|
| D | ext4.txt | 367 completes. This approach allows ext4 code to avoid
|
| D | vfs.txt | 614 or asynchronously when the write operation completes.
627 unlocked and marked uptodate once the read completes.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | transactional_memory.txt | 49 example, the transaction completes as though it were normal straight-line code
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | object.txt | 197 The cache should call fscache_obtained_object() if creation completes
|
| /linux-4.4.14/Documentation/nvdimm/ |
| D | btt.txt | 125 old_map : The old postmap ABA - after 'this' write completes, this will be a
|
| /linux-4.4.14/Documentation/networking/ |
| D | rds.txt | 116 operation completes). These notifications are received through
|
| /linux-4.4.14/Documentation/serial/ |
| D | tty.txt | 42 completes successfully. Should initialize any
|
| /linux-4.4.14/Documentation/scsi/ |
| D | st.txt | 196 itself is not added to the statistics until it completes.
208 updated and decremented when an I/O completes after updating statistics.
|
| D | scsi_eh.txt | 272 4. EH completes
|
| D | scsi_fc_transport.txt | 414 datastructures and references. If the LLDD completes successfully,
|
| D | ChangeLog.megaraid | 343 completes.
|
| D | ChangeLog.lpfc | 32 interpretation of stale sense length when the command completes
367 properly after ADISC handling completes.
638 (i.e. LOGO) before our FLOGI completes it should be LS_RJT'ed.
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | README.DAC960 | 553 Finally, the rebuild completes successfully. The driver logs the status of the
688 Finally, the rebuild completes successfully. The driver logs the status of the
|
| /linux-4.4.14/Documentation/s390/ |
| D | cds.txt | 272 When the I/O request completes, the CDS first level interrupt handler will
|
| /linux-4.4.14/Documentation/ioctl/ |
| D | hdio.txt | 669 {io|hob}_ports[] after the command completes iff one of the
|
| /linux-4.4.14/Documentation/input/ |
| D | atarikbd.txt | 172 keyboard error). If the controller self-test completes without error, the code
|
| /linux-4.4.14/arch/arm/mm/ |
| D | Kconfig | 947 the store buffer still remains when the operation completes.
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic7xxx.seq | 915 * completes or the target changes phase.
991 * correct value when the DMA completes. If the next
|
| D | aic79xx.seq | 1686 * completes or the target changes phase. Both conditions
1817 * correct value when the DMA completes. If the next
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | res_func.S | 6 | machine and the 040 completes the operation. This routine
|
| /linux-4.4.14/Documentation/power/ |
| D | devices.txt | 641 gives one example: after the suspend sequence completes, a non-legacy
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig | 1175 which starts prior to an ASID switch but completes afterwards. This
|