Home
last modified time | relevance | path

Searched refs:writer (Results 1 – 39 of 39) sorted by relevance

/linux-4.4.14/Documentation/trace/
Dring-buffer-design.txt21 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-4.4.14/tools/perf/util/
Ddata-convert-bt.c52 struct bt_ctf_writer *writer; member
74 struct ctf_writer writer; member
464 stream = bt_ctf_writer_create_stream(cw->writer, cw->stream_class); in ctf_stream__create()
563 struct ctf_writer *cw = &c->writer; in process_sample_event()
897 struct bt_ctf_writer *writer = cw->writer; in ctf_writer__setup_env() local
901 if (bt_ctf_writer_add_environment_field(writer, __n, __v)) \ in ctf_writer__setup_env()
1004 bt_ctf_writer_put(cw->writer); in ctf_writer__cleanup()
1012 struct bt_ctf_writer *writer; in ctf_writer__init() local
1019 writer = bt_ctf_writer_create(path); in ctf_writer__init()
1020 if (!writer) in ctf_writer__init()
[all …]
/linux-4.4.14/lib/
Ddecompress_unlzma.c277 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()
DKconfig.debug960 even a debug kernel. If you are a driver writer, enable it. If
/linux-4.4.14/drivers/misc/ibmasm/
Dremote.c187 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-4.4.14/drivers/char/
Dapm-emulation.c113 unsigned int writer: 1; member
270 if (!as->suser || !as->writer) in apm_ioctl()
373 as->writer = (filp->f_mode & FMODE_WRITE) == FMODE_WRITE; in apm_open()
554 as->writer && as->suser) { in apm_suspend_notifier()
/linux-4.4.14/drivers/tty/hvc/
Dhvsi.c73 struct delayed_work writer; member
765 cancel_delayed_work_sync(&hp->writer); in hvsi_flush_output()
865 container_of(work, struct hvsi_struct, writer.work); in hvsi_write_worker()
885 schedule_delayed_work(&hp->writer, HZ); in hvsi_write_worker()
891 schedule_delayed_work(&hp->writer, 10); in hvsi_write_worker()
962 schedule_delayed_work(&hp->writer, 10); in hvsi_write()
1198 INIT_DELAYED_WORK(&hp->writer, hvsi_write_worker); in hvsi_console_init()
/linux-4.4.14/Documentation/RCU/
Drculist_nulls.txt22 * 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
DlistRCU.txt13 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.
Drcuref.txt13 reader/writer spinlocks or semaphores are straightforward:
Dtorture.txt70 nfakewriters This is the number of RCU fake writer threads to run. Fake
71 writer threads repeatedly use the synchronous "wait for
222 o "ver": The number of times since boot that the RCU writer task
Drcubarrier.txt6 of as a replacement for read-writer locking (among other things), but with
19 How can an RCU writer possibly determine when all readers are finished,
DwhatisRCU.txt604 and release a global reader-writer lock. The synchronize_rcu()
612 It is possible to nest rcu_read_lock(), since reader-writer locks may
681 RCU is analogous to reader-writer locking. The following unified
682 diff shows how closely related RCU and reader-writer locking can be.
775 a reader-writer lock to a simple spinlock, and a synchronize_rcu()
DRTFP.txt1599 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
1602 the semantics of reader-writer locking. This is a recursive
/linux-4.4.14/Documentation/locking/
Dspinlocks.txt45 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
Dlocktorture.txt33 ownership (readers). The default is the same amount of writer
119 (B): Number of writer lock acquisitions. If dealing with a read/write primitive
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt162 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-4.4.14/Documentation/
Dlocal_ops.txt72 synchronization is done by the writer CPU, an outdated copy of the
114 respectively on the writer and the reader CPUs. It would be the case if you use
Ddevices.txt3212 /dev/cdwriter CD-writer symbolic Current CD-writer device
/linux-4.4.14/arch/x86/kernel/
Dapm_32.c342 unsigned int writer: 1; member
1198 if (!as->suser || !as->writer) in queue_event()
1526 if (!as->suser || !as->writer) in do_ioctl()
1624 as->writer = (filp->f_mode & FMODE_WRITE) == FMODE_WRITE; in do_open()
/linux-4.4.14/Documentation/video4linux/cx2341x/
Dfw-dma.txt20 allocate. Even still, 128K blocks are hard to come by, so the driver writer is
/linux-4.4.14/fs/jfs/
Djfs_logmgr.c215 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()
/linux-4.4.14/Documentation/cdrom/
Dpacket-writing.txt16 - Setup your writer
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt52 the server during system writeback. Only one writer at a time is allowed for any
/linux-4.4.14/Documentation/scsi/
Dhptiop.txt145 - Post the inbound list writer pointer to IOP.
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-firmware-acpi73 can do a anything the BIOS writer wants from
/linux-4.4.14/fs/cramfs/
DREADME114 `always use little-endian' (like ext2fs) or `writer chooses
/linux-4.4.14/Documentation/connector/
Dconnector.txt21 driver writer must create special sockets, must know about struct sk_buff
/linux-4.4.14/drivers/usb/storage/
DKconfig139 and Fujifilm DPC-R1 USB Card reader/writer devices.
/linux-4.4.14/fs/afs/
Dinternal.h146 struct work_struct writer; /* work item to perform the writeback */ member
/linux-4.4.14/Documentation/laptops/
Ddisk-shock-protection.txt95 device per port. Even if the CD/DVD writer happens to be connected to
/linux-4.4.14/drivers/block/
DKconfig403 DVD/CD writer.
/linux-4.4.14/Documentation/filesystems/
Drelay.txt121 time even if there's an active kernel writer. If the
/linux-4.4.14/drivers/net/wireless/
Dairo.c7860 static int (* writer)(struct airo_info *, u16 rid, const void *, int, int); in writerids() local
7871 writer = do_writerid; in writerids()
7884 case AIROPWEPKEY: ridcode = RID_WEP_TEMP; writer = PC4500_writerid; in writerids()
7953 if((*writer)(ai, ridcode, iobuf,comp->len,1)) { in writerids()
/linux-4.4.14/Documentation/virtual/kvm/
Dmmu.txt230 to detect in-progress updates and retry them until the writer has
/linux-4.4.14/Documentation/power/
Dpci.txt150 writer can provide the kernel with a means to perform actions depending
157 only be used to handle devices that the BIOS writer knew about in advance. The
/linux-4.4.14/Documentation/cgroups/
Dunified-hierarchy.txt274 writer must also have write access to the "cgroup.procs" file of the
/linux-4.4.14/drivers/scsi/
DKconfig163 writer software look at Cdrtools
/linux-4.4.14/
DCREDITS2645 D: PS/2 mouse driver writer etc.