Searched refs:ordering (Results 1 – 25 of 55) sorted by relevance
123
| /linux-3.4.99/arch/arm/lib/ |
| D | findbit.S | 107 1: eor r3, r2, #0x18 @ big endian byte ordering
125 eor r3, r2, #0x18 @ big endian byte ordering
141 1: eor r3, r2, #0x18 @ big endian byte ordering
159 eor r3, r2, #0x18 @ big endian byte ordering
|
| /linux-3.4.99/Documentation/arm/Samsung-S3C24XX/ |
| D | DMA.txt | 21 DMA code can be given a DMA ordering structure which
36 to register a complete ordering set. The routine will
|
| /linux-3.4.99/Documentation/networking/ |
| D | x25-iface.txt | 77 - With Linux 2.4.x (and above) SMP kernels, packet ordering is not
91 SMP re-ordering will not occur if the driver's interrupt handler is
|
| D | dm9000.txt | 29 These resources should be specified in that order, as the ordering of the
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | inotify.txt | 232 - There would be no way to get event ordering. Events on file foo and
234 which happened first. A single queue trivially gives you ordering. Such
235 ordering is crucial to existing applications such as Beagle. Imagine
236 "mv a b ; mv b a" events without ordering.
|
| D | sysv-fs.txt | 47 * Byte ordering of "short" (16 bit entities) on disk:
54 * Byte ordering of "long" (32 bit entities) on disk:
|
| D | directory-locking | 44 First of all, at any moment we have a partial ordering of the
47 That ordering can change. However, the following is true:
|
| D | ext3.txt | 46 data=writeback Data ordering is not preserved, data may be written
67 Write barriers enforce proper on-disk ordering
|
| D | ocfs2.txt | 61 data=writeback Data ordering is not preserved, data may be written
|
| D | ext4.txt | 101 the ordering)
168 data=writeback Data ordering is not preserved, data may be written
189 Write barriers enforce proper on-disk ordering
|
| /linux-3.4.99/Documentation/ |
| D | lockdep-design.txt | 136 cases there is an inherent "natural" ordering between the two objects
144 lock, the lock ordering is fully correct. The validator does not
145 automatically detect this natural ordering, as the locking rule behind
146 the ordering is not static.
|
| D | memory-barriers.txt | 53 (*) Assumed minimum execution ordering model.
102 abstract CPU, memory operation ordering is very relaxed, and a CPU may actually
272 ordering over the memory operations on either side of the barrier.
294 A write barrier is a partial ordering on stores only; it is not required
314 A data dependency barrier is a partial ordering on interdependent loads
328 showing the ordering constraints.
348 A read barrier is a partial ordering on loads only; it is not required to
365 A general memory barrier is a partial ordering over both loads and stores.
772 then the partial ordering imposed by CPU 1 will be perceived correctly by CPU
966 Transitivity is a deeply intuitive notion about ordering that is not
[all …]
|
| D | workqueue.txt | 269 Some users depend on the strict execution ordering of ST wq. The
273 the same ordering property as ST wq.
366 * Unless strict ordering is required, there is no need to use ST wq.
|
| D | svga.txt | 95 After scanning, the mode ordering is a bit different: the auto-detected SVGA
170 for more info on mode ordering). However, in very strange cases it's possible
|
| D | padata.txt | 5 parallel on multiple CPUs while retaining the ordering of tasks. It was
|
| /linux-3.4.99/Documentation/scsi/ |
| D | scsi.txt | 22 will enforce the correct ordering of loading and unloading modules in
|
| /linux-3.4.99/Documentation/infiniband/ |
| D | core_locking.txt | 63 simultaneously. However, the ordering of the work completion
|
| /linux-3.4.99/Documentation/timers/ |
| D | hrtimers.txt | 90 another basic requirement was the immediate enqueueing and ordering of
95 file systems. The rbtree is solely used for time sorted ordering, while
|
| /linux-3.4.99/arch/arm/mm/ |
| D | cache-v7.S | 45 dmb @ ensure ordering with previous memory accesses
|
| /linux-3.4.99/Documentation/x86/ |
| D | earlyprintk.txt | 88 specify the correct EHCI debug controller number. The ordering
|
| /linux-3.4.99/Documentation/video4linux/ |
| D | w9968cf.txt | 313 1 = use RGB component ordering.
314 0 = use BGR component ordering.
|
| /linux-3.4.99/Documentation/usb/ |
| D | dma.txt | 57 force a consistent memory access ordering by using memory barriers. It's
|
| /linux-3.4.99/arch/x86/ |
| D | Kconfig.cpu | 323 bool "PentiumPro memory ordering errata workaround"
327 memory operations to violate the x86 ordering standard in rare cases.
|
| /linux-3.4.99/fs/jffs2/ |
| D | README.Locking | 71 No ordering rules have been made for doing so.
|
| /linux-3.4.99/tools/perf/Documentation/ |
| D | perf-script.txt | 113 Do various checks like samples ordering and lost events.
|
123