Home
last modified time | relevance | path

Searched full:tearing (Results 1 – 13 of 13) sorted by relevance

/Documentation/arch/arm/
Dcluster-pm-race-avoidance.rst219 CPU can start up while another CPU is tearing the cluster down.
222 as seen by a CPU tearing the cluster down. The "inbound side" is the
227 independently of the CPU which is tearing down the cluster. For this
371 An outbound CPU is tearing the cluster down. The selected CPU
416 b) finish tearing the cluster down and put the cluster
/Documentation/devicetree/bindings/display/panel/
Dpanel-common.yaml124 GPIO spec for the tearing effect synchronization signal.
125 The tearing effect signal is active high. Active low signals can be
/Documentation/mm/
Dpage_frags.rst37 way of tearing down a page cache. For this reason __page_frag_cache_drain
/Documentation/driver-api/fpga/
Dfpga-region.rst73 following APIs to handle building or tearing down that list.
/Documentation/RCU/
Drcu_dereference.rst462 optimizations involving invented loads and perhaps also load tearing.
480 Load tearing could of course result in dereferencing a mashup of a pair
/Documentation/core-api/
Dcircular-buffers.rst229 prevents the compiler from tearing the store, and enforces ordering
/Documentation/devicetree/bindings/display/msm/
Ddsi-controller-main.yaml170 tearing elimination.
/Documentation/arch/arm/omap/
Ddss.rst206 tear_elim Tearing elimination 0=off, 1=on
/Documentation/
Dmemory-barriers.txt1779 with a single memory-reference instruction, prevents "load tearing"
1780 and "store tearing," in which a single large access is replaced by
1794 use of WRITE_ONCE() prevents store tearing in the following example:
1798 Use of packed structures can also result in load and store tearing,
1817 load tearing on 'foo1.b' and store tearing on 'foo2.b'. READ_ONCE()
1818 and WRITE_ONCE() again prevent tearing in this example:
/Documentation/filesystems/caching/
Dnetfs-api.rst83 extra pins into the cache to stop cache withdrawal from tearing down the
/Documentation/translations/ko_KR/
Dmemory-barriers.txt1746 대체되는 "로드 티어링(load tearing)" 과 "스토어 티어링(store tearing)" 을
/Documentation/translations/sp_SP/
Dmemory-barriers.txt1854 "desgarro de la carga" (load tearing) y "desgarro del store" (store
1855 tearing), en el que un solo gran acceso es reemplazado por múltiples
/Documentation/RCU/Design/Requirements/
DRequirements.rst442 | in a byte-at-a-time manner, resulting in *load tearing*, in turn |