Home
last modified time | relevance | path

Searched refs:coherency (Results 1 – 25 of 38) sorted by relevance

12

/linux/Documentation/devicetree/bindings/arm/marvell/
H A Dcoherency-fabric.txt9 * "marvell,coherency-fabric", to be used for the coherency fabric of
12 * "marvell,armada-375-coherency-fabric", for the Armada 375 coherency
15 * "marvell,armada-380-coherency-fabric", for the Armada 38x coherency
18 - reg: Should contain coherency fabric registers location and
21 * For "marvell,coherency-fabric", the first pair for the coherency
24 * For "marvell,armada-375-coherency-fabric", only one pair is needed
27 * For "marvell,armada-380-coherency-fabric", only one pair is needed
37 coherency-fabric@d0020200 {
38 compatible = "marvell,coherency-fabric";
44 coherency-fabric@21810 {
[all …]
/linux/Documentation/devicetree/bindings/powerpc/fsl/
H A Dccf.txt5 The CoreNet coherency fabric is a fabric-oriented, connectivity infrastructure
11 fsl,corenet1-cf - CoreNet coherency fabric version 1.
14 fsl,corenet2-cf - CoreNet coherency fabric version 2.
/linux/Documentation/filesystems/caching/
H A Dnetfs-api.rst18 (4) Cookies have coherency data that allows a cache to determine if the
35 (7) Data file coherency
72 for the cookie in the background, to check its coherency and, if necessary, to
104 and notes the coherency data.
116 The specified coherency data is stored in the cookie and will be matched
117 against coherency data stored on disk. The data pointer may be NULL if no data
118 is provided. If the coherency data doesn't match, the entire cache volume will
136 coherency data will be set to the value supplied. The amount of coherency data
163 The caller should also pass in a piece of coherency data in aux_data. A buffer
164 of size aux_data_len will be allocated and the coherency data copied in. It is
[all …]
H A Dbackend-api.rst147 u8 coherency[];
165 * ``coherency`` - A piece of coherency data that should be checked when the
168 * ``coherency_len`` - The amount of data in the coherency buffer.
203 * FSCACHE_COOKIE_NEEDS_UPDATE - The coherency data and/or object size has
227 * ``aux_len`` - The length of the coherency data buffer.
237 Each cookie also has a buffer for coherency data. This may also be inline or
/linux/Documentation/arch/arm/
H A Dcluster-pm-race-avoidance.rst6 cluster setup and teardown operations and to manage hardware coherency
33 mechanisms like Linux spinlocks may rely on coherency mechanisms which
73 enabling coherency.
83 coherency exit.
160 A CPU cannot start participating in hardware coherency until the
178 start participating in local coherency.
201 While in this state, the CPU exits coherency, including any
318 enabling of hardware coherency at the cluster level and any
323 setup to enable other CPUs in the cluster to enter coherency
329 cluster-level setup and hardware coherency complete
[all …]
/linux/Documentation/filesystems/
H A Docfs2.rst106 coherency=full (*) Disallow concurrent O_DIRECT writes, cluster inode
108 therefore full cluster coherency is guaranteed even
110 coherency=buffered Allow concurrent O_DIRECT writes without EX lock among
/linux/Documentation/ABI/removed/
H A Dnet_dma7 coherency issues of the cpu potentially touching the buffers
/linux/arch/arm/mach-mvebu/
H A DMakefile7 obj-y += cpu-reset.o board-v7.o coherency.o coherency_ll.o pmsu.o pmsu_ll.o
/linux/fs/netfs/
H A Dfscache_volume.c233 volume = kzalloc_flex(*volume, coherency, coherency_len); in fscache_alloc_volume()
240 memcpy(volume->coherency, coherency_data, coherency_len); in fscache_alloc_volume()
449 memcpy(volume->coherency, coherency_data, volume->coherency_len); in __fscache_relinquish_volume()
/linux/arch/arm/boot/dts/broadcom/
H A Dbcm-nsp-ax.dtsi5 * lack of DMA coherency.
/linux/drivers/gpu/drm/i915/selftests/
H A Di915_live_selftests.h36 selftest(coherency, i915_gem_coherency_live_selftests)
/linux/fs/cachefiles/
H A Dxattr.c284 const void *p = volume->vcookie->coherency; in cachefiles_set_volume_xattr()
333 const void *p = volume->vcookie->coherency; in cachefiles_check_volume_xattr()
/linux/drivers/cache/
H A DKconfig49 The Hydra Home Agent (HHA) is responsible for cache coherency
/linux/arch/arm/boot/dts/marvell/
H A Darmada-370-xp.dtsi175 coherencyfab: coherency-fabric@20200 {
176 compatible = "marvell,coherency-fabric";
H A Darmada-370-seagate-personal-cloud.dtsi34 coherency-fabric@20200 {
H A Darmada-39x.dtsi308 coherency-fabric@21010 {
309 compatible = "marvell,armada-380-coherency-fabric";
H A Darmada-375.dtsi409 coherencyfab: coherency-fabric@21010 {
410 compatible = "marvell,armada-375-coherency-fabric";
H A Darmada-38x.dtsi449 coherencyfab: coherency-fabric@21010 {
450 compatible = "marvell,armada-380-coherency-fabric";
/linux/arch/powerpc/boot/dts/
H A Damigaone.dts13 coherency-off;
/linux/drivers/block/drbd/
H A DKconfig35 cache coherency.
/linux/Documentation/admin-guide/device-mapper/
H A Dera.rst16 coherency after rolling back a vendor snapshot.
H A Dcache.rst98 worry about coherency. Coherency that exists is maintained, although
99 the cache will gradually cool as writes take place. If the coherency of
212 passthrough a degraded mode useful for various cache coherency
/linux/include/linux/
H A Dfscache.h92 u8 coherency[]; /* Coherency data */ member
/linux/Documentation/core-api/
H A Dcachetlb.rst343 Any necessary cache flushing or other coherency operations
380 coherency. It must do this by flushing the vmap range before doing
/linux/arch/loongarch/
H A DKconfig593 LoongArch maintains cache coherency in hardware, but when paired
595 is similar to WriteCombine) is out of the scope of cache coherency

12