writes (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:writes (Results 1 – 25 of 1537) sorted by relevance

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

/linux/tools/perf/pmu-events/arch/s390/cf_z13/
H A D	extended.json	6 "BriefDescription": "L1D Read-only Exclusive Writes", 13 "BriefDescription": "DTLB1 Writes", 27 "BriefDescription": "DTLB1 One-Megabyte Page Writes", 34 "BriefDescription": "DTLB1 Two-Gigabyte Page Writes", 41 "BriefDescription": "L1D L2D Sourced Writes", 48 "BriefDescription": "ITLB1 Writes", 62 "BriefDescription": "L1I L2I Sourced Writes", 69 "BriefDescription": "TLB2 PTE Writes", 76 "BriefDescription": "TLB2 CRSTE One-Megabyte Page Writes", 83 "BriefDescription": "TLB2 CRSTE Writes", [all …]
/linux/tools/perf/pmu-events/arch/s390/cf_z14/
H A D	extended.json	`6 "BriefDescription": "L1D Read-only Exclusive Writes", 13 "BriefDescription": "DTLB2 Writes", 27 "BriefDescription": "DTLB2 One-Megabyte Page Writes", 34 "BriefDescription": "DTLB2 Two-Gigabyte Page Writes", 41 "BriefDescription": "L1D L2D Sourced Writes", 48 "BriefDescription": "ITLB2 Writes", 62 "BriefDescription": "L1I L2I Sourced Writes", 69 "BriefDescription": "TLB2 PTE Writes", 76 "BriefDescription": "TLB2 CRSTE Writes", 111 "BriefDescription": "L1D On-Chip L3 Sourced Writes", [all …]`
/linux/tools/perf/pmu-events/arch/s390/cf_zec12/
H A D	extended.json	20 "BriefDescription": "L1D L2I Sourced Writes", 27 "BriefDescription": "L1I L2I Sourced Writes", 34 "BriefDescription": "L1D L2D Sourced Writes", 41 "BriefDescription": "DTLB1 Writes", 48 "BriefDescription": "L1D Local Memory Sourced Writes", 55 "BriefDescription": "L1I Local Memory Sourced Writes", 62 "BriefDescription": "L1D Read-only Exclusive Writes", 69 "BriefDescription": "DTLB1 One-Megabyte Page Writes", 76 "BriefDescription": "ITLB1 Writes", 83 "BriefDescription": "TLB2 PTE Writes", [all …]
/linux/tools/perf/pmu-events/arch/s390/cf_z15/
H A D	extended.json	`6 "BriefDescription": "L1D Read-only Exclusive Writes", 13 "BriefDescription": "DTLB2 Writes", 27 "BriefDescription": "DTLB2 One-Megabyte Page Writes", 34 "BriefDescription": "DTLB2 Two-Gigabyte Page Writes", 41 "BriefDescription": "L1D L2D Sourced Writes", 48 "BriefDescription": "ITLB2 Writes", 62 "BriefDescription": "L1I L2I Sourced Writes", 69 "BriefDescription": "TLB2 PTE Writes", 76 "BriefDescription": "TLB2 CRSTE Writes", 111 "BriefDescription": "L1D On-Chip L3 Sourced Writes", [all …]`
/linux/tools/perf/pmu-events/arch/s390/cf_z196/
H A D	extended.json	6 "BriefDescription": "L1D L2 Sourced Writes", 13 "BriefDescription": "L1I L2 Sourced Writes", 41 "BriefDescription": "L1D Off-Book L3 Sourced Writes", 48 "BriefDescription": "L1D On-Book L4 Sourced Writes", 55 "BriefDescription": "L1I On-Book L4 Sourced Writes", 62 "BriefDescription": "L1D Read-only Exclusive Writes", 69 "BriefDescription": "L1D Off-Book L4 Sourced Writes", 76 "BriefDescription": "L1I Off-Book L4 Sourced Writes", 83 "BriefDescription": "DTLB1 One-Megabyte Page Writes", 90 "BriefDescription": "L1D Local Memory Sourced Writes", [all …]
/linux/drivers/staging/gpib/ni_usb/
H A D	ni_usb_gpib.c	520 const struct ni_usb_register *writes, int num_writes, in ni_usb_write_registers() argument 541 i += ni_usb_bulk_register_write(&out_data[i], writes[j]); in ni_usb_write_registers() 1072 struct ni_usb_register writes[4]; in ni_usb_request_system_control() local 1079 writes[i].device = NIUSB_SUBDEV_TNT4882; in ni_usb_request_system_control() 1080 writes[i].address = CMDR; in ni_usb_request_system_control() 1081 writes[i].value = SETSC; in ni_usb_request_system_control() 1083 writes[i].device = NIUSB_SUBDEV_TNT4882; in ni_usb_request_system_control() 1084 writes[i].address = nec7210_to_tnt4882_offset(AUXMR); in ni_usb_request_system_control() 1085 writes[i].value = AUX_CIFC; in ni_usb_request_system_control() 1088 writes[i].device = NIUSB_SUBDEV_TNT4882; in ni_usb_request_system_control() [all …]
/linux/tools/perf/pmu-events/arch/s390/cf_z10/
H A D	extended.json	6 "BriefDescription": "L1I L2 Sourced Writes", 13 "BriefDescription": "L1D L2 Sourced Writes", 20 "BriefDescription": "L1I L3 Local Writes", 27 "BriefDescription": "L1D L3 Local Writes", 34 "BriefDescription": "L1I L3 Remote Writes", 41 "BriefDescription": "L1D L3 Remote Writes", 48 "BriefDescription": "L1D Local Memory Sourced Writes", 55 "BriefDescription": "L1I Local Memory Sourced Writes", 62 "BriefDescription": "L1D Read-only Exclusive Writes", 76 "BriefDescription": "ITLB1 Writes", [all …]
/linux/tools/perf/scripts/perl/
H A D	rw-by-pid.pl	`22 my %writes; 58 $writes{$common_pid}{errors}{$ret}++; 68 $writes{$common_pid}{bytes_written} += $count; 69 $writes{$common_pid}{total_writes}++; 70 $writes{$common_pid}{comm} = $common_comm; 119 "# writes", "bytes_written"); 123 foreach my $pid (sort { ($writes{$b}{bytes_written} \|\| 0) <=> 124 ($writes{$a}{bytes_written} \|\| 0)} keys %writes) { 125 my $comm = $writes{$pid}{comm} \|\| ""; 126 my $total_writes = $writes{$pid}{total_writes} \|\| 0; [all …]`
H A D	rwtop.pl	`28 my %writes; 75 $writes{$common_pid}{errors}{$ret}++; 87 $writes{$common_pid}{bytes_written} += $count; 88 $writes{$common_pid}{total_writes}++; 89 $writes{$common_pid}{comm} = $common_comm; 156 "# writes", "bytes_written"); 160 foreach my $pid (sort { ($writes{$b}{bytes_written} \|\| 0) <=> 161 ($writes{$a}{bytes_written} \|\| 0)} keys %writes) { 162 my $comm = $writes{$pid}{comm} \|\| ""; 163 my $total_writes = $writes{$pid}{total_writes} \|\| 0; [all …]`
H A D	rw-by-file.pl	`26 my %writes; 45 $writes{$fd}{bytes_written} += $count; 46 $writes{$fd}{total_writes}++; 66 printf("%6s %10s %10s\n", "fd", "# writes", "bytes_written"); 69 foreach my $fd (sort {$writes{$b}{bytes_written} <=> 70 $writes{$a}{bytes_written}} keys %writes) { 71 my $total_writes = $writes{$fd}{total_writes}; 72 my $bytes_written = $writes{$fd}{bytes_written};`
/linux/include/dt-bindings/memory/
H A D	tegra186-mc.h	`129 /* PCIE writes / 131 / High-definition audio (HDA) writes / 133 / Writes from Cortex-A9 4 CPU cores via the L2 cache / 135 / SATA writes / 145 / XUSB_HOST writes / 149 / XUSB_DEV writes / 157 / 3D, ltcx writes instance 0 / 183 / Audio Processing (APE) engine writes / 193 / ETR writes / 201 / 3D, ltcx writes instance 1 */`
/linux/Documentation/driver-api/md/
H A D	raid5-cache.rst	19 In both modes, all writes to the array will hit cache disk first. This means 28 disks and it's possible the writes don't hit all RAID disks yet before the 53 write. For non-full-stripe writes, MD must read old data before the new parity 54 can be calculated. These synchronous reads hurt write throughput. Some writes 90 order in which MD writes data to cache disk and RAID disks. Specifically, in 91 write-through mode, MD calculates parity for IO data, writes both IO data and 92 parity to the log, writes the data and parity to RAID disks after the data and 96 In write-back mode, MD writes IO data to the log and reports IO completion. The 110 they are discarded too. MD then loads valid data and writes them to RAID disks
/linux/Documentation/driver-api/
H A D	io_ordering.rst	`2 Ordering I/O writes to memory-mapped addresses 6 platforms, driver writers are responsible for ensuring that I/O writes to 9 chipset to flush pending writes to the device before any reads are posted. A 12 subsequent writes to I/O space arrived only after all prior writes (much like a 50 pending writes before actually posting the read to the chipset, preventing`
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A D	uncore-io.json	353 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 365 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 377 …e. Includes all requests initiated by the main die, including reads and writes. : x8 card plugged… 389 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 401 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 413 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 425 …e. Includes all requests initiated by the main die, including reads and writes. : x8 card plugged… 437 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 462 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 0", 475 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 1", [all …]
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	uncore-io.json	433 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 445 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 457 …e. Includes all requests initiated by the main die, including reads and writes. : x8 card plugged… 469 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 481 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 493 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 505 …e. Includes all requests initiated by the main die, including reads and writes. : x8 card plugged… 517 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 542 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 0", 555 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 1", [all …]
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/
H A D	cache.json	114 …ch cycle where the core is in write streaming mode and is not allocating writes into the L2 cache", 117 …ach cycle where the core is in write streaming mode and is not allocating writes into the L2 cache" 126 …ch cycle where the core is in write streaming mode and is not allocating writes into the L1 data c… 129 …ch cycle where the core is in write streaming mode and is not allocating writes into the L1 data c… 132 …ch cycle where the core is in write streaming mode and is not allocating writes into the L3 cache", 135 …ach cycle where the core is in write streaming mode and is not allocating writes into the L3 cache" 138 …ch cycle where the core is in write streaming mode and is not allocating writes into the system ca… 141 …ch cycle where the core is in write streaming mode and is not allocating writes into the system ca…
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A D	uncore-io.json	13 …die. Includes all requests initiated by the Card, including reads and writes. : x16 card plugge… 29 …die. Includes all requests initiated by the Card, including reads and writes. : x16 card plugge… 372 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 0", 385 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 1", 398 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 411 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 424 …e. Includes all requests initiated by the main die, including reads and writes. : x8 card plugged… 437 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 450 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 463 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… [all …]
H A D	uncore-memory.json	400 "BriefDescription": "Pre-charge for writes", 552 … is used to schedule write out to the memory controller and to track the writes. Requests allocat… 563 … is used to schedule write out to the memory controller and to track the writes. Requests allocat… 573 … is used to schedule write out to the memory controller and to track the writes. Requests allocat… 583 … is used to schedule write out to the memory controller and to track the writes. Requests allocat… 593 …writes. Requests allocate into the WPQ soon after they enter the memory controller, and need cred… 602 …writes. Requests allocate into the WPQ soon after they enter the memory controller, and need cred… 612 …writes and reads to pass up other writes to different addresses. Before a read or a write is issu… 623 …writes and reads to pass up other writes to different addresses. Before a read or a write is issu… 634 …writes and reads to pass up other writes to different addresses. Before a read or a write is issu… [all …]
/linux/Documentation/admin-guide/device-mapper/
H A D	log-writes.rst	`2 dm-log-writes 24 the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only 25 completed WRITEs, at the time the REQ_PREFLUSH is issued, are added in order to 59 log-writes <dev_path> <log_dev_path> 93 Every log has a mark at the end labeled "dm-log-writes-end". 99 It can be found here: https://github.com/josefbacik/log-writes 107 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc" 127 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"`
/linux/Documentation/filesystems/fuse/
H A D	fuse-io.rst	`17 In direct-io mode the page cache is completely bypassed for reads and writes. 23 after any writes to the file. All mmap modes are supported. 25 The cached mode has two sub modes controlling how writes are handled. The 32 uncached, but fully written pages). No READ requests are ever sent for writes, 35 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to`
/linux/arch/mips/include/asm/vdso/
H A D	processor.h	`12 * Loongson-3's SFB (Store-Fill-Buffer) may buffer writes indefinitely when a 13 * tight read loop is executed, because reads take priority over writes & the 14 * hardware (incorrectly) doesn't ensure that writes will eventually occur. 17 * flush from cpu_relax() such that any pending writes will become visible as`
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A D	uncore-io.json	341 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 0", 354 …e. Includes all requests initiated by the main die, including reads and writes. : IOMMU - Type 1", 367 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 380 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 393 …e. Includes all requests initiated by the main die, including reads and writes. : x8 card plugged… 406 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 419 …e. Includes all requests initiated by the main die, including reads and writes. : x16 card plugge… 432 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… 445 …e. Includes all requests initiated by the main die, including reads and writes. : x8 card plugged… 458 …e. Includes all requests initiated by the main die, including reads and writes. : x4 card is plug… [all …]
/linux/tools/memory-model/Documentation/
H A D	access-marking.txt	77 4. Writes setting values that feed into error-tolerant heuristics. 91 concurrently with updates to x. Then using plain C-language writes 152 Writes Setting Values Feeding Into Error-Tolerant Heuristics 155 for example, from sysfs. This means that some code in sysfs writes 156 to this same variable, and these writes can also use data_race(). 201 b. When the store writes the value already contained in 253 and data_race() writes on the other, KCSAN will not report the location 254 of these data_race() writes. 312 buggy lockless writes, read_foo_diagnostic() can be updated as follows: 327 However, in order for KCSAN to detect buggy lockless writes, your kernel [all …]
/linux/drivers/firmware/cirrus/test/
H A D	cs_dsp_test_bin.c	23 * 1) Create a mock regmap in cache-only mode so that all writes will be cached. 32 * 8) If the cache is still dirty there have been unexpected writes. 154 /* Drop expected writes and the cache should then be clean / in bin_patch_one_word() 202 / Drop expected writes and the cache should then be clean / in bin_patch_one_multiword() 254 / Drop expected writes and the cache should then be clean / in bin_patch_multi_oneword() 312 / Drop expected writes and the cache should then be clean / in bin_patch_multi_oneword_unordered() 374 / Drop expected writes from the cache / in bin_patch_multi_oneword_sparse_unordered() 378 / Drop expected writes and the cache should then be clean / in bin_patch_multi_oneword_sparse_unordered() 476 / Drop expected writes from the cache / in bin_patch_one_word_multiple_mems() 480 / Drop expected writes and the cache should then be clean */ in bin_patch_one_word_multiple_mems() [all …]
/linux/tools/memory-model/litmus-tests/
H A D	README	21 successive writes to the same variable are ordered. 24 Test of independent reads from independent writes with smp_mb() 27 the order of a pair of writes, where each write is to a different 32 Test of independent reads from independent writes with nothing 35 order of a pair of writes, where each write is to a different 55 of two variables then writes to the other? 60 writes to the other? 104 process writes data and then a flag, and the other process reads 182 For example, if the one process writes to a pair of variables, and

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