| /Linux-v4.19/Documentation/trace/ |
| D | ring-buffer-design.txt | 21 producer - the task that writes into the ring buffer (same as writer)
23 writer - same as producer
64 but a writer may interrupt another writer, but it must finish writing
65 before the previous writer may continue. This is very important to the
77 This is very much like a writer being preempted by an interrupt and
82 cannot preempt/interrupt a writer, but it may read/consume from the
83 buffer at the same time as a writer is writing, but the reader must be
85 and can be preempted by a writer.
87 A writer can preempt a reader, but a reader cannot preempt a writer.
89 as a writer.
[all …]
|
| /Linux-v4.19/kernel/locking/ |
| D | percpu-rwsem.c | 20 rcuwait_init(&sem->writer); in __percpu_init_rwsem()
105 rcuwait_wake_up(&sem->writer); in __percpu_up_read()
162 rcuwait_wait_event(&sem->writer, readers_active_check(sem)); in percpu_down_write()
|
| /Linux-v4.19/include/linux/ |
| D | percpu-rwsem.h | 16 struct rcuwait writer; /* blocked writer */ member
26 .writer = __RCUWAIT_INITIALIZER(name.writer), \
|
| /Linux-v4.19/lib/ |
| D | decompress_unlzma.c | 277 struct writer { struct
292 static inline size_t INIT get_pos(struct writer *wr) in get_pos() argument
298 static inline uint8_t INIT peek_old_byte(struct writer *wr, in peek_old_byte()
316 static inline int INIT write_byte(struct writer *wr, uint8_t byte) in write_byte()
330 static inline int INIT copy_byte(struct writer *wr, uint32_t offs) in copy_byte()
335 static inline int INIT copy_bytes(struct writer *wr, in copy_bytes()
347 static inline int INIT process_bit0(struct writer *wr, struct rc *rc, in process_bit0()
391 static inline int INIT process_bit1(struct writer *wr, struct rc *rc, in process_bit1()
553 struct writer wr; in unlzma()
|
| /Linux-v4.19/tools/perf/util/ |
| D | data-convert-bt.c | 57 struct bt_ctf_writer *writer; member
85 struct ctf_writer writer; member
695 stream = bt_ctf_writer_create_stream(cw->writer, cw->stream_class); in ctf_stream__create()
794 struct ctf_writer *cw = &c->writer; in process_sample_event()
871 struct ctf_writer *cw = &c->writer; \
1364 struct bt_ctf_writer *writer = cw->writer; in ctf_writer__setup_env() local
1368 if (bt_ctf_writer_add_environment_field(writer, __n, __v)) \ in ctf_writer__setup_env()
1478 bt_ctf_writer_put(cw->writer); in ctf_writer__cleanup()
1486 struct bt_ctf_writer *writer; in ctf_writer__init() local
1493 writer = bt_ctf_writer_create(path); in ctf_writer__init()
[all …]
|
| /Linux-v4.19/drivers/misc/ibmasm/ |
| D | remote.c | 187 unsigned long writer; in ibmasm_handle_mouse_interrupt() local
191 writer = get_queue_writer(sp); in ibmasm_handle_mouse_interrupt()
193 while (reader != writer) { in ibmasm_handle_mouse_interrupt()
206 writer = get_queue_writer(sp); in ibmasm_handle_mouse_interrupt()
|
| /Linux-v4.19/drivers/char/ |
| D | apm-emulation.c | 106 unsigned int writer: 1; member
263 if (!as->suser || !as->writer) in apm_ioctl()
366 as->writer = (filp->f_mode & FMODE_WRITE) == FMODE_WRITE; in apm_open()
534 as->writer && as->suser) { in apm_suspend_notifier()
|
| /Linux-v4.19/drivers/tty/hvc/ |
| D | hvsi.c | 60 struct delayed_work writer; member
752 cancel_delayed_work_sync(&hp->writer); in hvsi_flush_output()
852 container_of(work, struct hvsi_struct, writer.work); in hvsi_write_worker()
872 schedule_delayed_work(&hp->writer, HZ); in hvsi_write_worker()
878 schedule_delayed_work(&hp->writer, 10); in hvsi_write_worker()
949 schedule_delayed_work(&hp->writer, 10); in hvsi_write()
1185 INIT_DELAYED_WORK(&hp->writer, hvsi_write_worker); in hvsi_console_init()
|
| /Linux-v4.19/Documentation/RCU/ |
| D | rculist_nulls.txt | 22 * Because a writer could delete object, and a writer could
117 a race (some writer did a delete and/or a move of an object
|
| D | listRCU.txt | 13 The best applications are cases where, if reader-writer locking were
26 system-call auditing support. For example, a reader-writer locked
75 The changes to the update side are also straightforward. A reader-writer
161 However, if it did, reader-writer-locked code to do so might look as
217 the reader-writer lock would become a spinlock in this sort of code.
|
| D | rcuref.txt | 13 reader/writer spinlocks or semaphores are straightforward:
|
| D | torture.txt | 55 nfakewriters This is the number of RCU fake writer threads to run. Fake
56 writer threads repeatedly use the synchronous "wait for
207 o "ver": The number of times since boot that the RCU writer task
|
| /Linux-v4.19/Documentation/locking/ |
| D | spinlocks.txt | 45 Lesson 2: reader-writer spinlocks.
48 to mostly read from the shared variables, the reader-writer locks
53 NOTE! reader-writer locks require more atomic memory operations than
83 NOTE! We are working hard to remove reader-writer spinlocks in most
|
| D | locktorture.txt | 33 ownership (readers). The default is the same amount of writer
114 (B): Number of writer lock acquisitions. If dealing with a read/write primitive
|
| /Linux-v4.19/Documentation/media/kapi/ |
| D | dtv-common.rst | 48 2) If there is exactly one reader and one writer, there is no need
|
| /Linux-v4.19/drivers/staging/greybus/tools/ |
| D | lbtest | 108 row = csv.writer(csvf, delimiter=",", quotechar="'",
|
| /Linux-v4.19/Documentation/nvdimm/ |
| D | btt.txt | 162 writes. We can hit a condition where the writer thread grabs a free block to do
165 writer started writing to the same external LBA, and finished the write updating
174 read is complete. Every writer thread, after grabbing a free block, checks the
182 Consider a case where two writer threads are writing to the same LBA. There can
|
| /Linux-v4.19/tools/memory-model/litmus-tests/ |
| D | README | 78 As below, but with the second access of the writer process
88 As below, but with the first access of the writer process
|
| /Linux-v4.19/Documentation/media/uapi/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 | 232 driver writer may achieve that; it will depend on the hardware and
233 the ingenuity of the driver writer. High quality mode is a
|
| D | vidioc-cropcap.rst | 67 and height are defined in pixels, the driver writer is free to
|
| /Linux-v4.19/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
|
| /Linux-v4.19/arch/x86/kernel/ |
| D | apm_32.c | 344 unsigned int writer: 1; member
1207 if (!as->suser || !as->writer) in queue_event()
1535 if (!as->suser || !as->writer) in do_ioctl()
1633 as->writer = (filp->f_mode & FMODE_WRITE) == FMODE_WRITE; in do_open()
|
| /Linux-v4.19/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smp2p.txt | 4 a single 32-bit value between two processors. Each value has a single writer
|
| /Linux-v4.19/fs/jfs/ |
| D | jfs_logmgr.c | 215 int (*writer)(struct address_space *)) in write_special_inodes()
220 writer(sbi->ipbmap->i_mapping); in write_special_inodes()
221 writer(sbi->ipimap->i_mapping); in write_special_inodes()
222 writer(sbi->direct_inode->i_mapping); in write_special_inodes()
|
