/linux-4.1.27/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-4.1.27/Documentation/filesystems/ |
D | inotify.txt | 41 - There would be no way to get event ordering. Events on file foo and 43 which happened first. A single queue trivially gives you ordering. Such 44 ordering is crucial to existing applications such as Beagle. Imagine 45 "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 | 51 First of all, at any moment we have a partial ordering of the 54 That ordering can change. However, the following is true:
|
D | ext3.txt | 47 data=writeback Data ordering is not preserved, data may be written 68 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) 169 data=writeback Data ordering is not preserved, data may be written 190 Write barriers enforce proper on-disk ordering
|
D | xfs-delayed-logging-design.txt | 276 transactional integrity (as discussed in the next section) so the ordering is 621 3. Checkpoint commit ordering 661 The final serialisation point is the checkpoint commit record ordering code 664 an ordering loop after writing all the log vectors into the log buffers but
|
D | f2fs.txt | 138 but f2fs still guarantees the write ordering of all the
|
D | relay.txt | 276 mainly in seeing the relative ordering of system-wide events without
|
/linux-4.1.27/Documentation/devicetree/bindings/serial/ |
D | vt8500-uart.txt | 15 Aliases may be defined to ensure the correct ordering of the uarts.
|
D | qcom,msm-uartdm.txt | 30 Note: Aliases may be defined to ensure the correct ordering of the UARTs.
|
/linux-4.1.27/Documentation/ |
D | circular-buffers.txt | 163 /* The spin_unlock() and next spin_lock() provide needed ordering. */ 187 is actually awakened. We therefore cannot rely on it for ordering. However, 192 ordering between the read of the index indicating that the consumer has 234 prevents the compiler from tearing the store, and enforces ordering
|
D | memory-barriers.txt | 53 (*) Assumed minimum execution ordering model. 102 abstract CPU, memory operation ordering is very relaxed, and a CPU may actually 327 ordering over the memory operations on either side of the barrier. 349 A write barrier is a partial ordering on stores only; it is not required 369 A data dependency barrier is a partial ordering on interdependent loads 383 showing the ordering constraints. 403 A read barrier is a partial ordering on loads only; it is not required to 420 A general memory barrier is a partial ordering over both loads and stores. 617 However, stores are not speculated. This means that ordering -is- provided 629 counterintuitive effects on ordering. [all …]
|
D | workqueue.txt | 249 Some users depend on the strict execution ordering of ST wq. The 253 achieving the same ordering property as ST wq. 333 * 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
|
D | 00-INDEX | 239 - info on ordering I/O writes to memory-mapped addresses.
|
D | atomic_ops.txt | 633 is not dropping to zero, there are no memory ordering
|
D | kernel-parameters.txt | 354 old_ordering causes the ACPI 1.0 ordering of the _PTS 356 low power states, to be enforced (the ACPI 2.0 ordering
|
/linux-4.1.27/arch/arm/mach-tegra/ |
D | sleep.S | 50 dmb @ ensure ordering
|
/linux-4.1.27/Documentation/RCU/ |
D | rcu_dereference.txt | 51 the rcu_dereference(), thus maintaining proper ordering. 177 ordering either way. 186 so that a control dependency preserves the needed ordering. 324 from carrying out optimizations that otherwise might destroy the ordering 366 in turn destroying the ordering between this load and the loads of the
|
D | checklist.txt | 108 a. Readers must maintain proper ordering of their memory
|
D | RTFP.txt | 2034 Explanation of compilers violating dependency ordering.
|
/linux-4.1.27/tools/virtio/virtio-trace/ |
D | README | 112 4) Start to read trace data by ordering from a host 116 5) Stop to read trace data by ordering from a host
|
/linux-4.1.27/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
|
D | ppp_generic.txt | 14 ordering and combining received fragments
|
D | bonding.txt | 569 regards to the packet mis-ordering requirements of 752 characteristics but can cause packet reordering. If re-ordering is
|
/linux-4.1.27/Documentation/locking/ |
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.
|
/linux-4.1.27/Documentation/scsi/ |
D | scsi.txt | 22 will enforce the correct ordering of loading and unloading modules in
|
D | ChangeLog.sym53c8xx | 96 that implement a weak memory ordering. 481 - The PCI memory read from SCRIPTS that should ensure ordering 483 device drivers regarding ordering are working so well. ;-)
|
D | ChangeLog.ncr53c8xx | 32 that implement a weak memory ordering. 381 - Add some barriers to enforce memory ordering for x86 and
|
D | ncr53c8xx.txt | 1804 byte ordering.
|
D | ChangeLog.lpfc | 55 - stop using volatile. if you need special ordering use memory
|
/linux-4.1.27/arch/arm/mm/ |
D | cache-v7.S | 91 dmb @ ensure ordering with previous memory accesses 119 dmb @ ensure ordering with previous memory accesses
|
/linux-4.1.27/Documentation/infiniband/ |
D | core_locking.txt | 63 simultaneously. However, the ordering of the work completion
|
/linux-4.1.27/Documentation/acpi/ |
D | gpio-properties.txt | 8 the _CRS output ordering, for example).
|
/linux-4.1.27/Documentation/power/ |
D | s2ram.txt | 74 ordering-sensitive bugs).
|
D | userland-swsusp.txt | 124 These utilities MUST NOT make any assumptions regarding the ordering of
|
D | devices.txt | 256 The ordering of the device tree is defined by the order in which devices
|
/linux-4.1.27/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-4.1.27/Documentation/devicetree/bindings/soc/fsl/ |
D | qman.txt | 15 DPAA logic modules, maintains packet ordering within flows. Besides providing
|
/linux-4.1.27/Documentation/sound/alsa/soc/ |
D | DPCM.txt | 162 flags. There is also an option to specify the ordering of the trigger call for 164 components (as some DSPs have strong requirements for the ordering DAI/DSP
|
/linux-4.1.27/Documentation/x86/ |
D | earlyprintk.txt | 88 specify the correct EHCI debug controller number. The ordering
|
/linux-4.1.27/Documentation/usb/ |
D | dma.txt | 57 force a consistent memory access ordering by using memory barriers. It's
|
/linux-4.1.27/arch/x86/ |
D | Kconfig.cpu | 308 bool "PentiumPro memory ordering errata workaround" 312 memory operations to violate the x86 ordering standard in rare cases.
|
/linux-4.1.27/fs/jffs2/ |
D | README.Locking | 67 No ordering rules have been made for doing so.
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-script.txt | 113 Do various checks like samples ordering and lost events.
|
/linux-4.1.27/Documentation/crypto/ |
D | descore-readme.txt | 51 33us per encryption (options: 64k tables, FIPS standard bit ordering) 53 48us per encryption (options: 2k tables, FIPS standard bit ordering)
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | msr.txt | 255 guest does not need to use either lock prefix or memory ordering
|
/linux-4.1.27/Documentation/ide/ |
D | ChangeLog.ide-cd.1994-2004 | 61 * 3.01 Sep 2, 1995 -- Fix ordering of reenabling interrupts in
|
/linux-4.1.27/drivers/message/fusion/lsi/ |
D | mpi_history.txt | 301 * CONFIG_PAGE_LAN_1 to match preferred 64-bit ordering. 597 * byte ordering.
|
/linux-4.1.27/Documentation/netlabel/ |
D | draft-ietf-cipso-ipsecurity-01.txt | 250 provides representation of categories 0 to 239. The ordering of the bits 254 shows this ordering. Bit N is binary 1 if category N is part of the label
|
/linux-4.1.27/Documentation/device-mapper/ |
D | thin-provisioning.txt | 194 have only one of them active, and there's no ordering requirement on
|
/linux-4.1.27/Documentation/powerpc/ |
D | pci_iov_resource_on_powernv.txt | 115 there's a defined ordering for which window applies.
|
/linux-4.1.27/Documentation/cgroups/ |
D | blkio-controller.txt | 232 (there might be a time lag here due to re-ordering of requests by the
|
/linux-4.1.27/Documentation/block/ |
D | biodoc.txt | 252 some control over i/o ordering. 807 a bit of explaining. Normally we don't care too much about request ordering, 894 Specific I/O schedulers are responsible for ordering normal filesystem
|
/linux-4.1.27/net/sched/ |
D | Kconfig | 201 re-ordering. This is often useful to simulate networks when
|
/linux-4.1.27/Documentation/PCI/ |
D | MSI-HOWTO.txt | 47 the interrupt. PCI transaction ordering rules require that all the data
|
/linux-4.1.27/Documentation/isdn/ |
D | README.HiSax | 127 cards are installed, the ordering within the comma separated parameter
|
/linux-4.1.27/Documentation/mtd/ |
D | nand_ecc.txt | 281 And note that care must taken wrt byte ordering. The way bytes are
|
/linux-4.1.27/arch/arm/ |
D | Kconfig | 1088 ordering of the two writes. This workaround sets a specific bit in
|
/linux-4.1.27/drivers/net/wireless/ |
D | airo.c | 570 __le16 ordering; member
|