/linux-3.4.99/Documentation/block/ |
D | writeback_cache_control.txt | 9 write back caches. That means the devices signal I/O completion to the 60 devices with volatile caches need to implement the support for these 67 For devices that do not support volatile write caches there is no driver 70 requests that have a payload. For devices with volatile write caches the 71 driver needs to tell the block layer that it supports flushing caches by
|
D | 00-INDEX | 18 - Control of volatile write back caches
|
/linux-3.4.99/arch/arm/boot/compressed/ |
D | head-xscale.S | 27 mcr p15, 0, r0, c7, c7, 0 @ flush I & D caches 29 @ disabling MMU and caches
|
/linux-3.4.99/arch/arm/mm/ |
D | proc-arm720.S | 60 mcr p15, 0, r0, c1, c0, 0 @ disable caches 124 mcr p15, 0, r0, c7, c7, 0 @ invalidate caches 152 mcr p15, 0, r0, c7, c7, 0 @ invalidate caches
|
D | proc-sa110.S | 52 mcr p15, 0, r0, c1, c0, 0 @ disable caches 68 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 167 mcr p15, 0, r10, c7, c7 @ invalidate I,D caches on v4
|
D | proc-fa526.S | 44 mcr p15, 0, r0, c1, c0, 0 @ disable caches 63 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 145 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-arm926.S | 67 mcr p15, 0, r0, c1, c0, 0 @ disable caches 83 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 414 mcr p15, 0, ip, c7, c7, 0 @ invalidate I+D caches 429 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 437 mov r0, #4 @ disable write-back on caches explicitly
|
D | proc-sa1100.S | 60 mcr p15, 0, r0, c1, c0, 0 @ disable caches 76 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 206 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-arm920.S | 75 mcr p15, 0, r0, c1, c0, 0 @ disable caches 91 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 399 mcr p15, 0, ip, c7, c7, 0 @ invalidate I+D caches 414 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-arm740.S | 44 mcr p15, 0, r0, c1, c0, 0 @ disable caches 68 mcr p15, 0, r0, c7, c0, 0 @ invalidate caches
|
D | proc-arm925.S | 98 mcr p15, 0, r0, c1, c0, 0 @ disable caches 123 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 451 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4 458 mov r0, #4 @ disable write-back on caches explicitly
|
D | proc-mohawk.S | 57 mcr p15, 0, r0, c1, c0, 0 @ disable caches 75 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 352 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches
|
D | proc-arm1026.S | 74 mcr p15, 0, r0, c1, c0, 0 @ disable caches 90 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 401 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-arm922.S | 77 mcr p15, 0, r0, c1, c0, 0 @ disable caches 93 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 392 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-arm1022.S | 74 mcr p15, 0, r0, c1, c0, 0 @ disable caches 90 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 411 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-arm1020e.S | 85 mcr p15, 0, r0, c1, c0, 0 @ disable caches 101 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 429 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-xsc3.S | 95 mcr p15, 0, r0, c1, c0, 0 @ disable caches 116 mcr p15, 0, ip, c7, c7, 0 @ invalidate L1 caches and BTB 430 mcr p15, 0, ip, c7, c7, 0 @ invalidate I & D caches, BTB 452 mcr p15, 0, ip, c7, c7, 0 @ invalidate L1 caches and BTB
|
D | proc-arm6_7.S | 186 mcr p15, 0, r0, c1, c0, 0 @ disable caches 247 mcr p15, 0, r0, c7, c0 @ flush caches on v3 260 mcr p15, 0, r0, c7, c0 @ flush caches on v3
|
D | proc-arm1020.S | 85 mcr p15, 0, r0, c1, c0, 0 @ disable caches 101 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches 447 mcr p15, 0, r0, c7, c7 @ invalidate I,D caches on v4
|
D | proc-xscale.S | 130 mcr p15, 0, r0, c1, c0, 0 @ disable caches 158 mcr p15, 0, ip, c7, c7, 0 @ invalidate I,D caches & BTB 545 mcr p15, 0, ip, c7, c7, 0 @ invalidate I & D caches, BTB 561 mcr p15, 0, ip, c7, c7, 0 @ invalidate I, D caches & BTB
|
/linux-3.4.99/drivers/scsi/qla2xxx/ |
D | Kconfig | 22 Upon request, the driver caches the firmware image until
|
/linux-3.4.99/Documentation/filesystems/nfs/ |
D | rpc-cache.txt | 8 a wide variety of values to be caches. 10 There are a number of caches that are similar in structure though 12 of common code for managing these caches. 14 Examples of caches that are likely to be needed are: 92 includes it on a list of caches that will be regularly
|
/linux-3.4.99/fs/coda/ |
D | Kconfig | 11 persistent client caches and write back caching.
|
/linux-3.4.99/Documentation/ |
D | cachetlb.txt | 130 us to properly handle systems whose caches are strict and require 138 indexed caches which must be flushed when virtual-->physical 140 indexed physically tagged caches of IA32 processors have no need to 141 implement these interfaces since the caches are fully synchronized 149 the caches. That is, after running, there will be no cache 158 the caches. That is, after running, there will be no cache 165 optimizations for VIPT caches.
|
/linux-3.4.99/arch/unicore32/mm/ |
D | proc-ucv2.S | 49 movc p0.c1, ip, #0 @ disable caches and mmu
|