Home
last modified time | relevance | path

Searched +full:write +full:- +full:to +full:- +full:read (Results 1 – 25 of 1216) sorted by relevance

12345678910>>...49

/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/freescale/imx8mp/sys/
Dmetrics.json3 "BriefDescription": "bytes of all masters read from ddr",
5 "MetricExpr": "imx8_ddr0@axid\\-read\\,axi_mask\\=0xffff\\,axi_id\\=0x0000@",
6 "ScaleUnit": "9.765625e-4KB",
11 "BriefDescription": "bytes of all masters write to ddr",
13 "MetricExpr": "imx8_ddr0@axid\\-write\\,axi_mask\\=0xffff\\,axi_id\\=0x0000@",
14 "ScaleUnit": "9.765625e-4KB",
19 "BriefDescription": "bytes of a53 core read from ddr",
21 "MetricExpr": "imx8_ddr0@axid\\-read\\,axi_mask\\=0x0000\\,axi_id\\=0x0000@",
22 "ScaleUnit": "9.765625e-4KB",
27 "BriefDescription": "bytes of a53 core write to ddr",
[all …]
/kernel/linux/linux-6.6/drivers/net/ethernet/aquantia/atlantic/macsec/
Dmacsec_api.h1 /* SPDX-License-Identifier: GPL-2.0-only */
48 /*! Read the raw table data from the specified row of the Egress CTL
50 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
51 * table_index - The table row to read (max 23).
57 /*! Pack the fields of rec, and write the packed data into the
59 * rec - [IN] The bitfield values to write to the table row.
60 * table_index - The table row to write(max 23).
66 /*! Read the raw table data from the specified row of the Egress
68 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
69 * table_index - The table row to read (max 47).
[all …]
/kernel/linux/linux-5.10/drivers/net/ethernet/aquantia/atlantic/macsec/
Dmacsec_api.h1 /* SPDX-License-Identifier: GPL-2.0-only */
48 /*! Read the raw table data from the specified row of the Egress CTL
50 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
51 * table_index - The table row to read (max 23).
57 /*! Pack the fields of rec, and write the packed data into the
59 * rec - [IN] The bitfield values to write to the table row.
60 * table_index - The table row to write(max 23).
66 /*! Read the raw table data from the specified row of the Egress
68 * rec - [OUT] The raw table row data will be unpacked into the fields of rec.
69 * table_index - The table row to read (max 47).
[all …]
/kernel/linux/linux-6.6/Documentation/filesystems/spufs/
Dspufs.rst1 .. SPDX-License-Identifier: GPL-2.0
10 spufs - the SPU file system
17 Broadband Engine Architecture in order to access Synergistic Processor
20 The file system provides a name space similar to posix shared memory or
21 message queues. Users that have write permissions on the file system
22 can use spu_create(2) to establish SPU contexts in the spufs root.
26 logical SPU. Users can change permissions on those files, but not actu-
43 The files in spufs mostly follow the standard behavior for regular sys-
44 tem calls like read(2) or write(2), but often support only a subset of
49 All files that support the read(2) operation also support readv(2) and
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/spufs/
Dspufs.rst1 .. SPDX-License-Identifier: GPL-2.0
10 spufs - the SPU file system
17 Broadband Engine Architecture in order to access Synergistic Processor
20 The file system provides a name space similar to posix shared memory or
21 message queues. Users that have write permissions on the file system
22 can use spu_create(2) to establish SPU contexts in the spufs root.
26 logical SPU. Users can change permissions on those files, but not actu-
43 The files in spufs mostly follow the standard behavior for regular sys-
44 tem calls like read(2) or write(2), but often support only a subset of
49 All files that support the read(2) operation also support readv(2) and
[all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/
Duncore-memory.json3 "BriefDescription": "read requests to memory controller. Derived from unc_m_cas_count.rd",
7 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
13 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
17 …"PublicDescription": "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-p…
27 …channel. Activate commands are issued to open up a page on the DRAM devices so that it can be rea…
32 "BriefDescription": "DRAM Activate Count : Activate due to Bypass",
36 …to Bypass : Counts the number of DRAM Activate commands sent on this channel. Activate commands a…
50 "BriefDescription": "All DRAM read CAS commands issued (including underfills)",
54 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
59 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre",
[all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/
Duncore-memory.json3 "BriefDescription": "read requests to memory controller. Derived from unc_m_cas_count.rd",
13 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
50 "BriefDescription": "Pre-charges due to page misses",
59 "BriefDescription": "Pre-charge for reads",
68 "BriefDescription": "Pre-charge for writes",
77 …"BriefDescription": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC p…
85 …"BriefDescription": "Write requests allocated in the PMM Write Pending Queue for Intel Optane DC p…
93 …"BriefDescription": "Intel Optane DC persistent memory bandwidth read (MB). Derived from unc_m_pmm…
96 "EventName": "UNC_M_PMM_BANDWIDTH.READ",
98 "ScaleUnit": "6.103515625E-5MB",
[all …]
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/
Duncore-memory.json3 "BriefDescription": "read requests to memory controller. Derived from unc_m_cas_count.rd",
13 "BriefDescription": "write requests to memory controller. Derived from unc_m_cas_count.wr",
50 "BriefDescription": "Pre-charges due to page misses",
59 "BriefDescription": "Pre-charge for reads",
68 "BriefDescription": "Pre-charge for writes",
77 "BriefDescription": "DRAM Page Activate commands sent due to a write request",
82 …to a write request to the iMC (Memory Controller). Activate commands are issued to open up a page…
92 …to DRAM per memory channel. CAS commands are issued to specify the address to read or write on DR…
97 "BriefDescription": "All DRAM Read CAS Commands issued (does not include underfills)",
102 …read commands issued to DRAM on a per channel basis. CAS commands are issued to specify the addre…
[all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelakex/
Duncore-memory.json7 …channel. Activate commands are issued to open up a page on the DRAM devices so that it can be rea…
12 "BriefDescription": "DRAM Activate Count : Activate due to Bypass",
16 …to Bypass : Counts the number of DRAM Activate commands sent on this channel. Activate commands a…
30 "BriefDescription": "All DRAM read CAS commands issued (including underfills)",
34 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu…
39 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre",
43 …ommands. : DRAM RD_CAS commands w/auto-pre : DRAM RD_CAS and WR_CAS Commands : Counts the total nu…
57 "BriefDescription": "All DRAM read CAS commands issued (does not include underfills)",
61 …"PublicDescription": "Counts the total number of DRAM Read CAS commands issued on this channel. T…
66 "BriefDescription": "DRAM underfill read CAS commands issued",
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/
Dzonefs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ZoneFS - Zone filesystem for Zoned block devices
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
12 device support (e.g. f2fs), zonefs does not hide the sequential write
13 constraint of zoned block devices to the user. Files representing sequential
14 write zones of the device must be written sequentially starting from the end
17 As such, zonefs is in essence closer to a raw block device access interface
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
21 direct block device file ioctls which may be more obscure to developers. One
22 example of this approach is the implementation of LSM (log-structured merge)
[all …]
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-cti1 What: /sys/bus/coresight/devices/<cti-name>/enable
7 What: /sys/bus/coresight/devices/<cti-name>/powered
11 Description: (Read) Indicate if the CTI hardware is powered.
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
17 Description: (Read) Display the associated CTM ID
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
29 Description: (Read) Name of connected device <N>
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
[all …]
Dsysfs-platform-dfl-port1 What: /sys/bus/platform/devices/dfl-port.0/id
5 Description: Read-only. It returns id of this port. One DFL FPGA device
6 may have more than one port. Userspace could use this id to
9 What: /sys/bus/platform/devices/dfl-port.0/afu_id
13 Description: Read-only. User can program different PR bitstreams to FPGA
15 returns uuid which could be used to identify which PR bitstream
18 What: /sys/bus/platform/devices/dfl-port.0/power_state
22 Description: Read-only. It reports the APx (AFU Power) state, different APx
24 returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6.
26 What: /sys/bus/platform/devices/dfl-port.0/ap1_event
[all …]
Dsysfs-platform-dfl-fme1 What: /sys/bus/platform/devices/dfl-fme.0/ports_num
5 Description: Read-only. One DFL FPGA device may have more than 1
7 number of ports on the FPGA device when read it.
9 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_id
13 Description: Read-only. It returns Bitstream (static FPGA region)
17 What: /sys/bus/platform/devices/dfl-fme.0/bitstream_metadata
21 Description: Read-only. It returns Bitstream (static FPGA region) meta
25 What: /sys/bus/platform/devices/dfl-fme.0/cache_size
29 Description: Read-only. It returns cache size of this FPGA device.
31 What: /sys/bus/platform/devices/dfl-fme.0/fabric_version
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-cti1 What: /sys/bus/coresight/devices/<cti-name>/enable
7 What: /sys/bus/coresight/devices/<cti-name>/powered
11 Description: (Read) Indicate if the CTI hardware is powered.
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
17 Description: (Read) Display the associated CTM ID
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
29 Description: (Read) Name of connected device <N>
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
[all …]
Dsysfs-platform-dfl-port1 What: /sys/bus/platform/devices/dfl-port.0/id
5 Description: Read-only. It returns id of this port. One DFL FPGA device
6 may have more than one port. Userspace could use this id to
9 What: /sys/bus/platform/devices/dfl-port.0/afu_id
13 Description: Read-only. User can program different PR bitstreams to FPGA
15 returns uuid which could be used to identify which PR bitstream
18 What: /sys/bus/platform/devices/dfl-port.0/power_state
22 Description: Read-only. It reports the APx (AFU Power) state, different APx
24 returns "0" - Normal / "1" - AP1 / "2" - AP2 / "6" - AP6.
26 What: /sys/bus/platform/devices/dfl-port.0/ap1_event
[all …]
Dsysfs-class-bdi14 non-block filesystems which provide their own BDI, such as NFS
17 MAJOR:MINOR-fuseblk
23 The default backing dev, used for non-block device backed
30 Size of the read-ahead window in kilobytes
32 (read-write)
38 total write-back cache that relates to its current average
39 writeout speed in relation to the other devices.
42 percentage of the write-back cache to a particular device.
45 (read-write)
52 total write-back cache that relates to its current average
[all …]
/kernel/linux/linux-5.10/drivers/rtc/
Drtc-ds1685.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * An rtc driver for the Dallas/Maxim DS1685/DS1687 and related real-time
6 * Copyright (C) 2011-2014 Joshua Kinard <kumba@gentoo.org>.
7 * Copyright (C) 2009 Matthias Fuchs <matthias.fuchs@esd-electronics.com>.
10 * DS1685/DS1687 3V/5V Real-Time Clocks, 19-5215, Rev 4/10.
11 * DS17x85/DS17x87 3V/5V Real-Time Clocks, 19-5222, Rev 4/10.
12 * DS1689/DS1693 3V/5V Serialized Real-Time Clocks, Rev 112105.
33 /* ----------------------------------------------------------------------- */
35 * Standard read/write
40 * ds1685_read - read a value from an rtc register.
[all …]
/kernel/linux/linux-6.6/drivers/rtc/
Drtc-ds1685.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * An rtc driver for the Dallas/Maxim DS1685/DS1687 and related real-time
6 * Copyright (C) 2011-2014 Joshua Kinard <kumba@gentoo.org>.
7 * Copyright (C) 2009 Matthias Fuchs <matthias.fuchs@esd-electronics.com>.
10 * DS1685/DS1687 3V/5V Real-Time Clocks, 19-5215, Rev 4/10.
11 * DS17x85/DS17x87 3V/5V Real-Time Clocks, 19-5222, Rev 4/10.
12 * DS1689/DS1693 3V/5V Serialized Real-Time Clocks, Rev 112105.
33 /* ----------------------------------------------------------------------- */
35 * Standard read/write
40 * ds1685_read - read a value from an rtc register.
[all …]
/kernel/linux/linux-6.6/tools/testing/selftests/kvm/lib/
Dio.c1 // SPDX-License-Identifier: GPL-2.0-only
10 /* Test Write
12 * A wrapper for write(2), that automatically handles the following
16 * + Write of less than requested amount
17 * + Non-block return (EAGAIN)
19 * For each of the above, an additional write is performed to automatically
21 * There are also many cases where write(2) can return an unexpected
24 * Note, for function signature compatibility with write(2), this function
26 * to the number of requested bytes. All other conditions in this and
27 * future enhancements to this function either automatically issue another
[all …]
/kernel/linux/linux-5.10/tools/testing/selftests/kvm/lib/
Dio.c1 // SPDX-License-Identifier: GPL-2.0-only
10 /* Test Write
12 * A wrapper for write(2), that automatically handles the following
16 * + Write of less than requested amount
17 * + Non-block return (EAGAIN)
19 * For each of the above, an additional write is performed to automatically
21 * There are also many cases where write(2) can return an unexpected
24 * Note, for function signature compatibility with write(2), this function
26 * to the number of requested bytes. All other conditions in this and
27 * future enhancements to this function either automatically issue another
[all …]
/kernel/linux/linux-5.10/arch/parisc/kernel/
Dperf_asm.S1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 /* low-level asm for "intrigue" (PA8500-8700 CPU perf counters)
5 * Copyright (C) 2001 Randolph Chung <tausq at parisc-linux.org>
6 * Copyright (C) 2001 Hewlett-Packard (Grant Grundler)
30 ; The coprocessor only needs to be enabled when
45 ssm 0,0 ; dummy op to ensure completion
71 ssm 0,0 ; dummy op to ensure completion
86 ;* is shifted shifted backup immediately. This is to compensate
91 ;* arg0 : rdr to be read
98 ;* arg0 : rdr to be read
[all …]
/kernel/linux/linux-6.6/arch/parisc/kernel/
Dperf_asm.S1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 /* low-level asm for "intrigue" (PA8500-8700 CPU perf counters)
5 * Copyright (C) 2001 Randolph Chung <tausq at parisc-linux.org>
6 * Copyright (C) 2001 Hewlett-Packard (Grant Grundler)
30 ; The coprocessor only needs to be enabled when
45 ssm 0,0 ; dummy op to ensure completion
71 ssm 0,0 ; dummy op to ensure completion
86 ;* is shifted shifted backup immediately. This is to compensate
91 ;* arg0 : rdr to be read
98 ;* arg0 : rdr to be read
[all …]
/kernel/linux/linux-6.6/Documentation/filesystems/
Dzonefs.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ZoneFS - Zone filesystem for Zoned block devices
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
12 device support (e.g. f2fs), zonefs does not hide the sequential write
13 constraint of zoned block devices to the user. Files representing sequential
14 write zones of the device must be written sequentially starting from the end
17 As such, zonefs is in essence closer to a raw block device access interface
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
21 direct block device file ioctls which may be more obscure to developers. One
22 example of this approach is the implementation of LSM (log-structured merge)
[all …]
/kernel/linux/linux-6.6/Documentation/locking/
Dseqlock.rst8 Sequence counters are a reader-writer consistency mechanism with
9 lockless readers (read-only retry loops), and no writer starvation. They
10 are used for data that's rarely written to (e.g. system time), where the
11 reader wants a consistent set of information and is willing to retry if
15 read side critical section is even and the same sequence count value is
16 read again at the end of the critical section. The data in the set must
17 be copied out inside the read side critical section. If the sequence
23 is odd and indicates to the readers that an update is in progress. At
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
[all …]
/kernel/linux/linux-5.10/Documentation/locking/
Dseqlock.rst8 Sequence counters are a reader-writer consistency mechanism with
9 lockless readers (read-only retry loops), and no writer starvation. They
10 are used for data that's rarely written to (e.g. system time), where the
11 reader wants a consistent set of information and is willing to retry if
15 read side critical section is even and the same sequence count value is
16 read again at the end of the critical section. The data in the set must
17 be copied out inside the read side critical section. If the sequence
23 is odd and indicates to the readers that an update is in progress. At
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
[all …]

12345678910>>...49