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

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:each (Results 1 – 25 of 4569) sorted by relevance

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

/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A D	floating-point.json	12 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 21 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 39 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 48 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 52 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/linux/tools/perf/pmu-events/arch/x86/rocketlake/
H A D	floating-point.json	12 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 21 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 39 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 48 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 52 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A D	floating-point.json	12 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 21 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 39 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 48 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 52 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/linux/tools/perf/pmu-events/arch/x86/icelake/
H A D	floating-point.json	12 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 21 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 39 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 43 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 48 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 52 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	floating-point.json	7 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 39 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 43 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… 48 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 52 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 57 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 61 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… [all …]
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/
H A D	cache.json	114 …"PublicDescription": "L2 cache write streaming mode. This event counts for each cycle where the co… 117 …"BriefDescription": "L2 cache write streaming mode. This event counts for each cycle where the cor… 120 …ion": "L1 data cache entering write streaming mode. This event counts for each entry into write st… 123 …ion": "L1 data cache entering write streaming mode. This event counts for each entry into write st… 126 …"PublicDescription": "L1 data cache write streaming mode. This event counts for each cycle where t… 129 …"BriefDescription": "L1 data cache write streaming mode. This event counts for each cycle where th… 132 …"PublicDescription": "L3 cache write streaming mode. This event counts for each cycle where the co… 135 …"BriefDescription": "L3 cache write streaming mode. This event counts for each cycle where the cor… 138 …"PublicDescription": "Last level cache write streaming mode. This event counts for each cycle wher… 141 …"BriefDescription": "Last level cache write streaming mode. This event counts for each cycle where… [all …]
/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	floating-point.json	7 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 39 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 43 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… 48 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 52 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 57 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 61 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… [all …]
/linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/
H A D	trace.json	4 …"PublicDescription": "This event is generated each time the current write pointer is wrapped to th… 8 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 12 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 16 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 20 …"PublicDescription": "This event is generated each time an event is signaled by ETE external event… 24 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger… 28 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger… 32 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger… 36 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger…
/linux/Documentation/ABI/testing/
H A D	debugfs-scmi-raw	11 Each write to the entry causes one command request to be built 13 (receiving an EOF at each message boundary). 29 Each write to the entry causes one command request to be built 31 (receiving an EOF at each message boundary). 45 Each write to the entry causes one command request to be built 47 (receiving an EOF at each message boundary). 65 Each write to the entry causes one command request to be built 67 (receiving an EOF at each message boundary). 77 Each read gives back one message at time (receiving an EOF at 78 each message boundary). [all …]
/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/
H A D	cache.json	123 …"PublicDescription": "Level 2 cache write streaming mode. This event counts for each cycle where t… 126 …"BriefDescription": "Level 2 cache write streaming mode. This event counts for each cycle where th… 129 …: "Level 1 data cache entering write streaming mode.This event counts for each entry into write-st… 132 …: "Level 1 data cache entering write streaming mode.This event counts for each entry into write-st… 135 …"PublicDescription": "Level 1 data cache write streaming mode.This event counts for each cycle whe… 138 …"BriefDescription": "Level 1 data cache write streaming mode.This event counts for each cycle wher… 141 …"PublicDescription": "Level 3 cache write streaming mode.This event counts for each cycle where th… 144 …"BriefDescription": "Level 3 cache write streaming mode.This event counts for each cycle where the… 171 …This event counts on each access to the IPA cache. +//0 If a single pagewalk needs to make multipl… 174 …This event counts on each access to the IPA cache. +//0 If a single pagewalk needs to make multipl… [all …]
/linux/Documentation/admin-guide/mm/damon/
H A D	usage.rst	54 figure, parents-children relations are represented with indentations, each 55 directory is having ``/`` suffix, and files in each directory are separated by 116 child directories named ``0`` to ``N-1``. Each directory represents each 124 In each kdamond directory, two files (``state`` and ``pid``) and one directory 143 - ``update_schemes_stats``: Update the contents of stats files for each 147 action tried regions directory for each DAMON-based operation scheme of the 154 action tried regions directory for each DAMON-based operation scheme of the 157 ``effective_bytes`` files for each DAMON-based operation scheme of the 172 ``0`` to ``N-1``. Each directory represents each monitoring context (refer to 182 In each context directory, two files (``avail_operations`` and ``operations``) [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	floating-point.json	3 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 7 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 12 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 21 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 39 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 43 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	floating-point.json	3 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 7 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 12 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 21 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 39 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 43 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwell/
H A D	floating-point.json	3 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 7 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 12 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 21 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 30 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 39 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 43 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… [all …]
/linux/lib/842/
H A D	842.h	6 /* The 842 compressed format is made up of multiple blocks, each of 12 * template operation. For normal operations, each arg is either a specific 18 * table, the static "decomp_ops" table used in decompress. For each template 19 * (table row), there are between 1 and 4 actions; each action corresponds to 20 * an arg following the template code bits. Each action is either a "data" 21 * type action, or a "index" type action, and each action results in 2, 4, or 8 22 * bytes being written to the output buffer. Each template (i.e. all actions 36 * The number of bits for each index's arg are: 8 bits for I2, 9 bits for I4, 37 * and 8 bits for I8. Since each index points to a 2, 4, or 8 byte section, 41 * each of I2, I4, and I8 that are updated for each byte written to the output [all …]
/linux/Documentation/filesystems/nfs/
H A D	pnfs.rst	6 reference multiple devices, each of which can reference multiple data servers. 7 Each data server can be referenced by multiple devices. Each device 17 Each nfs_inode may hold a pointer to a cache of these layout 20 We reference the header for the inode pointing to it, across each 22 LAYOUTCOMMIT), and for each lseg held within. 24 Each header is also (when non-empty) put on a list associated with 34 nfs4_deviceid_cache). The cache itself is referenced across each 36 the lifetime of each lseg referencing them. 66 layout types: "files", "objects", "blocks", and "flexfiles". For each
/linux/Documentation/hwmon/
H A D	ibmpowernv.rst	`18 'hwmon' populates the 'sysfs' tree having attribute files, each for a given 21 All the nodes in the DT appear under "/ibm,opal/sensors" and each valid node in 45 each OCC. Using this attribute each OCC can be asked to 58 each OCC. Using this attribute each OCC can be asked to 69 each OCC. Using this attribute each OCC can be asked to 80 each OCC. Using this attribute each OCC can be asked to`
/linux/Documentation/devicetree/bindings/pinctrl/
H A D	pinctrl-bindings.txt	5 controllers. Each pin controller must be represented as a node in device tree, 9 designated client devices. Again, each client device must be represented as a 16 device is inactive. Hence, each client device can define a set of named 35 For each client device individually, every pin state is assigned an integer 36 ID. These numbers start at 0, and are contiguous. For each state ID, a unique 37 property exists to define the pin configuration. Each state may also be 41 Each client device's own binding determines the set of states that must be 47 pinctrl-0: List of phandles, each pointing at a pin configuration 52 from multiple nodes for a single pin controller, each 65 pinctrl-1: List of phandles, each pointing at a pin configuration [all …]
/linux/tools/perf/pmu-events/arch/x86/skylake/
H A D	floating-point.json	7 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 16 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 34 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 39 …ructions will count twice as noted below. Each count represents 2 or/and 4 computation operations… 43 …uctions will count twice as noted below. Each count represents 2 or/and 4 computation operations,… 52 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … 61 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … 70 …instructions retired; some instructions will count twice as noted below. Each count represents 1 …
/linux/tools/perf/pmu-events/arch/x86/amdzen1/
H A D	floating-point.json	6 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 13 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 20 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 27 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 34 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 41 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 48 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 55 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 62 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may … 69 …each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipelines are and may …
/linux/Documentation/admin-guide/device-mapper/
H A D	vdo-design.rst	46 normal operation, each zone is assigned to a specific thread, and only that 48 Associated with each thread is a work queue. Each bio is associated with a 54 each zone has an implicit lock on the structures it manages for all its 58 Although each structure is divided into zones, this division is not 59 reflected in the on-disk representation of each data structure. Therefore, 60 the number of zones for each structure, and hence the number of threads, 61 can be reconfigured each time a vdo target is started. 83 Each block of data is hashed to produce a 16-byte block name. An index 90 storage, or reading and rehashing each block before overwriting it. 95 index as hints, and reads each indicated block to verify that it is indeed [all …]
/linux/Documentation/filesystems/
H A D	qnx6.rst	42 Each qnx6fs got two superblocks, each one having a 64bit serial number. 44 In write mode with reach new snapshot (after each synchronous write), the 53 Each superblock holds a set of root inodes for the different filesystem 55 Each of these root nodes holds information like total size of the stored 57 If the level value is 0, up to 16 direct blocks can be addressed by each 60 Level 1 adds an additional indirect addressing level where each indirect 79 0x1000 is the size reserved for each superblock - regardless of the 85 Each object in the filesystem is represented by an inode. (index node) 107 It is a specially formatted file containing records which associate each 146 Each data block (tree leaves) holds one long filename. That filename is [all …]
/linux/Documentation/devicetree/bindings/gpio/
H A D	nvidia,tegra186-gpio.yaml	37 aliases" in address space, each of which access the same underlying 42 implemented by the SoC. Each GPIO is assigned to a port, and a port may 43 control a number of GPIOs. Thus, each GPIO is named according to an 47 The number of ports implemented by each GPIO controller varies. The number 48 of implemented GPIOs within each port varies. GPIO registers within a 60 Each GPIO controller can generate a number of interrupt signals. Each 67 Each GPIO controller in fact generates multiple interrupts signals for 68 each set of ports. Each GPIO may be configured to feed into a specific 70 for each generated signal to be routed to a different CPU, thus allowing 71 different CPUs to each handle subsets of the interrupts within a port. [all …]
/linux/Documentation/userspace-api/
H A D	dma-buf-alloc-exchange.rst	60 A tuple of numbers, representing a color. Each element in the tuple is a 94 Each buffer must have an underlying format. This format describes the color 95 values provided for each pixel. Although each subsystem has its own format 101 Each ``DRM_FORMAT_*`` token describes the translation between a pixel 104 whether they are RGB or YUV, integer or floating-point, the size of each channel 108 For example, ``DRM_FORMAT_ARGB8888`` describes a format in which each pixel has 118 sample is stored for each 2x2 pixel grouping). 122 modifier is ``DRM_FORMAT_MOD_LINEAR``, describing a scheme in which each plane 149 Each pixel buffer must be accompanied by logical pixel dimensions. This refers 160 Each plane must therefore be described with an ``offset`` in bytes, which will be [all …]
/linux/Documentation/networking/
H A D	scaling.rst	30 applying a filter to each packet that assigns it to one of a small number 31 of logical flows. Packets for each flow are steered to a separate receive 41 implementation of RSS uses a 128-entry indirection table where each entry 82 for each CPU if the device supports enough queues, or otherwise at least 83 one for each memory domain, where a memory domain is a set of CPUs that 98 Each receive queue has a separate IRQ associated with it. The NIC triggers 101 that can route each interrupt to a particular CPU. The active mapping 106 affinity of each interrupt see Documentation/core-api/irq/irq-affinity.rst. Some systems 122 interrupts (and thus work) grows with each additional queue. 125 processors with hyperthreading (HT), each hyperthread is represented as [all …]

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