Searched full:reader (Results 1 – 25 of 78) sorted by relevance
1234
| /Documentation/trace/ |
| D | ring-buffer-map.rst | 21 fields of the meta-page is the reader. It contains the sub-buffer ID which can
25 therefore effortless to know where the reader starts in the mapping:
29 reader_id = meta->reader->id;
32 When the application is done with the current reader, it can get a new one using
70 void *map, *reader, *data;
96 reader_id = meta->reader.id;
97 reader = data + meta->subbuf_size * reader_id;
99 printf("Current reader address: %p\n", reader);
|
| D | ring-buffer-design.rst | 34 - the task that reads from the buffer (same as reader)
36 reader
41 by the reader.
44 - a pointer to the page that the reader will use next
98 same time, nor can a reader preempt/interrupt another reader. A reader
100 buffer at the same time as a writer is writing, but the reader must be
101 on another processor to do so. A reader may read on its own processor
104 A writer can preempt a reader, but a reader cannot preempt a writer.
105 But a reader can read the buffer at the same time (on another processor)
110 At initialization a reader page is allocated for the reader that is not
[all …]
|
| /Documentation/locking/ |
| D | seqlock.rst | 8 Sequence counters are a reader-writer consistency mechanism with
11 reader wants a consistent set of information and is willing to retry if
19 the reader must retry.
28 or interrupted by read side sections. Otherwise the reader will spin for
30 interrupted writer. If that reader belongs to a real-time scheduling
34 as the writer can invalidate a pointer that the reader is following.
197 number. Writers do not wait for a sequence reader::
206 2. Locking readers which will wait if a writer or another locking reader
207 is in progress. A locking reader in progress will also block a writer
209 exclusive. Unlike rwlock_t, only one locking reader can acquire it::
[all …]
|
| D | spinlocks.rst | 52 Lesson 2: reader-writer spinlocks.
56 to mostly read from the shared variables, the reader-writer locks
61 NOTE! reader-writer locks require more atomic memory operations than
62 simple spinlocks. Unless the reader critical section is long, you
91 NOTE! We are working hard to remove reader-writer spinlocks in most
|
| D | lockdep-design.rst | 418 even inside the critical section of another reader of the same lock instance,
422 the critical section of another reader of the same lock instance.
435 Task A gets the reader (no matter whether recursive or non-recursive) on X via
535 exclusive writer to recursive reader dependency, "X -(ER)-> Y" means
536 X -> Y and X is a writer and Y is a recursive reader.
540 X -> Y and X is a writer and Y is either a writer or non-recursive reader.
543 shared reader to recursive reader dependency, "X -(SR)-> Y" means
544 X -> Y and X is a reader (recursive or not) and Y is a recursive reader.
547 shared reader to non-recursive locker dependency, "X -(SN)-> Y" means
548 X -> Y and X is a reader (recursive or not) and Y is either a writer or
[all …]
|
| /Documentation/admin-guide/laptops/ |
| D | lg-laptop.rst | 18 - FN-F9 (Reader mode) - Generates F14
23 Reader mode
27 reader mode. In this mode the screen colors change (blue color reduced),
28 and the reader mode indicator LED (on F9 key) turns on.
|
| /Documentation/devicetree/bindings/mmc/ |
| D | litex,mmc.yaml | 30 - description: DMA Reader buffer
39 - const: reader
74 reg-names = "phy", "core", "reader", "writer", "irq";
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sti-asoc-card.txt | 16 "st,stih407-uni-reader-pcm_in", "st,stih407-uni-reader-hdmi",
36 "rx" for "st,sti-uni-reader" compatibility
88 sti_uni_reader1: sti-uni-reader@8d84000 {
89 compatible = "st,stih407-uni-reader-hdmi";
|
| /Documentation/usb/ |
| D | iuu_phoenix.rst | 23 How to tune the reader speed?
57 - boost provide a way to overclock the reader ( my favorite :-) )
62 This will put the reader in a base of 3Mhz579 but boosted a 195 % !
|
| /Documentation/RCU/ |
| D | whatisRCU.rst | 47 :ref:`6. ANALOGY WITH READER-WRITER LOCKING <6_whatisRCU>`
94 during the removal phase need be considered, because any reader starting
136 So how the heck can a reclaimer tell when a reader is done, given
165 This temporal primitive is used by a reader to inform the
166 reclaimer that the reader is entering an RCU read-side critical
186 This temporal primitives is used by a reader to inform the
187 reclaimer that the reader is exiting an RCU read-side critical
260 in value from the updater to the reader. This is a spatial (as
282 The reader uses the spatial rcu_dereference() macro to fetch
364 reader, updater, and reclaimer.
[all …]
|
| D | torture.rst | 28 rcu-torture: Reader Pipe: 727860534 34213 0 0 0 0 0 0 0 0 0
29 rcu-torture: Reader Batch: 727877838 17003 0 0 0 0 0 0 0 0 0
91 * "Reader Pipe": Histogram of "ages" of structures seen by readers.
95 it becomes one when removed from reader visibility, and is
103 * "Reader Batch": Another histogram of "ages" of structures seen
108 "Reader Batch" list than in the "Reader Pipe" list.
113 the second to the number that have been removed from reader view,
|
| D | rcuref.rst | 17 reader/writer spinlocks or semaphores are straightforward:
125 any reader finds the element, that reader may safely acquire a reference
|
| D | listRCU.rst | 12 modify the list. The reader is guaranteed to see all of the elements
16 be seen. If the writer calls list_replace_rcu(), the reader may see
79 Some reader-writer locking use cases compute a value while holding
95 the system-call auditing support. For example, a reader-writer locked
149 The changes to the update side are also straightforward. A reader-writer lock
236 if it did, the reader-writer-locked code to do so might look as follows
396 For some use cases, reader performance can be improved by skipping
|
| D | rculist_nulls.rst | 100 We need to make sure a reader cannot read the new 'obj->obj_node.next' value
103 before the move, 'next' pointer is NULL, and lockless reader can not
152 then the reader doesn't care: It might occasionally
|
| D | rcu_dereference.rst | 251 void reader(void)
275 a second time between the time reader() loaded into "r1" and the time
279 But suppose that the reader needs a consistent view?
312 void reader(void)
372 int reader(void)
386 on the other. The comparison in reader() therefore tells the compiler
|
| /Documentation/driver-api/80211/ |
| D | introduction.rst | 15 The reader is expected to be familiar with the 802.11 standard as
|
| /Documentation/litmus-tests/rcu/ |
| D | RCU+sync+free.litmus | 6 * This litmus test demonstrates that an RCU reader can never see a write that
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-lg-laptop | 6 Control reader mode. 1 means on, 0 means off.
|
| D | sysfs-platform-eeepc-laptop | 26 Control the card reader. 1 means on, 0 means off.
|
| /Documentation/driver-api/nvdimm/ |
| D | btt.rst | 174 a new IO, but the (slow) reader thread is still reading from it. In other words,
175 the reader consulted a map entry, and started reading the corresponding block. A
178 internal, postmap block that the reader is (still) reading has been inserted
180 grab this free block, and start writing to it, causing the reader to read
183 The RTT is a simple, per arena table with 'nfree' entries. Every reader inserts
187 reader clears the RTT entry, and only then starts writing to it.
|
| /Documentation/devicetree/bindings/mfd/ |
| D | ti,am3359-tscadc.yaml | 53 description: Magnetic reader
|
| /Documentation/filesystems/ |
| D | files.rst | 27 a lock-free reader, all the elements of the file descriptor
64 4. To look up the file structure given an fd, a reader
|
| /Documentation/driver-api/media/ |
| D | dtv-common.rst | 41 2) If there is exactly one reader and one writer, there is no need
|
| /Documentation/translations/it_IT/RCU/ |
| D | torture.rst | 28 rcu-torture: Reader Pipe: 727860534 34213 0 0 0 0 0 0 0 0 0
29 rcu-torture: Reader Batch: 727877838 17003 0 0 0 0 0 0 0 0 0
88 * "Reader Pipe": un istogramma dell'età delle strutture viste dai lettori. RCU
100 * "Reader Batch": un istogramma di età di strutture viste dai lettori, ma
104 che nella lista "Reader Pipe".
|
| /Documentation/userspace-api/media/dvb/ |
| D | intro.rst | 15 The reader of this document is required to have some knowledge in the
51 Now, the API is maintained by the LinuxTV community (i.e. you, the reader
|
1234