| /linux-4.1.27/fs/ |
| D | pipe.c | 353 if (!pipe->readers) { in pipe_write()
389 if (!pipe->readers) { in pipe_write()
524 if (!pipe->readers) in pipe_poll()
553 pipe->readers--; in pipe_release()
557 if (pipe->readers || pipe->writers) { in pipe_release()
653 pipe->readers = pipe->writers = 1; in get_pipe_inode()
867 if (pipe->readers++ == 0) in fifo_open()
889 if (!is_pipe && (filp->f_flags & O_NONBLOCK) && !pipe->readers) in fifo_open()
896 if (!is_pipe && !pipe->readers) { in fifo_open()
910 pipe->readers++; in fifo_open()
[all …]
|
| D | coredump.c | 458 pipe->readers++; in wait_for_dump_helpers()
468 wait_event_interruptible(pipe->wait, pipe->readers == 1); in wait_for_dump_helpers()
471 pipe->readers--; in wait_for_dump_helpers()
|
| D | splice.c | 198 if (!pipe->readers) { in splice_to_pipe()
1193 pipe->readers = 1; in splice_direct_to_actor()
1765 if (!pipe->readers) { in opipe_prep()
1816 if (!opipe->readers) { in splice_pipe_to_pipe()
1920 if (!opipe->readers) { in link_pipe()
|
| /linux-4.1.27/drivers/misc/ibmasm/ |
| D | event.c | 44 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()
|
| D | ibmasm.h | 128 struct list_head readers; member
|
| /linux-4.1.27/Documentation/RCU/ |
| D | rcu.txt | 8 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
|
| D | checklist.txt | 28 RCU does allow -readers- to run (almost) naked, but -writers- must
60 The whole point of RCU is to permit readers to run without
61 any locks or atomic operations. This means that readers will
74 locks (that are acquired by both readers and writers)
76 the readers refrain from accessing can be guarded by
81 c. Make updates appear atomic to readers. For example,
85 appear to be atomic to RCU readers, nor will sequences
91 readers see valid data at all phases of the update.
134 is common to readers and updaters. However, lockdep
153 readers. Similarly, if the hlist macros are being used,
[all …]
|
| D | whatisRCU.txt | 32 Section 1, though most readers will profit by reading this section at
53 new versions of these data items), and can run concurrently with readers.
55 readers is the semantics of modern CPUs guarantee that readers will see
59 removal phase. Because reclaiming data items can disrupt any readers
61 not start until readers no longer hold references to those data items.
65 reclamation phase until all readers active during the removal phase have
67 callback that is invoked after they finish. Only readers that are active
75 readers cannot gain a reference to it.
77 b. Wait for all previous readers to complete their RCU read-side
80 c. At this point, there cannot be any readers who hold references
[all …]
|
| D | lockdep.txt | 37 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.
54 that is invoked by both RCU readers and updaters.
|
| D | rcubarrier.txt | 7 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
|
| D | torture.txt | 55 irqreader Says to invoke RCU readers from irq level. This is currently
72 current readers" function of the interface selected by
233 to readers.
236 has changed the structure visible to readers.
278 o "Reader Pipe": Histogram of "ages" of structures seen by readers.
291 by readers, but in terms of counter flips (or batches) rather
|
| D | listRCU.txt | 144 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
|
| D | rcuref.txt | 112 readers that can or ever will be able to reference the element. The
|
| D | rcu_dereference.txt | 210 Because updaters can run concurrently with RCU readers, RCU readers can
211 see stale and/or inconsistent values. If RCU readers need fresh or
|
| D | arrayRCU.txt | 139 using seqlock is that frequent updates can livelock readers.
|
| D | rculist_nulls.txt | 169 * insert obj in RCU way (readers might be traversing chain)
|
| D | RTFP.txt | 87 extended their technique to allow for multiple readers [Cowan96a].
115 contention, reduces memory latency for readers, and parallelizes pipeline
481 using the resource at hand. Allows multiple readers.
1599 RCU-based reader-writer lock that allows readers to proceed with
1601 If writer do show up, readers must of course wait as required by
1743 RCU-like implementation for frequent updaters and rare readers(!).
1819 Page-cache modifications permitting RCU readers and concurrent
1963 (2) wait for pre-existing readers to complete, and (2) maintain
2160 readers to confine themselves to the desired snapshot of the
2571 readers to confine themselves to the desired snapshot of the
|
| /linux-4.1.27/drivers/hid/ |
| D | hid-roccat.c | 50 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()
|
| D | Kconfig | 199 tristate "Cypress mouse and barcode readers"
203 Support for cypress mouse and barcode readers.
|
| /linux-4.1.27/net/sunrpc/ |
| D | cache.c | 346 atomic_set(&cd->readers, 0); in sunrpc_init_cache_detail()
737 int readers; member
787 rq->readers++; in cache_read()
821 rq->readers--; in cache_read()
822 if (rq->readers == 0 && in cache_read()
986 atomic_inc(&cd->readers); in cache_open()
1008 ->readers--; in cache_release()
1020 atomic_dec(&cd->readers); in cache_release()
1044 if (cr->readers != 0) in cache_dequeue()
1128 if (atomic_read(&detail->readers)) in cache_listeners_exist()
[all …]
|
| /linux-4.1.27/include/linux/ |
| D | pipe_fs_i.h | 50 unsigned int readers; member
|
| /linux-4.1.27/drivers/media/dvb-core/ |
| D | dvbdev.h | 92 int readers; member
|
| D | dvbdev.c | 117 if (!dvbdev->readers) in dvb_generic_open()
119 dvbdev->readers--; in dvb_generic_open()
140 dvbdev->readers++; in dvb_generic_release()
|
| D | dmxdev.c | 148 if (!dvbdev->readers) { in dvb_dvr_open()
158 dvbdev->readers--; in dvb_dvr_open()
196 dvbdev->readers++; in dvb_dvr_release()
1217 .readers = 1,
|
| D | dvb_ca_en50221.c | 1644 .readers = 1,
|
| D | dvb_frontend.c | 2737 .readers = (~0)-1, in dvb_register_frontend()
|
| /linux-4.1.27/drivers/mtd/ubi/ |
| D | kapi.c | 175 vol->readers += 1; in ubi_open_volume()
185 if (vol->exclusive || vol->writers || vol->readers || in ubi_open_volume()
346 vol->readers -= 1; in ubi_close_volume()
|
| D | cdev.c | 63 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()
|
| D | ubi.h | 321 int readers; member
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | dev-kmsg | 29 persistent state; many readers can concurrently open the device
30 and read from it, without affecting other readers.
|
| /linux-4.1.27/drivers/usb/storage/ |
| D | Kconfig | 17 and card readers.
38 for Realtek RTS51xx USB card readers.
51 Support for certain Datafab CompactFlash readers.
|
| /linux-4.1.27/Documentation/block/ |
| D | cfq-iosched.txt | 265 queues. Otherwise in presence of many sequential readers, other
268 For example, if there are 10 sequential readers doing IO and they get
274 multiple sequential readers.
282 badly in presence of multiple sequential readers.
285 provides isolation from multiple sequential readers and at the same
|
| /linux-4.1.27/Documentation/ |
| D | braille-console.txt | 4 readers can start), you first need to compile the support for the usual serial
|
| D | kernel-parameters.txt | 3118 Set number of RCU readers.
|
| /linux-4.1.27/Documentation/locking/ |
| D | locktorture.txt | 33 ownership (readers). The default is the same amount of writer
35 both readers and writers be the amount of online CPUs.
|
| D | spinlocks.txt | 50 readers to be in the same critical region at once, but if somebody wants
73 itself. The read lock allows many concurrent readers. Anything that
|
| /linux-4.1.27/drivers/media/firewire/ |
| D | firedtv-ci.c | 226 .readers = 1,
|
| /linux-4.1.27/drivers/media/pci/ngene/ |
| D | ngene-dvb.c | 100 .readers = -1,
|
| /linux-4.1.27/include/linux/sunrpc/ |
| D | cache.h | 117 atomic_t readers; /* how many time is /chennel open */ member
|
| /linux-4.1.27/drivers/pcmcia/ |
| D | Kconfig | 115 device, found in some older laptops and PCMCIA card readers.
133 older laptops and ISA-bus card readers for desktop systems. A
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | files.txt | 31 structure is freed with RCU and lock-free readers either
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | rpc-cache.txt | 178 Note: If a cache has no active readers on the channel, and has had not
179 active readers for more than 60 seconds, further requests will not be
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | of_unittest.txt | 175 Astute readers would have noticed that test-child0 node becomes the last
|
| D | usage-model.txt | 130 Astute readers might point out that the Beagle xM could also claim
|
| /linux-4.1.27/Documentation/scsi/ |
| D | scsi-changer.txt | 42 123 CD-ROM's, 5 CD-ROM readers (and therefore 6 SCSI ID's: the changer
|
| /linux-4.1.27/drivers/media/pci/bt8xx/ |
| D | dst_ca.c | 702 .readers = 1,
|
| /linux-4.1.27/Documentation/trace/ |
| D | ring-buffer-design.txt | 80 Readers can happen at any time. But no two readers may run at the
455 the readers. But the writers will never take a lock to write to the
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 7.AdvancedTopics | 146 Some readers will certainly object to putting this section with "advanced
|
| D | 3.Early-stage | 192 Some readers may be thinking at this point that their kernel work is
|
| /linux-4.1.27/Documentation/usb/ |
| D | usbmon.txt | 130 have leading zeros, for the sake of human readers.
|
| /linux-4.1.27/drivers/media/pci/ttpci/ |
| D | av7110_av.c | 1543 .readers = 5, /* arbitrary */
|
| /linux-4.1.27/drivers/media/pci/ddbridge/ |
| D | ddbridge-core.c | 981 .readers = -1,
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | mmu.txt | 446 memslot update, while some SRCU readers might be using the old copy. We do not
|
| /linux-4.1.27/drivers/usb/serial/ |
| D | Kconfig | 412 readers:
|
| /linux-4.1.27/fs/fuse/ |
| D | dev.c | 1401 if (!pipe->readers) { in fuse_dev_splice_read()
|
| /linux-4.1.27/init/ |
| D | Kconfig | 669 This option boosts the priority of preempted RCU readers that
715 readers blocking that grace period. Note that any RCU reader
|
| /linux-4.1.27/drivers/mfd/ |
| D | Kconfig | 708 Select this option to get support for Realtek USB 2.0 card readers
|
| /linux-4.1.27/Documentation/s390/ |
| D | Debugging390.txt | 1527 you can alternatively spool it to another readers guest.
|
| /linux-4.1.27/drivers/staging/speakup/ |
| D | spkguide.txt | 1260 or discourage subsequent modification by readers is not Transparent.
|