Searched full:consistent (Results 1 – 25 of 1013) sorted by relevance
12345678910>>...41
| /linux-6.12.1/Documentation/admin-guide/blockdev/drbd/ |
| D | disk-states-8.dot | 3 Diskless -> Consistent [ label = "ioctl_set_disk()" ]
5 Consistent -> Outdated [ label = "receive_param()" ]
6 Consistent -> UpToDate [ label = "receive_param()" ]
7 Consistent -> Inconsistent [ label = "start resync" ]
11 Consistent -> Failed [ label = "io completion error" ]
|
| /linux-6.12.1/tools/testing/selftests/bpf/progs/ |
| D | cgroup_tcp_skb.c | 201 * are consistent with the state of the server socket.
224 * are consistent with the state of the server socket.
247 * are consistent with the state of the server socket.
270 * are consistent with the state of the server socket.
293 * are consistent with the state of the client socket.
316 * are consistent with the state of the client socket.
339 * are consistent with the state of the client socket.
362 * are consistent with the state of the client socket.
|
| /linux-6.12.1/drivers/comedi/drivers/ni_routing/ |
| D | README | 18 2) The register values are _NOT_ completely consistent. There is no way to
29 4) The sets of routes that are valid are not consistent from device to device.
33 through any documentation. In fact, the only consistent source of this
48 directory are chosen to be consistent with (a) the NI's user level
96 As noted above, the only known consistent source of information for
119 As noted above, the only consistent source of information of valid
178 convention, although the register values are not consistent. This next table
|
| /linux-6.12.1/Documentation/core-api/ |
| D | dma-api-howto.rst | 158 SN2) requires 64-bit consistent allocations to operate correctly when the IO
177 The setup for consistent allocations is performed via a call
244 uses consistent allocations, one would have to check the return value from
301 - Consistent DMA mappings which are usually mapped at driver
307 Think of "consistent" as "synchronous" or "coherent".
309 The current default is to return consistent memory in the low 32
311 set the consistent mask even if this default is fine for your
314 Good examples of what to use consistent mappings for are:
323 versa. Consistent mappings guarantee this.
327 Consistent DMA memory does not preclude the usage of
[all …]
|
| D | protection-keys.rst | 92 The kernel attempts to make protection keys consistent with the
119 value for the protection key register and so will not be consistent with
|
| D | dma-api.rst | 11 Part II describes extensions for supporting non-consistent memory
13 non-consistent platforms (this is usually only legacy platforms) you
36 Consistent memory is memory for which a write by either the device or
42 This routine allocates a region of <size> bytes of consistent memory.
51 Note: consistent memory can be expensive on some platforms, and the
53 consolidate your requests for consistent memory as much as possible.
67 Free a region of consistent memory you previously allocated. dev,
|
| /linux-6.12.1/arch/powerpc/mm/ |
| D | dma-noncoherent.c | 3 * PowerPC version derived from arch/arm/mm/consistent.c
20 * make an area consistent.
91 * __dma_sync_page makes memory consistent. identical to __dma_sync, but
|
| /linux-6.12.1/Documentation/scheduler/ |
| D | sched-nice-design.rst | 58 To sum it up: we always wanted to make nice levels more consistent, but
93 it was possible to implement better and more consistent nice +19
98 To address the second complaint (of nice levels not being consistent),
|
| /linux-6.12.1/drivers/video/ |
| D | hdmi.c | 85 * Validates that the infoframe is consistent and updates derived fields
191 * Validates that the infoframe is consistent and updates derived fields
256 * Validates that the infoframe is consistent and updates derived fields
325 * Validates that the infoframe is consistent and updates derived fields
380 * Validates that the infoframe is consistent and updates derived fields
466 * Validates that the infoframe is consistent and updates derived fields
584 * Validates that the infoframe is consistent and updates derived fields
664 * Validates that the infoframe is consistent and updates derived fields
732 * Validates that the infoframe is consistent.
818 * Validates that the infoframe is consistent and updates derived fields
[all …]
|
| /linux-6.12.1/arch/microblaze/mm/ |
| D | Makefile | 6 obj-y := consistent.o init.o pgtable.o mmu_context.o fault.o
|
| D | consistent.c | 3 * Microblaze support for cache consistent memory.
|
| /linux-6.12.1/include/linux/ |
| D | u64_stats_sync.h | 27 * are consistent w.r.t. each other (remember point #2: seqcounts are not
46 * While a consumer (reader) should use following template to get consistent
|
| /linux-6.12.1/fs/ubifs/ |
| D | ioctl.c | 20 /* Need to be kept consistent with checked flags in ioctl2ubifs() */
25 /* Need to be kept consistent with checked flags in ubifs2ioctl() */
|
| /linux-6.12.1/drivers/misc/mei/ |
| D | debugfs.c | 32 /* if the driver is not enabled the list won't be consistent */ in mei_dbgfs_meclients_show()
71 /* if the driver is not enabled the list won't be consistent */ in mei_dbgfs_active_show()
|
| /linux-6.12.1/arch/x86/include/asm/ |
| D | text-patching.h | 30 * consistent state to another consistent state atomically.
|
| /linux-6.12.1/kernel/trace/rv/ |
| D | rv_reactors.c | 369 /* Ensures that concurrent monitors read consistent reacting_on */ in rv_reacting_on()
388 /* Ensures that concurrent monitors read consistent reacting_on */ in turn_reacting_off()
395 /* Ensures that concurrent monitors read consistent reacting_on */ in turn_reacting_on()
|
| /linux-6.12.1/Documentation/devicetree/bindings/sound/ |
| D | eukrea-tlv320.txt | 15 Note: The AUDMUX port numbering should start at 1, which is consistent with
|
| /linux-6.12.1/drivers/media/usb/pvrusb2/ |
| D | pvrusb2-debugifc.h | 13 driver so the information should be self-consistent (but it will
|
| /linux-6.12.1/drivers/staging/media/atomisp/pci/isp/kernels/bh/bh_2/ |
| D | ia_css_bh_types.h | 20 * Should be consistent with hmem.h
|
| /linux-6.12.1/arch/riscv/mm/ |
| D | cacheflush.c | 211 * consistent with instruction storage. This does not enforce any guarantees
220 * will be guaranteed to be consistent with instruction storage.
|
| /linux-6.12.1/arch/s390/include/asm/ |
| D | vmlinux.lds.h | 12 * structs are avoided and linker produces consistent result.
|
| /linux-6.12.1/arch/parisc/include/asm/ |
| D | dma-mapping.h | 8 ** I/O MMU consistent method dma_sync behavior
|
| /linux-6.12.1/drivers/iio/imu/bno055/ |
| D | bno055_ser_core.c | 332 * packet is valid (i.e. header ok && received payload len consistent wrt the
351 * seems consistent with itself; if we got an unexpected in bno055_ser_handle_rx()
465 * len (as long as the serial protocol is consistent wrt in bno055_ser_receive_buf()
466 * itself (i.e. response header is consistent with received in bno055_ser_receive_buf()
|
| /linux-6.12.1/drivers/pinctrl/cirrus/ |
| D | pinctrl-cs47l92.c | 19 * To stay consistent with the datasheet the function names are the same as
|
| D | pinctrl-cs47l15.c | 19 * To stay consistent with the datasheet the function names are the same as
|
12345678910>>...41