Home
last modified time | relevance | path

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

123456

/openbmc/linux/kernel/locking/
H A Drwbase_rt.c61 for (r = atomic_read(&rwb->readers); r < 0;) { in rwbase_read_trylock()
62 if (likely(atomic_try_cmpxchg_acquire(&rwb->readers, &r, r + 1))) in rwbase_read_trylock()
122 atomic_inc(&rwb->readers); in __rwbase_read_lock()
173 if (unlikely(atomic_dec_and_test(&rwb->readers))) in rwbase_read_unlock()
186 (void)atomic_add_return_release(READER_BIAS - bias, &rwb->readers); in __rwbase_write_unlock()
219 if (!atomic_read_acquire(&rwb->readers)) { in __rwbase_write_trylock()
220 atomic_set(&rwb->readers, WRITER_BIAS); in __rwbase_write_trylock()
238 atomic_sub(READER_BIAS, &rwb->readers); in rwbase_write_lock()
280 atomic_sub(READER_BIAS, &rwb->readers); in rwbase_write_trylock()
/openbmc/linux/include/linux/
H A Drwbase_rt.h12 atomic_t readers; member
18 .readers = ATOMIC_INIT(READER_BIAS), \
25 atomic_set(&(rwbase)->readers, READER_BIAS); \
31 return atomic_read(&rwb->readers) != READER_BIAS; in rw_base_is_locked()
36 return atomic_read(&rwb->readers) > 0; in rw_base_is_contended()
H A Drwlock_types.h59 atomic_t readers; member
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/fbida/files/
H A Dfbida-gcc10.patch21 #include "readers.h"
29 --- fbida-2.14/readers.c.org 2020-03-15 17:01:18.692683597 +0100
30 +++ fbida-2.14/readers.c 2020-03-15 16:57:19.141632384 +0100
33 #include "readers.h"
/openbmc/linux/fs/btrfs/
H A Dlocking.c331 atomic_set(&lock->readers, 0); in btrfs_drew_lock_init()
340 if (atomic_read(&lock->readers)) in btrfs_drew_try_write_lock()
347 if (atomic_read(&lock->readers)) { in btrfs_drew_try_write_lock()
360 wait_event(lock->pending_writers, !atomic_read(&lock->readers)); in btrfs_drew_write_lock()
372 atomic_inc(&lock->readers); in btrfs_drew_read_lock()
391 if (atomic_dec_and_test(&lock->readers)) in btrfs_drew_read_unlock()
H A Dsubpage.c174 atomic_set(&ret->readers, 0); in btrfs_alloc_subpage()
249 atomic_add(nbits, &subpage->readers); in btrfs_subpage_start_reader()
262 ASSERT(atomic_read(&subpage->readers) >= nbits); in btrfs_subpage_end_reader()
263 last = atomic_sub_and_test(nbits, &subpage->readers); in btrfs_subpage_end_reader()
303 ASSERT(atomic_read(&subpage->readers) == 0); in btrfs_subpage_start_writer()
/openbmc/linux/drivers/misc/cardreader/
H A DKconfig9 Alcor Micro card readers support access to many types of memory cards,
20 Realtek card readers support access to many types of memory cards,
29 Select this option to get support for Realtek USB 2.0 card readers
/openbmc/linux/Documentation/RCU/
H A Drcu.rst10 must be long enough that any readers accessing the item being deleted have
21 The advantage of RCU's two-part approach is that RCU readers need
26 in read-mostly situations. The fact that RCU readers need not
30 if the RCU readers give no indication when they are done?
32 Just as with spinlocks, RCU readers are not permitted to
42 same effect, but require that the readers manipulate CPU-local
H A Dchecklist.rst30 One final exception is where RCU readers are used to prevent
40 RCU does allow *readers* to run (almost) naked, but *writers* must
85 The whole point of RCU is to permit readers to run without
86 any locks or atomic operations. This means that readers will
99 locks (that are acquired by both readers and writers)
100 that guard per-element state. Fields that the readers
106 c. Make updates appear atomic to readers. For example,
110 appear to be atomic to RCU readers, nor will sequences
118 d. Carefully order the updates and the reads so that readers
161 is common to readers and updaters. However, lockdep
[all …]
H A DwhatisRCU.rst56 Section 1, though most readers will profit by reading this section at
79 new versions of these data items), and can run concurrently with readers.
81 readers is the semantics of modern CPUs guarantee that readers will see
85 removal phase. Because reclaiming data items can disrupt any readers
87 not start until readers no longer hold references to those data items.
91 reclamation phase until all readers active during the removal phase have
93 callback that is invoked after they finish. Only readers that are active
101 readers cannot gain a reference to it.
103 b. Wait for all previous readers to complete their RCU read-side
106 c. At this point, there cannot be any readers who hold references
[all …]
H A Dlockdep.rst43 invoked by both RCU readers and updaters.
47 is invoked by both RCU-bh readers and updaters.
51 is invoked by both RCU-sched readers and updaters.
55 is invoked by both SRCU readers and updaters.
H A DlistRCU.rst54 ``tasklist_lock``. To prevent readers from noticing changes in the list
58 any readers traversing the list will see valid ``p->tasks.next`` pointers
62 all existing readers finish, which guarantees that the ``task_struct``
64 of all RCU readers that might possibly have a reference to that object.
210 need for writers to exclude readers.
217 readers to fail spectacularly.
219 So, when readers can tolerate stale data and when entries are either added or
/openbmc/linux/Documentation/locking/
H A Dlockdep-design.rst405 spin_lock() or write_lock()), non-recursive readers (i.e. shared lockers, like
406 down_read()) and recursive readers (recursive shared lockers, like rcu_read_lock()).
410 r: stands for non-recursive readers.
411 R: stands for recursive readers.
412 S: stands for all readers (non-recursive + recursive), as both are shared lockers.
413 N: stands for writers and non-recursive readers, as both are not recursive.
417 Recursive readers, as their name indicates, are the lockers allowed to acquire
421 While non-recursive readers will cause a self deadlock if trying to acquire inside
424 The difference between recursive readers and non-recursive readers is because:
425 recursive readers get blocked only by a write lock *holder*, while non-recursive
[all …]
H A Dseqlock.rst9 lockless readers (read-only retry loops), and no writer starvation. They
23 is odd and indicates to the readers that an update is in progress. At
25 even again which lets readers make progress.
153 from interruption by readers. This is typically the case when the read
195 1. Normal Sequence readers which never block a writer but they must
206 2. Locking readers which will wait if a writer or another locking reader
218 according to a passed marker. This is used to avoid lockless readers
H A Dlocktypes.rst95 readers.
135 rw_semaphore is a multiple readers and single writer lock mechanism.
141 exist special-purpose interfaces that allow non-owner release for readers.
151 readers, a preempted low-priority reader will continue holding its lock,
152 thus starving even high-priority writers. In contrast, because readers
155 writer from starving readers.
299 rwlock_t is a multiple readers and single writer lock mechanism.
314 readers, a preempted low-priority reader will continue holding its lock,
315 thus starving even high-priority writers. In contrast, because readers
318 preventing that writer from starving readers.
/openbmc/linux/drivers/misc/ibmasm/
H A Devent.c30 list_for_each_entry(reader, &sp->event_buffer->readers, node) in wake_up_event_readers()
123 list_add(&reader->node, &sp->event_buffer->readers); in ibmasm_event_reader_register()
153 INIT_LIST_HEAD(&buffer->readers); in ibmasm_event_buffer_init()
/openbmc/phosphor-webui/app/common/styles/elements/
H A Dpaginate.scss48 /* screen readers only */
88 /* screen readers only */
100 /* screen readers only */
126 /* screen readers only */
/openbmc/linux/fs/
H A Dpipe.c413 !READ_ONCE(pipe->readers); in pipe_writable()
446 if (!pipe->readers) { in pipe_write()
487 if (!pipe->readers) { in pipe_write()
698 if (!pipe->readers) in pipe_poll()
727 pipe->readers--; in pipe_release()
732 if (!pipe->readers != !pipe->writers) { in pipe_release()
893 pipe->readers = pipe->writers = 1; in get_pipe_inode()
1148 if (pipe->readers++ == 0) in fifo_open()
1170 if (!is_pipe && (filp->f_flags & O_NONBLOCK) && !pipe->readers) in fifo_open()
1177 if (!is_pipe && !pipe->readers) { in fifo_open()
[all …]
/openbmc/qemu/tests/unit/
H A Dtest-rcu-list.c351 int duration = 0, readers = 0; in main() local
371 readers = strtoul(argv[2], NULL, 0); in main()
373 if (duration && readers) { in main()
374 rcu_qtest(argv[0], duration, readers); in main()
/openbmc/linux/drivers/soc/aspeed/
H A Daspeed-p2a-ctrl.c65 u32 readers; member
192 ctrl->readers += 1; in aspeed_p2a_ioctl()
275 priv->parent->readers -= priv->read; in aspeed_p2a_release()
299 if (!open_regions && priv->parent->readers == 0) in aspeed_p2a_release()
/openbmc/linux/drivers/hid/
H A Dhid-roccat.c47 struct list_head readers; member
191 list_add_tail(&reader->node, &device->readers); in roccat_open()
270 list_for_each_entry(reader, &device->readers, node) { in roccat_report_event()
339 INIT_LIST_HEAD(&device->readers); in roccat_connect()
/openbmc/linux/drivers/iio/
H A DTODO14 to state struct and using property handlers and readers.
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/openct/
H A Dopenct_0.6.20.bb4 OpenCT implements drivers for several smart card readers. \
9 readers to remote machines via TCP/IP."
/openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/
H A Dpython3-pyatspi_2.46.1.bb2 …PI2 is a protocol over DBus, toolkit widgets use to provide content to screen readers such as Orca"
/openbmc/qemu/docs/devel/
H A Drcu.rst9 RCU supports concurrency between a single writer and multiple readers,
33 readers will not be able to get a reference to the old data. After
37 there cannot be any readers who hold references to the data structure,
154 with readers, if the updater never mutates a field within a
155 data item that is already accessible to readers. This is the
158 before ``qatomic_rcu_set()`` makes the data item visible to readers.

123456