| /linux/Documentation/block/ |
| H A 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 a 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 …]
|
| /linux/rust/kernel/alloc/ |
| H A D | allocator.rs | 89 /// # Guarantees in call()
91 /// This method has the same guarantees as `Allocator::realloc`. Additionally in call()
122 // - Those functions provide the guarantees of this function. in call()
143 // `layout.align()` which together with the slab guarantees means that `Kmalloc` will return
149 // SAFETY: `realloc` delegates to `ReallocFunc::call`, which guarantees that in realloc()
152 // - `realloc` satisfies the guarantees, since `ReallocFunc::call` has the same. in realloc()
222 // SAFETY: `realloc` delegates to `ReallocFunc::call`, which guarantees that in realloc()
225 // - `realloc` satisfies the guarantees, since `ReallocFunc::call` has the same. in realloc()
243 // SAFETY: `realloc` delegates to `ReallocFunc::call`, which guarantees that in realloc()
246 // - `realloc` satisfies the guarantees, sinc in realloc()
[all...] |
| /linux/rust/kernel/list/ |
| H A D | impl_list_item_mod.rs | 197 // SAFETY: See GUARANTEES comment on each method.
199 // GUARANTEES:
205 // SAFETY: The caller guarantees that `me` points at a valid value of type `Self`.
211 // GUARANTEES:
227 // GUARANTEES:
240 // GUARANTEES:
263 // SAFETY: See GUARANTEES comment on each method.
265 // GUARANTEES:
301 // GUARANTEES:
317 // GUARANTEES
[all...] |
| /linux/rust/kernel/debugfs/ |
| H A D | entry.rs | 67 // * The caller guarantees that `data` will outlive the returned `Entry`. in dynamic_file()
68 // * The guarantees on `FileOps` assert the vtable will be compatible with the data we have in dynamic_file()
120 // * The caller guarantees that `vtable` is compatible with `data`. in file()
121 // * The guarantees on `FileOps` assert the vtable will be compatible with the data we have in file()
154 /// # Guarantees in as_ptr()
167 // `as_ptr` guarantees that the pointer is of this form.
|
| /linux/rust/kernel/ |
| H A D | alloc.rs | 161 /// - Implementers must ensure that all trait functions abide by the guarantees documented in the
162 /// `# Guarantees` sections.
166 /// # Guarantees
179 /// # Guarantees
207 /// to `realloc` guarantees that the new or grown buffer has at least `Layout::size` bytes, but
226 /// # Guarantees
228 /// This function has the same guarantees as [`Allocator::alloc`]. When `ptr == Some(p)`, then
229 /// it additionally guarantees that:
252 // SAFETY: The caller guarantees that `ptr` points at a valid allocation created by this in free()
|
| H A D | uaccess.rs | 262 /// # Guarantees
435 // * If we hit the `len < dst.len()` case, then `raw_strncpy_from_user` guarantees that in strcpy_into_buf()
437 // * Otherwise, `raw_strncpy_from_user` guarantees that the string contained no NUL bytes, in strcpy_into_buf()
474 // SAFETY: Caller guarantees `from` is valid for `len` bytes (see this function's in write_raw()
636 /// # Guarantees
661 // GUARANTEES: `strncpy_from_user` was successful, so `dst` has contents in accordance with the in raw_strncpy_from_user()
662 // guarantees of this function. in raw_strncpy_from_user()
|
| /linux/tools/testing/selftests/vfio/lib/include/libvfio/ |
| H A D | vfio_pci_driver.h | 35 * Guarantees:
50 * Guarantees:
62 * Guarantees:
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-numa | 24 to violate the guarantees of cpusets. Shared memory,
28 which need strict cpuset location guarantees.
|
| /linux/arch/s390/include/asm/ |
| H A D | kmsan.h | 46 * Note, this sacrifices occasionally breaking scheduling guarantees. in kmsan_virt_addr_valid()
48 * performance guarantees due to being heavily instrumented. in kmsan_virt_addr_valid()
|
| /linux/arch/parisc/include/asm/ |
| H A D | ldcw.h | 5 /* Because kmalloc only guarantees 8-byte alignment for kmalloc'd data,
6 and GCC only guarantees 8-byte alignment for stack locals, we can't
|
| /linux/tools/memory-model/Documentation/ |
| H A D | locking.txt | 48 The basic rule guarantees that if CPU0() acquires mylock before CPU1(),
80 This converse to the basic rule guarantees that if CPU0() acquires
140 The smp_load_acquire() guarantees that its load from "flags" will
142 problem. The smp_store_release() guarantees that its store will be
|
| /linux/arch/x86/include/asm/ |
| H A D | kmsan.h | 89 * Note, this sacrifices occasionally breaking scheduling guarantees. in kmsan_virt_addr_valid()
91 * performance guarantees due to being heavily instrumented. in kmsan_virt_addr_valid()
|
| /linux/arch/riscv/include/asm/ |
| H A D | bitops.h | 249 * Note: there are no guarantees that this function will not be reordered
251 * make sure not to rely on its reordering guarantees.
266 * Note: there are no guarantees that this function will not be reordered
268 * make sure not to rely on its reordering guarantees.
|
| /linux/rust/zerocopy-derive/derive/ |
| H A D | into_bytes.rs | 63 // The only data layout guarantees made by [`repr(Rust)`] are those in derive_into_bytes_struct()
150 // guarantees the layout, our `PaddingCheck::Union` guarantees that there is in derive_into_bytes_union()
|
| /linux/arch/arm/nwfpe/ |
| H A 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
|
| /linux/kernel/livepatch/ |
| H A 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
|
| /linux/lib/ |
| H A D | Kconfig.kgdb | 141 'go', KDB tries to continue. No guarantees that the
144 No guarantees that the kernel is still usable in this situation.
|
| /linux/include/linux/ |
| H A D | dm-bufio.h | 107 * dm_bufio_write_dirty_buffers guarantees that the buffer is on-disk but
127 * Write all dirty buffers. Guarantees that all dirty buffers created prior
|
| /linux/kernel/ |
| H A D | Kconfig.preempt | 30 time, but there are no guarantees and occasional longer delays
107 require real-time guarantees.
|
| /linux/drivers/mmc/core/ |
| H A D | sd_ops.c | 318 /* NOTE: caller guarantees scr is heap-allocated */ in mmc_app_send_scr()
368 /* NOTE: caller guarantees resp is heap-allocated */ in mmc_sd_switch()
388 /* NOTE: caller guarantees ssr is heap-allocated */ in mmc_app_sd_status()
|
| /linux/rust/kernel/fs/ |
| H A D | file.rs | 284 // SAFETY: The caller guarantees that the pointer is not dangling and stays valid for the in from_raw_file()
287 // INVARIANT: The caller guarantees that there are no problematic `fdget_pos` calls. in from_raw_file()
340 // SAFETY: The file is valid because the shared reference guarantees a nonzero refcount. in flags()
358 // SAFETY: The caller guarantees that the pointer is not dangling and stays valid for the in from_raw_file()
361 // INVARIANT: The caller guarantees that there are no problematic `fdget_pos` calls. in from_raw_file()
|
| /linux/tools/testing/selftests/arm64/pauth/ |
| H A D | pac_corruptor.S | 9 * also guarantees no possible collision. TCR_EL1.TBI0 is set by default so no
|
| /linux/net/dcb/ |
| H A D | Kconfig | 18 framework for assigning bandwidth guarantees to traffic classes.
|
| /linux/Documentation/ |
| H A D | memory-barriers.txt | 49 - Guarantees.
223 GUARANTEES
226 There are some minimal guarantees that may be expected of a CPU:
309 And there are anti-guarantees:
311 (*) These guarantees do not apply to bitfields, because compilers often
322 (*) These guarantees apply only to properly aligned and sized scalar
329 guarantees were introduced into the C11 standard, so beware when
418 the CPU under consideration guarantees that for any load preceding it,
476 This acts as a one-way permeable barrier. It guarantees that all memory
491 This also acts as a one-way permeable barrier. It guarantees that all
[all …]
|
| /linux/drivers/greybus/ |
| H A D | hd.c | 71 /* Locking: Caller guarantees serialisation */
95 /* Locking: Caller guarantees serialisation */
|