Searched full:guarantees (Results 1 – 25 of 999) sorted by relevance
12345678910>>...40
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 14 ``atomic_*()`` functions with regards to the memory ordering guarantees.
17 these memory ordering guarantees.
33 In the absence of any memory ordering guarantees (i.e. fully unordered)
35 program order (po) relation (on the same CPU). It guarantees that
41 A strong (full) memory ordering guarantees that all prior loads and
44 It also guarantees that all po-earlier stores on the same CPU
49 A RELEASE memory ordering guarantees that all prior loads and
51 before the operation. It also guarantees that all po-earlier
57 An ACQUIRE memory ordering guarantees that all post loads and
59 completed after the acquire operation. It also guarantees that all
[all …]
|
| /kernel/linux/linux-4.19/Documentation/core-api/ |
| D | refcount-vs-atomic.rst | 14 ``atomic_*()`` functions with regards to the memory ordering guarantees.
17 these memory ordering guarantees.
33 In the absence of any memory ordering guarantees (i.e. fully unordered)
35 program order (po) relation (on the same CPU). It guarantees that
41 A strong (full) memory ordering guarantees that all prior loads and
44 It also guarantees that all po-earlier stores on the same CPU
49 A RELEASE memory ordering guarantees that all prior loads and
51 before the operation. It also guarantees that all po-earlier
57 A control dependency (on success) for refcounters guarantees that
63 a single CPU relation and provides no guarantees for other CPUs.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/block/ |
| D | bfq-iosched.txt | 7 - BFQ guarantees a high system and application responsiveness, and a
55 4-1 Service guarantees provided
68 Regardless of the actual background workload, BFQ guarantees that, for
106 Strong fairness, bandwidth and delay guarantees
111 guarantees, it is possible to compute tight per-I/O-request delay
112 guarantees by a simple formula. If not configured for strict service
113 guarantees, BFQ switches to time-based resource sharing (only) for
121 possibly heavy workloads are being served, BFQ guarantees:
172 - With respect to idling for service guarantees, if several
175 guarantees the expected throughput distribution without ever
[all …]
|
| /kernel/linux/linux-5.10/Documentation/block/ |
| D | bfq-iosched.rst | 9 - BFQ guarantees a high system and application responsiveness, and a
70 4-1 Service guarantees provided
84 Regardless of the actual background workload, BFQ guarantees that, for
126 Strong fairness, bandwidth and delay guarantees
132 guarantees, it is possible to compute tight per-I/O-request delay
133 guarantees by a simple formula. If not configured for strict service
134 guarantees, BFQ switches to time-based resource sharing (only) for
142 possibly heavy workloads are being served, BFQ guarantees:
193 - With respect to idling for service guarantees, if several
196 guarantees the expected throughput distribution without ever
[all …]
|
| /kernel/linux/linux-5.10/arch/riscv/include/asm/ |
| D | bitops.h | 107 * Note: there are no guarantees that this function will not be reordered
109 * make sure not to rely on its reordering guarantees.
124 * Note: there are no guarantees that this function will not be reordered
126 * make sure not to rely on its reordering guarantees.
|
| /kernel/linux/linux-4.19/arch/riscv/include/asm/ |
| D | bitops.h | 120 * Note: there are no guarantees that this function will not be reordered
122 * make sure not to rely on its reordering guarantees.
137 * Note: there are no guarantees that this function will not be reordered
139 * make sure not to rely on its reordering guarantees.
|
| /kernel/linux/linux-5.10/arch/parisc/include/asm/ |
| D | ldcw.h | 6 /* Because kmalloc only guarantees 8-byte alignment for kmalloc'd data,
7 and GCC only guarantees 8-byte alignment for stack locals, we can't
|
| /kernel/linux/linux-5.10/kernel/ |
| D | Kconfig.preempt | 12 time, but there are no guarantees and occasional longer delays
73 require real-time guarantees.
|
| /kernel/linux/linux-4.19/arch/parisc/include/asm/ |
| D | ldcw.h | 6 /* Because kmalloc only guarantees 8-byte alignment for kmalloc'd data,
7 and GCC only guarantees 8-byte alignment for stack locals, we can't
|
| /kernel/linux/linux-4.19/lib/ |
| D | Kconfig.kgdb | 119 'go', KDB tries to continue. No guarantees that the
122 No guarantees that the kernel is still usable in this situation.
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/gem/ |
| D | i915_gem_busy.c | 24 * The uABI guarantees an active writer is also amongst the read in __busy_write_id()
45 * guarantees forward progress. We could rely on the idle worker in __busy_set_if_active()
|
| /kernel/linux/linux-5.10/arch/arm/nwfpe/ |
| D | ChangeLog | 61 comment in the code beside init_flag state the kernel guarantees
64 I couldn't even find anything that guarantees it is zeroed when
|
| /kernel/linux/linux-4.19/arch/arm/nwfpe/ |
| D | ChangeLog | 61 comment in the code beside init_flag state the kernel guarantees
64 I couldn't even find anything that guarantees it is zeroed when
|
| /kernel/linux/linux-5.10/kernel/livepatch/ |
| D | shadow.c | 189 * This function guarantees that the constructor function is called only when
218 * This function guarantees that only one shadow variable exists with the given
219 * @id for the given @obj. It also guarantees that the constructor function
|
| /kernel/linux/linux-5.10/drivers/mmc/core/ |
| D | sd_ops.c | 219 /* NOTE: caller guarantees scr is heap-allocated */ in mmc_app_send_scr()
272 /* NOTE: caller guarantees resp is heap-allocated */ in mmc_sd_switch()
314 /* NOTE: caller guarantees ssr is heap-allocated */ in mmc_app_sd_status()
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | dm-bufio.h | 91 * dm_bufio_write_dirty_buffers guarantees that the buffer is on-disk but
111 * Write all dirty buffers. Guarantees that all dirty buffers created prior
|
| /kernel/linux/linux-5.10/lib/ |
| D | Kconfig.kgdb | 140 'go', KDB tries to continue. No guarantees that the
143 No guarantees that the kernel is still usable in this situation.
|
| /kernel/linux/linux-4.19/kernel/livepatch/ |
| D | shadow.c | 201 * This function guarantees that the constructor function is called only when
230 * This function guarantees that only one shadow variable exists with the given
231 * @id for the given @obj. It also guarantees that the constructor function
|
| /kernel/linux/linux-4.19/drivers/mmc/core/ |
| D | sd_ops.c | 244 /* NOTE: caller guarantees scr is heap-allocated */ in mmc_app_send_scr()
297 /* NOTE: caller guarantees resp is heap-allocated */ in mmc_sd_switch()
339 /* NOTE: caller guarantees ssr is heap-allocated */ in mmc_app_sd_status()
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | dm-bufio.h | 91 * dm_bufio_write_dirty_buffers guarantees that the buffer is on-disk but
111 * Write all dirty buffers. Guarantees that all dirty buffers created prior
|
| /kernel/linux/linux-5.10/tools/testing/selftests/arm64/pauth/ |
| D | pac_corruptor.S | 9 * also guarantees no possible collision. TCR_EL1.TBI0 is set by default so no
|
| /kernel/linux/linux-5.10/net/sunrpc/xprtrdma/ |
| D | frwr_ops.c | 256 * largest r/wsize NFS will ask for. This guarantees that in frwr_query_device()
486 * memory regions. This guarantees that registered MRs are properly fenced
526 /* Strong send queue ordering guarantees that when the in frwr_unmap_sync()
592 * This guarantees that registered MRs are properly fenced from the
630 /* Strong send queue ordering guarantees that when the in frwr_unmap_async()
|
| /kernel/linux/linux-4.19/net/dcb/ |
| D | Kconfig | 17 framework for assigning bandwidth guarantees to traffic classes.
|
| /kernel/linux/linux-4.19/kernel/locking/ |
| D | percpu-rwsem.c | 175 * Therefore we force it through the slow path which guarantees an in percpu_up_write()
176 * acquire and thereby guarantees the critical section's consistency. in percpu_up_write()
|
| /kernel/linux/linux-5.10/net/dcb/ |
| D | Kconfig | 18 framework for assigning bandwidth guarantees to traffic classes.
|
12345678910>>...40