Searched full:writer (Results 1 – 25 of 46) sorted by relevance
12
| /Documentation/trace/ |
| D | ring-buffer-design.rst | 28 - the task that writes into the ring buffer (same as writer)
30 writer
81 but a writer may interrupt another writer, but it must finish writing
82 before the previous writer may continue. This is very important to the
94 This is very much like a writer being preempted by an interrupt and
99 cannot preempt/interrupt a writer, but it may read/consume from the
100 buffer at the same time as a writer is writing, but the reader must be
102 and can be preempted by a writer.
104 A writer can preempt a reader, but a reader cannot preempt a writer.
106 as a writer.
[all …]
|
| /Documentation/locking/ |
| D | seqlock.rst | 8 Sequence counters are a reader-writer consistency mechanism with
9 lockless readers (read-only retry loops), and no writer starvation. They
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.
53 requirements of writer serialization and non-preemptibility, use
97 sequence counters associate the lock used for writer serialization at
165 embedded spinlock for writer serialization and non-preemptibility.
195 1. Normal Sequence readers which never block a writer but they must
196 retry if a writer is in progress by detecting change in the sequence
206 2. Locking readers which will wait if a writer or another locking reader
[all …]
|
| D | locktypes.rst | 135 rw_semaphore is a multiple readers and single writer lock mechanism.
138 writer starvation.
150 Because an rw_semaphore writer cannot grant its priority to multiple
153 can grant their priority to a writer, a preempted low-priority writer will
155 writer from starving readers.
299 rwlock_t is a multiple readers and single writer lock mechanism.
303 thus preventing writer starvation.
313 - Because an rwlock_t writer cannot grant its priority to multiple
316 can grant their priority to a writer, a preempted low-priority writer
318 preventing that writer from starving readers.
|
| 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
91 NOTE! We are working hard to remove reader-writer spinlocks in most
|
| D | lockdep-design.rst | 436 read_lock() first. And when task B tries to acquire writer on X, it will block
437 and become a waiter for writer on X. Now if read_lock_2() is recursive readers,
438 task A will make progress, because writer waiters don't block recursive readers,
440 it will get blocked by writer waiter B, and cause a self deadlock.
451 writer waiters)
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.
539 exclusive writer to non-recursive locker dependency, "X -(EN)-> Y" means
540 X -> Y and X is a writer and Y is either a writer or non-recursive reader.
548 X -> Y and X is a reader (recursive or not) and Y is either a writer or
[all …]
|
| D | locktorture.rst | 40 ownership (readers). The default is the same amount of writer
137 (B): Number of writer lock acquisitions. If dealing with a read/write
|
| /Documentation/devicetree/bindings/mmc/ |
| D | litex,mmc.yaml | 31 - description: DMA Writer buffer
40 - const: writer
74 reg-names = "phy", "core", "reader", "writer", "irq";
|
| /Documentation/RCU/ |
| D | listRCU.rst | 16 be seen. If the writer calls list_replace_rcu(), the reader may see
59 writer lock protection. The list_del_rcu() invocation removes
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
294 writer lock would become a spinlock in this sort of code.
|
| D | rculist_nulls.rst | 46 * Because a writer could delete object, and a writer could
147 a race (some writer did a delete and/or a move of an object
|
| D | whatisRCU.rst | 47 :ref:`6. ANALOGY WITH READER-WRITER LOCKING <6_whatisRCU>`
655 reader-writer locks: If you try this with non-recursive locks, and
699 and release a global reader-writer lock. The synchronize_rcu()
710 It is possible to nest rcu_read_lock(), since reader-writer locks may
792 6. ANALOGY WITH READER-WRITER LOCKING
796 RCU is analogous to reader-writer locking. The following unified
797 diff shows how closely related RCU and reader-writer locking can be.
903 a reader-writer lock to a simple spinlock, and a synchronize_rcu()
922 The reader-writer analogy (illustrated by the previous section) is not
998 reader-writer lock and RCU as a reference counting system -- it is useful
[all …]
|
| D | rcuref.rst | 17 reader/writer spinlocks or semaphores are straightforward:
|
| /Documentation/driver-api/media/ |
| D | dtv-common.rst | 41 2) If there is exactly one reader and one writer, there is no need
|
| /Documentation/userspace-api/media/v4l/ |
| D | selection-api-configuration.rst | 45 driver writer considers the complete picture. Drivers shall set the
116 the driver writer considers the complete picture. It is recommended for
|
| D | vidioc-g-parm.rst | 238 driver writer may achieve that; it will depend on the hardware and
239 the ingenuity of the driver writer. High quality mode is a
|
| D | vidioc-cropcap.rst | 66 and height are defined in pixels, the driver writer is free to
|
| /Documentation/driver-api/nvdimm/ |
| D | btt.rst | 173 writes. We can hit a condition where the writer thread grabs a free block to do
176 writer started writing to the same external LBA, and finished the write updating
185 read is complete. Every writer thread, after grabbing a free block, checks the
193 Consider a case where two writer threads are writing to the same LBA. There can
|
| /Documentation/core-api/ |
| D | local_ops.rst | 83 synchronization is done by the writer CPU, an outdated copy of the
130 respectively on the writer and the reader CPUs. It would be the case if you use
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smp2p.yaml | 17 writer (the local side) and a single reader (the remote side). Values are
|
| /Documentation/cdrom/ |
| D | packet-writing.rst | 21 - Setup your writer::
|
| /Documentation/driver-api/ |
| D | connector.rst | 23 driver writer must create special sockets, must know about struct sk_buff
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 30 Driver Writer's Guide
|
| /Documentation/admin-guide/ |
| D | devices.rst | 115 /dev/cdwriter CD-writer symbolic Current CD-writer device
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 117 Set dm-crypt workqueues and the writer thread to high priority. This
|
| /Documentation/admin-guide/laptops/ |
| D | disk-shock-protection.rst | 96 device per port. Even if the CD/DVD writer happens to be connected to
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 131 _OSI("Linux") led to some BIOS' malfunctioning due to BIOS writer's
|
12