Searched full:consistent (Results 1 – 25 of 1616) sorted by relevance
12345678910>>...65
| /kernel/linux/linux-5.10/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" ]
|
| /kernel/linux/linux-6.6/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" ]
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/drivers/staging/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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
224 uses consistent allocations, one would have to check the return value from
281 - Consistent DMA mappings which are usually mapped at driver
287 Think of "consistent" as "synchronous" or "coherent".
289 The current default is to return consistent memory in the low 32
291 set the consistent mask even if this default is fine for your
294 Good examples of what to use consistent mappings for are:
303 versa. Consistent mappings guarantee this.
307 Consistent DMA memory does not preclude the usage of
[all …]
|
| 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,
536 This routine allocates a region of <size> bytes of consistent memory. It
|
| /kernel/linux/linux-6.6/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
224 uses consistent allocations, one would have to check the return value from
281 - Consistent DMA mappings which are usually mapped at driver
287 Think of "consistent" as "synchronous" or "coherent".
289 The current default is to return consistent memory in the low 32
291 set the consistent mask even if this default is fine for your
294 Good examples of what to use consistent mappings for are:
303 versa. Consistent mappings guarantee this.
307 Consistent DMA memory does not preclude the usage of
[all …]
|
| /kernel/linux/common_modules/tzdriver/core/ |
| D | Kconfig | 21 TA Cpu Affinity bind range, consistent with CONFIG_MAX_NUM_NODES in TEE
28 consistent with CONFIG_MAX_NUM_NODES in TEE
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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),
|
| /kernel/linux/linux-5.10/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),
|
| /kernel/linux/linux-5.10/arch/microblaze/mm/ |
| D | consistent.c | 3 * Microblaze support for cache consistent memory.
27 * Consistent memory allocators. Used for DMA devices that want to share
|
| D | Makefile | 6 obj-y := consistent.o init.o
|
| /kernel/linux/linux-5.10/arch/arm/mm/ |
| D | dma-mapping-nommu.c | 28 * arm_nommu_dma_ops rely on consistent DMA memory (please, refer to
44 * - no consistent DMA region has been defined, so we can't in arm_nommu_dma_alloc()
46 * - there is no space left in consistent DMA region, so we in arm_nommu_dma_alloc()
|
| /kernel/linux/linux-6.6/fs/btrfs/ |
| D | Kconfig | 59 state of the filesystem on disk is always consistent, i.e.,
61 in a consistent state.
|
| /kernel/linux/linux-5.10/fs/btrfs/ |
| D | Kconfig | 58 state of the filesystem on disk is always consistent, i.e.,
60 in a consistent state.
|
| /kernel/liteos_m/testsuites/sample/kernel/task/ |
| D | It_los_task_103.c | 61 // 2, Assert this result is consistent with the priority that has been set. in TaskF01()
66 // 2, Assert this result is consistent with the priority that has been set. in TaskF01()
|
| D | It_los_task_104.c | 46 // 3, Assert this result is consistent with the priority that has been set. in TaskF02()
51 // 2, Assert this result is consistent with the priority that has been set. in TaskF02()
|
| D | It_los_task_112.c | 43 // 2, Assert this result is consistent with the priority that has been set. in TaskF02()
71 // 2, Assert this result is consistent with the priority that has been set. in TaskF01()
|
| /kernel/linux/linux-5.10/arch/x86/include/asm/ |
| D | text-patching.h | 40 * consistent state to another consistent state atomically.
|
| /kernel/linux/linux-6.6/arch/microblaze/mm/ |
| D | Makefile | 6 obj-y := consistent.o init.o pgtable.o mmu_context.o fault.o
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/drivers/video/ |
| D | hdmi.c | 84 * Validates that the infoframe is consistent and updates derived fields
190 * Validates that the infoframe is consistent and updates derived fields
251 * Validates that the infoframe is consistent and updates derived fields
320 * Validates that the infoframe is consistent and updates derived fields
375 * Validates that the infoframe is consistent and updates derived fields
455 * Validates that the infoframe is consistent and updates derived fields
536 * Validates that the infoframe is consistent and updates derived fields
616 * Validates that the infoframe is consistent and updates derived fields
684 * Validates that the infoframe is consistent.
770 * Validates that the infoframe is consistent and updates derived fields
[all …]
|
12345678910>>...65