each (full) in projects: Linux-v6.1 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/Linux-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/
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-v6.1/tools/perf/pmu-events/arch/x86/icelakex/
D	floating-point.json	15 …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 2 computation operations, one … 26 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 32 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 37 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 43 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 48 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 54 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 59 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 65 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/icelake/
D	floating-point.json	15 …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 2 computation operations, one … 26 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 32 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 37 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 43 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 48 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 54 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 59 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 65 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/tigerlake/
D	floating-point.json	14 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 20 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 25 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 31 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 36 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 42 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 47 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 53 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 58 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 64 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/cascadelakex/
D	floating-point.json	8 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 18 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 28 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 38 …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 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 53 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 58 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 68 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … 78 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/sapphirerapids/
D	floating-point.json	71 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 77 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 82 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 88 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 93 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 99 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 104 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 110 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 115 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 121 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/
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-v6.1/tools/perf/pmu-events/arch/x86/skylakex/
D	floating-point.json	8 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 18 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 28 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 38 …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 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 53 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 58 …nstructions will count twice as noted below. Each count represents 16 computation operations, one… 68 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … 78 …instructions retired; some instructions will count twice as noted below. Each count represents 1 …
/Linux-v6.1/Documentation/hwmon/
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-v6.1/Documentation/filesystems/nfs/
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-v6.1/lib/842/
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-v6.1/Documentation/devicetree/bindings/pinctrl/
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-v6.1/Documentation/admin-guide/mm/damon/
D	usage.rst	63 figure, parents-children relations are represented with indentations, each 64 directory is having ``/`` suffix, and files in each directory are separated by 107 are called DAMON context. DAMON executes each context with a kernel thread 113 of child directories named ``0`` to ``N-1``. Each directory represents each 119 In each kdamond directory, two files (``state`` and ``pid``) and one directory 127 for each DAMON-based operation scheme of the kdamond. For details of the 140 ``0`` to ``N-1``. Each directory represents each monitoring context. At the 147 In each context directory, two files (``avail_operations`` and ``operations``) 195 to ``N-1``. Each directory represents each monitoring target. 200 In each target directory, one file (``pid_target``) and one directory [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/broadwellx/
D	floating-point.json	3 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 8 …nstructions will count twice as noted below. Each count represents 2 computation operations, one … 13 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 18 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 23 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 28 …nstructions will count twice as noted below. Each count represents 4 computation operations, one … 33 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 38 …nstructions will count twice as noted below. Each count represents 8 computation operations, one … 61 … instructions retired; some instructions will count twice as noted below. Each count represents 1 … 66 …instructions retired; some instructions will count twice as noted below. Each count represents 1 … [all …]
/Linux-v6.1/tools/perf/pmu-events/arch/x86/amdzen1/
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-v6.1/Documentation/networking/
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 60 for each CPU if the device supports enough queues, or otherwise at least 61 one for each memory domain, where a memory domain is a set of CPUs that 76 Each receive queue has a separate IRQ associated with it. The NIC triggers 79 that can route each interrupt to a particular CPU. The active mapping 84 affinity of each interrupt see Documentation/core-api/irq/irq-affinity.rst. Some systems 100 interrupts (and thus work) grows with each additional queue. 103 processors with hyperthreading (HT), each hyperthread is represented as [all …]
/Linux-v6.1/Documentation/devicetree/bindings/gpio/
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-v6.1/Documentation/filesystems/
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-v6.1/Documentation/devicetree/bindings/dma/
D	st,stm32-mdma.yaml	13 described in the dma.txt file, using a five-cell specifier for each channel: 24 0x2: Source address pointer is incremented after each data transfer 25 0x3: Source address pointer is decremented after each data transfer 28 0x2: Destination address pointer is incremented after each data transfer 29 0x3: Destination address pointer is decremented after each data transfer 43 0x00: Each MDMA request triggers a buffer transfer (max 128 bytes) 44 0x1: Each MDMA request triggers a block transfer (max 64K bytes) 45 0x2: Each MDMA request triggers a repeated block transfer 46 0x3: Each MDMA request triggers a linked list transfer
/Linux-v6.1/Documentation/scheduler/
D	sched-domains.rst	5 Each CPU has a "base" scheduling domain (struct sched_domain). The domain 10 Each scheduling domain spans a number of CPUs (stored in the ->span field). 13 i. The top domain for each CPU will generally span all CPUs in the system 19 Each scheduling domain must have one or more CPU groups (struct sched_group) 29 Balancing within a sched domain occurs between groups. That is, each group 31 load of each of its member CPUs, and only when the load of a group becomes 34 In kernel/sched/core.c, trigger_load_balance() is run periodically on each CPU 59 of SMT, you'll span all siblings of the physical CPU, with each group being 63 node. Each group being a single physical CPU. Then with NUMA, the parent 64 of the SMP domain will span the entire machine, with each group having the
/Linux-v6.1/Documentation/ABI/testing/
D	sysfs-firmware-sgi_uv	31 machines, which each partition running a unique copy 32 of the operating system. Each partition will have a unique 55 The hubs directory contains a number of hub objects, each representing 56 a UV Hub visible to the BIOS. Each hub object's name is appended by a 59 Each hub object directory contains a number of read-only attributes:: 94 Each hub object directory also contains a number of port objects, 95 each representing a fabric port on the corresponding hub. 99 Each port object directory contains a number of read-only attributes:: 125 Each PCI bus object's name is appended by its PCI bus address. 128 Each pcibus object has a number of possible read-only attributes::
/Linux-v6.1/include/linux/
D	prime_numbers.h	`11 * for_each_prime_number - iterate over each prime upto a value 15 * Starting from the first prime number 2 iterate over each prime number up to 16 * the @max value. On each iteration, @prime is set to the current prime number. 25 * for_each_prime_number_from - iterate over each prime upto a value 30 * Starting from @from iterate over each successive prime number up to the 31 * @max value. On each iteration, @prime is set to the current prime number.`
/Linux-v6.1/Documentation/gpu/
D	msm-crash-dump.rst	`11 Each entry is in the form key: value. Sections headers will not have a value 13 Each section might have multiple array entries the start of which is designated 43 Section containing the contents of each ringbuffer. Each ringbuffer is 47 Ringbuffer ID (0 based index). Each ringbuffer in the section 73 Each buffer object will have a uinque iova. 86 Set of registers values. Each entry is on its own line enclosed`
/Linux-v6.1/Documentation/devicetree/bindings/phy/
D	apm-xgene-phy.txt	`3 PHY nodes are defined to describe on-chip 15Gbps Multi-purpose PHY. Each 19 Two set of 3-tuple setting for each (up to 3) 25 Two set of 3-tuple setting for each (up to 3) 28 gain control. Two set of 3-tuple setting for each 32 each (up to 3) supported link speed on the host. 36 3-tuple setting for each (up to 3) supported link 40 3-tuple setting for each (up to 3) supported link 46 - apm,tx-speed : Tx operating speed. One set of 3-tuple for each`
/Linux-v6.1/include/media/
D	v4l2-device.h	36 * Each instance of a V4L2 device should create the v4l2_device struct, 234 * @arg: arguments for the notification. Those are specific to each 267 * the @sd variable pointing to each sub-device in turn. 281 * Each element there groups a set of operations functions. 284 * each element at &struct v4l2_subdev_ops. 306 * Each element there groups a set of operations functions. 309 * each element at &struct v4l2_subdev_ops. 334 * Each element there groups a set of operations functions. 337 * each element at &struct v4l2_subdev_ops. 369 * Each element there groups a set of operations functions. [all …]

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