write (full) in projects: Linux-v5.4 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:write (Results 1 – 25 of 7240) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...290

/Linux-v5.4/Documentation/driver-api/md/
D	raid5-cache.rst	7 caches data to the RAID disks. The cache can be in write-through (supported 8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since 9 3.4) has a new option '--write-journal' to create array with cache. Please 11 in write-through mode. A user can switch it to write-back mode by:: 13 echo "write-back" > /sys/block/md0/md/journal_mode 15 And switch it back to write-through mode by:: 17 echo "write-through" > /sys/block/md0/md/journal_mode 22 write-through mode 25 This mode mainly fixes the 'write hole' issue. For RAID 4/5/6 array, an unclean 27 and parity don't match. The reason is that a stripe write involves several RAID [all …]
/Linux-v5.4/tools/perf/pmu-events/arch/arm64/
D	armv8-recommended.json	9 "PublicDescription": "Attributable Level 1 data cache access, write", 12 "BriefDescription": "L1D cache access, write" 21 "PublicDescription": "Attributable Level 1 data cache refill, write", 24 "BriefDescription": "L1D cache refill, write" 39 "PublicDescription": "Attributable Level 1 data cache Write-Back, victim", 42 "BriefDescription": "L1D cache Write-Back, victim" 45 "PublicDescription": "Level 1 data cache Write-Back, cleaning and coherency", 48 "BriefDescription": "L1D cache Write-Back, cleaning and coherency" 63 "PublicDescription": "Attributable Level 1 data TLB refill, write", 66 "BriefDescription": "L1D tlb refill, write" [all …]
/Linux-v5.4/arch/arm/mach-pxa/include/mach/
D	regs-uart.h	12 #define FFTHR __REG(0x40100000) /* Transmit Holding Register (write only) / 13 #define FFIER __REG(0x40100004) / Interrupt Enable Register (read/write) / 15 #define FFFCR __REG(0x40100008) / FIFO Control Register (write only) / 16 #define FFLCR __REG(0x4010000C) / Line Control Register (read/write) / 17 #define FFMCR __REG(0x40100010) / Modem Control Register (read/write) / 20 #define FFSPR __REG(0x4010001C) / Scratch Pad Register (read/write) / 21 #define FFISR __REG(0x40100020) / Infrared Selection Register (read/write) / 22 #define FFDLL __REG(0x40100000) / Divisor Latch Low Register (DLAB = 1) (read/write) / 23 #define FFDLH __REG(0x40100004) / Divisor Latch High Register (DLAB = 1) (read/write) / 28 #define BTTHR __REG(0x40200000) / Transmit Holding Register (write only) */ [all …]
/Linux-v5.4/Documentation/media/uapi/v4l/
D	func-write.rst	10 .. _func-write: 13 V4L2 write() 19 v4l2-write - Write to a V4L2 device 30 .. c:function:: ssize_t write( int fd, void *buf, size_t count ) 31 :name: v4l2-write 48 :ref:`write() <func-write>` writes up to ``count`` bytes to the device 51 enables them. When ``count`` is zero, :ref:`write() <func-write>` returns 0 65 variable is set appropriately. In this case the next write will start at 71 available to write the data immediately. 77 The driver does not support multiple write streams and the device is [all …]
/Linux-v5.4/arch/mips/kernel/
D	cps-vec-ns16550.S	18 * _mips_cps_putc() - write a character to the UART 19 * @a0: ASCII character to write 31 * _mips_cps_puts() - write a string to the UART 35 * Write a null-terminated ASCII string to the UART. 51 * _mips_cps_putx4 - write a 4b hex value to the UART 52 * @a0: the 4b value to write to the UART 55 * Write a single hexadecimal character to the UART. 68 * _mips_cps_putx8 - write an 8b hex value to the UART 69 * @a0: the 8b value to write to the UART 72 * Write an 8 bit value (ie. 2 hexadecimal characters) to the UART. [all …]
/Linux-v5.4/tools/perf/pmu-events/arch/s390/cf_z13/
D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/Linux-v5.4/arch/parisc/kernel/
D	perf_asm.S	`556 ;* arg1 = 64-bit value to write 586 ; RDR 0 write sequence 588 sync ; RDR 0 write sequence 598 ; RDR 1 write sequence 610 ; RDR 2 write sequence 622 ; RDR 3 write sequence 634 ; RDR 4 write sequence 646 ; RDR 5 write sequence 658 ; RDR 6 write sequence 670 ; RDR 7 write sequence [all …]`
/Linux-v5.4/fs/ubifs/
D	io.c	16 * write-buffering support. Write buffers help to save space which otherwise 18 * Instead, data first goes to the write-buffer and is flushed when the 22 * UBIFS distinguishes between minimum write size (@c->min_io_size) and maximum 23 * write size (@c->max_write_size). The latter is the maximum amount of bytes 26 * @c->min_io_size <= @c->max_write_size. Write-buffers are of 28 * write-buffer is flushed, only the portion of it (aligned to @c->min_io_size 29 * boundary) which contains data is written, not the whole write-buffer, 33 * hand, we want to write in optimal @c->max_write_size bytes chunks, which 35 * other hand, we do not want to waste space when synchronizing the write 37 * the next write offset to be not aligned to @c->max_write_size bytes. So the [all …]
/Linux-v5.4/arch/sh/include/asm/
D	watchdog.h	`73 * sh_wdt_write_cnt - Write to Counter 74 * @val: Value to write 77 * The upper byte is set manually on each write. 85 * sh_wdt_write_bst - Write to Counter 86 * @val: Value to write 89 * The upper byte is set manually on each write. 106 * sh_wdt_write_csr - Write to Control/Status Register 107 * @val: Value to write 110 * register. The upper byte is set manually on each write. 127 * sh_wdt_write_cnt - Write to Counter [all …]`
/Linux-v5.4/tools/perf/pmu-events/arch/s390/cf_z14/
D	extended.json	7 …"PublicDescription": "L1D_RO_EXCL_WRITES A directory write to the Level-1 Data cache where the lin… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/Linux-v5.4/tools/perf/pmu-events/arch/s390/cf_z15/
D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/Linux-v5.4/kernel/
D	sysctl.c	185 * enum sysctl_writes_mode - supported sysctl write modes 187 * @SYSCTL_WRITES_LEGACY: each write syscall must fully contain the sysctl value 195 * sent to the write syscall. If dealing with strings respect the file 200 * These write modes control how current file position affects the behavior of 201 * updating sysctl values through the proc interface on each write. 211 static int proc_do_cad_pid(struct ctl_table table, int write, 213 static int proc_taint(struct ctl_table table, int write, 218 static int proc_dointvec_minmax_sysadmin(struct ctl_table table, int write, 222 static int proc_dointvec_minmax_coredump(struct ctl_table table, int write, 225 static int proc_dostring_coredump(struct ctl_table *table, int write, [all …]
/Linux-v5.4/tools/perf/pmu-events/arch/x86/skylakex/
D	uncore-memory.json	13 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr", 77 "BriefDescription": "DRAM Page Activate commands sent due to a write request", 82 …ption": "Counts DRAM Page Activate commands sent on this channel due to a write request to the iMC… 92 …write on DRAM, so this event increments for every read and write. This event counts whether AutoPr… 112 …write on DRAM, and this event increments for every regular read. This event only counts regular r… 122 …write, on a per channel basis. CAS commands are issued to specify the address to read or write on… 127 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr", 155 "BriefDescription": "Write Pending Queue Allocations", 160 …Write Pending Queue (WPQ). The WPQ is used to schedule writes out to the memory controller and to… 164 "BriefDescription": "Write Pending Queue Occupancy", [all …]
/Linux-v5.4/drivers/gpu/drm/i2c/
D	tda998x_drv.c	97 * write a given register, we need to make sure CURPAGE register is set 105 #define REG_CURPAGE 0xff /* write / 110 #define REG_MAIN_CNTRL0 REG(0x00, 0x01) / read/write / 118 #define REG_SOFTRESET REG(0x00, 0x0a) / write / 121 #define REG_DDC_DISABLE REG(0x00, 0x0b) / read/write / 122 #define REG_CCLK_ON REG(0x00, 0x0c) / read/write / 123 #define REG_I2C_MASTER REG(0x00, 0x0d) / read/write / 127 #define REG_FEAT_POWERDOWN REG(0x00, 0x0e) / read/write / 131 #define REG_INT_FLAGS_0 REG(0x00, 0x0f) / read/write / 132 #define REG_INT_FLAGS_1 REG(0x00, 0x10) / read/write */ [all …]
/Linux-v5.4/drivers/staging/comedi/drivers/
D	ni_660x.c	99 [NITIO_G0_INT_ACK] = { 0x004, 2 }, /* write / 101 [NITIO_G1_INT_ACK] = { 0x006, 2 }, / write / 104 [NITIO_G0_CMD] = { 0x00c, 2 }, / write / 106 [NITIO_G1_CMD] = { 0x00e, 2 }, / write / 109 [NI660X_STC_DIO_OUTPUT] = { 0x014, 2 }, / write / 110 [NI660X_STC_DIO_CONTROL] = { 0x016, 2 }, / write / 113 [NITIO_G0_MODE] = { 0x034, 2 }, / write / 115 [NITIO_G1_MODE] = { 0x036, 2 }, / write / 117 [NITIO_G0_LOADA] = { 0x038, 4 }, / write / 119 [NITIO_G0_LOADB] = { 0x03c, 4 }, / write */ [all …]
D	pcl730.c	40 * offset to the (insn_bits) functions to read/write the correct 45 BASE+0 Isolated outputs 0-7 (write) / inputs 0-7 (read) 46 * BASE+1 Isolated outputs 8-15 (write) / inputs 8-15 (read) 47 * BASE+2 TTL outputs 0-7 (write) / inputs 0-7 (read) 48 * BASE+3 TTL outputs 8-15 (write) / inputs 8-15 (read) 54 * BASE+0 Isolated outputs 0-7 (write) (read back on p8r8dio) 59 * BASE+0 Isolated outputs 0-7 (write) (read back) 60 * BASE+1 Isolated outputs 8-15 (write) (read back) 66 * BASE+0 Isolated outputs 0-7 (write) or inputs 0-7 (read) 67 * BASE+1 Isolated outputs 8-15 (write) or inputs 8-15 (read) [all …]
/Linux-v5.4/tools/perf/pmu-events/arch/s390/cf_zec12/
D	extended.json	21 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 28 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 35 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 49 …"PublicDescription": "A directory write to the Level-1 Data cache where the installed cache line w… 56 …"PublicDescription": "A directory write to the Level-1 Instruction cache where the installed cache… 63 …"PublicDescription": "A directory write to the Level-1 D-Cache where the line was originally in a … 105 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
/Linux-v5.4/drivers/iio/dac/
D	ad5446.c	`50 * @write: chip specific helper function to write to the register 56 int (write)(struct ad5446_state st, unsigned val); member 123 ret = st->chip_info->write(st, val); in ad5446_write_dac_powerdown() 133 .write = ad5446_write_dac_powerdown, 201 ret = st->chip_info->write(st, val); in ad5446_write_raw() 346 .write = ad5446_write, 350 .write = ad5446_write, 354 .write = ad5446_write, 358 .write = ad5446_write, 362 .write = ad5446_write, [all …]`
/Linux-v5.4/Documentation/ABI/testing/
D	sysfs-block-zram	5 The disksize file is read-write and specifies the disk size 21 The reset file is write-only and allows resetting the 29 The max_comp_streams file is read-write and specifies the 37 The comp_algorithm file is read-write and lets to show 45 The mem_used_max file is write-only and is used to reset 47 compressed data. For resetting the value, you should write 55 The mem_limit file is write-only and specifies the maximum 64 The compact file is write-only and trigger compaction for 98 The backing_dev file is read-write and set up backing 99 device for zram to write incompressible pages. [all …]
/Linux-v5.4/include/uapi/linux/
D	virtio_mmio.h	58 /* Device (host) features set selector - Write Only / 62 (32 bits per set) - Write Only / 65 / Activated features set selector - Write Only / 71 / Guest's memory page size in bytes - Write Only / 77 / Queue selector - Write Only / 83 / Queue size for the currently selected queue - Write Only / 89 / Used Ring alignment for the currently selected queue - Write Only / 92 / Guest's PFN for the currently selected queue - Read Write / 98 / Ready bit for the currently selected queue - Read Write / 101 / Queue notifier - Write Only */ [all …]
/Linux-v5.4/arch/powerpc/sysdev/
D	fsl_85xx_cache_ctlr.h	40 u32 ewar0; /* 0x010 - External write address 0 / 41 u32 ewarea0; / 0x014 - External write address extended 0 / 42 u32 ewcr0; / 0x018 - External write ctrl / 44 u32 ewar1; / 0x020 - External write address 1 / 45 u32 ewarea1; / 0x024 - External write address extended 1 / 46 u32 ewcr1; / 0x028 - External write ctrl 1 / 48 u32 ewar2; / 0x030 - External write address 2 / 49 u32 ewarea2; / 0x034 - External write address extended 2 / 50 u32 ewcr2; / 0x038 - External write ctrl 2 / 52 u32 ewar3; / 0x040 - External write address 3 */ [all …]
/Linux-v5.4/drivers/rtc/
D	rtc-pm8xxx.c	29 * @write: base address of write register 33 * @alarm_rw: base address of alarm read-write register 38 unsigned int write; member 67 * Steps to write the RTC registers. 70 * 3. Write 0x00 to LSB. 71 * 4. Write Byte[1], Byte[2], Byte[3] then Byte[0]. 107 dev_err(dev, "Write to RTC Alarm control register failed\n"); in pm8xxx_rtc_set_time() 122 dev_err(dev, "Write to RTC control register failed\n"); in pm8xxx_rtc_set_time() 127 /* Write 0 to Byte[0] */ in pm8xxx_rtc_set_time() 128 rc = regmap_write(rtc_dd->regmap, regs->write, 0); in pm8xxx_rtc_set_time() [all …]
/Linux-v5.4/Documentation/scsi/
D	sd-parameters.txt	`6 Enable/disable drive write & read cache. 8 cache_type string \| WCE RCD \| Write cache \| Read cache 10 write through \| 0 0 \| off \| on 12 write back \| 1 0 \| on \| on 13 write back, no read (daft) \| 1 1 \| on \| off 15 To set cache type to "write back" and save this setting to the drive: 17 # echo "write back" > cache_type 22 # echo "temporary write back" > cache_type`
/Linux-v5.4/fs/proc/
D	proc_net.c	66 if (file->f_mode & FMODE_WRITE && !PDE(inode)->write) in seq_open_net() 96 .write = proc_simple_write, 124 * @write: The write method which which to 'modify' the file. 135 * The @write function is called with the data copied into a kernel space 137 * modified by the @write function. @write should return 0 on success. 139 * The @data value is accessible from the @show and @write functions by calling 146 proc_write_t write, in proc_create_net_data_write() argument 158 p->write = write; in proc_create_net_data_write() 189 .write = proc_simple_write, 216 * @write: The write method which which to 'modify' the file. [all …]
/Linux-v5.4/tools/testing/selftests/bpf/verifier/
D	direct_value_access.c	`2 "direct map access, write test 1", 14 "direct map access, write test 2", 26 "direct map access, write test 3", 38 "direct map access, write test 4", 50 "direct map access, write test 5", 62 "direct map access, write test 6", 74 "direct map access, write test 7", 86 "direct map access, write test 8", 98 "direct map access, write test 9", 110 "direct map access, write test 10", [all …]`

12 3 4 5 6 7 8 9 10 >>...290