Home
last modified time | relevance | path

Searched refs:readers (Results 1 – 25 of 67) sorted by relevance

123

/Linux-v4.19/Documentation/RCU/
Drcu.txt8 must be long enough that any readers accessing the item being deleted have
19 The advantage of RCU's two-part approach is that RCU readers need
24 in read-mostly situations. The fact that RCU readers need not
28 if the RCU readers give no indication when they are done?
30 Just as with spinlocks, RCU readers are not permitted to
40 same effect, but require that the readers manipulate CPU-local
DwhatisRCU.txt37 Section 1, though most readers will profit by reading this section at
58 new versions of these data items), and can run concurrently with readers.
60 readers is the semantics of modern CPUs guarantee that readers will see
64 removal phase. Because reclaiming data items can disrupt any readers
66 not start until readers no longer hold references to those data items.
70 reclamation phase until all readers active during the removal phase have
72 callback that is invoked after they finish. Only readers that are active
80 readers cannot gain a reference to it.
82 b. Wait for all previous readers to complete their RCU read-side
85 c. At this point, there cannot be any readers who hold references
[all …]
Dchecklist.txt26 One final exception is where RCU readers are used to prevent
36 RCU does allow -readers- to run (almost) naked, but -writers- must
76 The whole point of RCU is to permit readers to run without
77 any locks or atomic operations. This means that readers will
90 locks (that are acquired by both readers and writers)
92 the readers refrain from accessing can be guarded by
97 c. Make updates appear atomic to readers. For example,
101 appear to be atomic to RCU readers, nor will sequences
107 readers see valid data at all phases of the update.
150 is common to readers and updaters. However, lockdep
[all …]
Dlockdep.txt37 invoked by both RCU readers and updaters.
41 is invoked by both RCU-bh readers and updaters.
45 is invoked by both RCU-sched readers and updaters.
49 is invoked by both SRCU readers and updaters.
Drcubarrier.txt7 very low-overhead readers that are immune to deadlock, priority inversion,
13 readers, so that RCU updates to shared data must be undertaken quite
15 pre-existing readers have finished. These old versions are needed because
16 such readers might hold a reference to them. RCU updates can therefore be
19 How can an RCU writer possibly determine when all readers are finished,
20 given that readers might well leave absolutely no trace of their
22 pre-existing readers have completed. An updater wishing to delete an
Dtorture.txt40 irqreader Says to invoke RCU readers from irq level. This is currently
57 current readers" function of the interface selected by
205 to readers.
208 has changed the structure visible to readers.
250 o "Reader Pipe": Histogram of "ages" of structures seen by readers.
263 by readers, but in terms of counter flips (or batches) rather
DlistRCU.txt144 writers to exclude readers. Normally, the write_lock() calls would
152 otherwise cause concurrent readers to fail spectacularly.
154 So, when readers can tolerate stale data and when entries are either added
/Linux-v4.19/drivers/misc/ibmasm/
Devent.c44 list_for_each_entry(reader, &sp->event_buffer->readers, node) in wake_up_event_readers()
137 list_add(&reader->node, &sp->event_buffer->readers); in ibmasm_event_reader_register()
167 INIT_LIST_HEAD(&buffer->readers); in ibmasm_event_buffer_init()
Dibmasm.h131 struct list_head readers; member
/Linux-v4.19/fs/
Dpipe.c368 if (!pipe->readers) { in pipe_write()
402 if (!pipe->readers) { in pipe_write()
537 if (!pipe->readers) in pipe_poll()
566 pipe->readers--; in pipe_release()
570 if (pipe->readers || pipe->writers) { in pipe_release()
718 pipe->readers = pipe->writers = 1; in get_pipe_inode()
918 if (pipe->readers++ == 0) in fifo_open()
940 if (!is_pipe && (filp->f_flags & O_NONBLOCK) && !pipe->readers) in fifo_open()
947 if (!is_pipe && !pipe->readers) { in fifo_open()
961 pipe->readers++; in fifo_open()
[all …]
Dsplice.c194 if (unlikely(!pipe->readers)) { in splice_to_pipe()
234 if (unlikely(!pipe->readers)) { in add_to_pipe()
930 pipe->readers = 1; in splice_direct_to_actor()
1073 if (unlikely(!pipe->readers)) { in wait_for_space()
1483 if (!pipe->readers) { in opipe_prep()
1534 if (!opipe->readers) { in splice_pipe_to_pipe()
1638 if (!opipe->readers) { in link_pipe()
Dcoredump.c492 pipe->readers++; in wait_for_dump_helpers()
502 wait_event_interruptible(pipe->wait, pipe->readers == 1); in wait_for_dump_helpers()
505 pipe->readers--; in wait_for_dump_helpers()
/Linux-v4.19/drivers/misc/cardreader/
DKconfig8 Realtek card readers support access to many types of memory cards,
17 Select this option to get support for Realtek USB 2.0 card readers
/Linux-v4.19/drivers/hid/
Dhid-roccat.c50 struct list_head readers; member
194 list_add_tail(&reader->node, &device->readers); in roccat_open()
271 list_for_each_entry(reader, &device->readers, node) { in roccat_report_event()
338 INIT_LIST_HEAD(&device->readers); in roccat_connect()
/Linux-v4.19/net/sunrpc/
Dcache.c349 atomic_set(&cd->readers, 0); in sunrpc_init_cache_detail()
756 int readers; member
806 rq->readers++; in cache_read()
840 rq->readers--; in cache_read()
841 if (rq->readers == 0 && in cache_read()
1005 atomic_inc(&cd->readers); in cache_open()
1027 ->readers--; in cache_release()
1039 atomic_dec(&cd->readers); in cache_release()
1063 if (cr->readers != 0) in cache_dequeue()
1147 if (atomic_read(&detail->readers)) in cache_listeners_exist()
[all …]
/Linux-v4.19/include/linux/
Dpipe_fs_i.h52 unsigned int readers; member
/Linux-v4.19/drivers/mtd/ubi/
Dkapi.c175 vol->readers += 1; in ubi_open_volume()
185 if (vol->exclusive || vol->writers || vol->readers || in ubi_open_volume()
349 vol->readers -= 1; in ubi_close_volume()
Dcdev.c63 users = vol->readers + vol->writers + vol->exclusive + vol->metaonly; in get_exclusive()
69 vol->readers = vol->writers = vol->metaonly = 0; in get_exclusive()
89 ubi_assert(vol->readers == 0 && vol->writers == 0 && vol->metaonly == 0); in revoke_exclusive()
93 vol->readers = 1; in revoke_exclusive()
/Linux-v4.19/drivers/usb/storage/
DKconfig17 and card readers.
38 for Realtek RTS51xx USB card readers.
51 Support for certain Datafab CompactFlash readers.
/Linux-v4.19/Documentation/media/kapi/
Ddtv-common.rst50 Two or more readers must be locked against each other.
/Linux-v4.19/include/media/
Ddvbdev.h167 int readers; member
/Linux-v4.19/Documentation/block/
Dcfq-iosched.txt264 queues. Otherwise in presence of many sequential readers, other
267 For example, if there are 10 sequential readers doing IO and they get
273 multiple sequential readers.
281 badly in presence of multiple sequential readers.
284 provides isolation from multiple sequential readers and at the same
/Linux-v4.19/Documentation/ABI/testing/
Ddev-kmsg29 persistent state; many readers can concurrently open the device
30 and read from it, without affecting other readers.
/Linux-v4.19/Documentation/admin-guide/
Dbraille-console.rst5 readers can start), you first need to compile the support for the usual serial
/Linux-v4.19/Documentation/locking/
Dlocktorture.txt33 ownership (readers). The default is the same amount of writer
35 both readers and writers be the amount of online CPUs.

123