Searched full:guarantees (Results 1 – 25 of 73) sorted by relevance
123
| /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 …]
|
| /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 …]
|
| D | writeback_cache_control.rst | 26 guarantees that previously completed write requests are on non-volatile
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-class-dax | 11 1. Guarantees fault granularity with respect to a given
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-event.rst | 32 Starting with kernel 3.1 certain guarantees can be given with regards to
|
| /Documentation/security/tpm/ |
| D | tpm_event_log.rst | 44 This introduces another problem: nothing guarantees that it is not called
|
| /Documentation/vm/ |
| D | overcommit-accounting.rst | 46 guarantees and run close to the edge you MUST mmap your stack for the
|
| /Documentation/networking/device_drivers/ethernet/neterion/ |
| D | vxge.rst | 30 priority allocation and guarantees, GRO, TSO, interrupt moderation etc are
|
| /Documentation/i2c/muxes/ |
| D | i2c-mux-gpio.rst | 79 of any GPIO pin it uses as the device ID. This guarantees that every
|
| /Documentation/ |
| D | memory-barriers.txt | 49 - Guarantees.
224 GUARANTEES
227 There are some minimal guarantees that may be expected of a CPU:
310 And there are anti-guarantees:
312 (*) These guarantees do not apply to bitfields, because compilers often
323 (*) These guarantees apply only to properly aligned and sized scalar
330 guarantees were introduced into the C11 standard, so beware when
414 under consideration guarantees that for any load preceding it, if that
468 This acts as a one-way permeable barrier. It guarantees that all memory
483 This also acts as a one-way permeable barrier. It guarantees that all
[all …]
|
| /Documentation/driver-api/ |
| D | device_link.rst | 28 types: It guarantees correct suspend/resume and shutdown ordering between a
29 "supplier" device and its "consumer" devices, and it guarantees driver
244 from a child to a parent. Since the driver core already guarantees
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-entries | 46 guarantees that handles as exported are unique, and
|
| /Documentation/networking/ |
| D | ppp_generic.rst | 202 provides certain guarantees to the channels. Essentially the channels
210 The generic layer requires these guarantees from the channel:
234 The generic layer provides these guarantees to the channels:
|
| D | tls-offload.rst | 110 After TX state is installed, the stack guarantees that the first segment
137 There are no guarantees on record length or record segmentation. In particular
|
| /Documentation/arm64/ |
| D | elf_hwcaps.rst | 263 For interoperation with userspace, the kernel guarantees that bits 62
|
| /Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 18 RCU grace periods provide extremely strong memory-ordering guarantees
72 Tree RCU uses these two ordering guarantees to form an ordering
164 Tree RCU's grace--period memory-ordering guarantees rely most heavily on
257 provides no ordering guarantees, either for itself or for phase one of
448 guarantees that the first CPU's quiescent state happens before the
|
| /Documentation/RCU/ |
| D | rcuref.rst | 124 element can therefore safely be freed. This in turn guarantees that if
|
| D | rcu_dereference.rst | 296 r2 = p->c; /* Locking guarantees r2 == 144. */
312 guarantees that RCU depends on. And the volatile cast in rcu_dereference()
|
| /Documentation/filesystems/nfs/ |
| D | exporting.rst | 72 dentries. That guarantees that we won't need to hunt them down upon
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 19 domain, and the spec guarantees that all transactions within the
|
| /Documentation/arm/ |
| D | vlocks.rst | 151 guarantees coherency between overlapping memory accesses of
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 169 trusted key provides strong guarantees that the EVM key has not been
|
| /Documentation/gpu/ |
| D | i915.rst | 297 driver guarantees that commands issued to a fixed context are to be
305 In addition to the ordering guarantees, the kernel will restore GPU
320 used by the batchbuffer and guarantees that not only is the memory of
|
| /Documentation/driver-api/media/ |
| D | v4l2-event.rst | 27 :c:type:`v4l2_kevent` ringbuffer. This guarantees that if a driver is
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-dqevent.rst | 91 size of the message queue guarantees that all messages received in
|
123