Searched full:generations (Results 1 – 25 of 203) sorted by relevance
123456789
| /kernel/linux/linux-6.6/Documentation/mm/ |
| D | multigen_lru.rst | 24 group of pages with similar access recency. Generations establish a
39 recency, are similar. With generations as a common frame of reference,
44 Again, with generations as a common frame of reference, this becomes
82 Evictable pages are divided into multiple generations for each
94 at most ``MAX_NR_GENS`` generations. The gen counter stores a value
100 generations, tiers do not have dedicated ``lrugen->folios[]``. In
101 contrast to moving across generations, which requires the LRU lock,
114 The aging produces young generations. Given an ``lruvec``, it
130 The eviction consumes old generations. Given an ``lruvec``, it
218 The PID controller uses generations rather than the wall clock as the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/gpu/ |
| D | tegra.rst | 15 The drm/tegra driver supports NVIDIA Tegra SoC generations since Tegra20. It
65 Tegra SoC generations, up until Tegra186 which introduces several changes that
100 The type and number of supported outputs varies between Tegra SoC generations.
101 All generations support at least HDMI. While earlier generations supported the
102 very simple RGB interfaces (one per display controller), recent generations no
|
| /kernel/linux/linux-6.6/Documentation/gpu/ |
| D | tegra.rst | 15 The drm/tegra driver supports NVIDIA Tegra SoC generations since Tegra20. It
65 Tegra SoC generations, up until Tegra186 which introduces several changes that
100 The type and number of supported outputs varies between Tegra SoC generations.
101 All generations support at least HDMI. While earlier generations supported the
102 very simple RGB interfaces (one per display controller), recent generations no
|
| /kernel/linux/linux-6.6/Documentation/driver-api/surface_aggregator/ |
| D | overview.rst | 11 with the following generations.
39 on newer generations, less devices are declared in ACPI, making them a bit
51 5th and later generations, communication takes place via a USART serial
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/pinctrl/ |
| D | nvidia,tegra234-pinmux-common.yaml | 27 # for all chip generations. In this case, however, we want the per-SoC
29 # allowed, since not all pinmux generations support the same sets of
|
| /kernel/linux/linux-6.6/fs/btrfs/ |
| D | lru_cache.h | 22 * Entries with the same key and different generations are stored in a
24 * of different generations.
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/ |
| D | multigen_lru.rst | 92 evicted generations in this file.
134 certain time interval to create new generations, and it ranks the
147 generations less than or equal to ``min_gen_nr``.
|
| /kernel/linux/linux-5.10/drivers/platform/x86/ |
| D | apple-gmux.c | 336 * MacBook Pro generations, MBP5 2008/09 and MBP6 2010. This is done by an
340 * The following MacBook Pro generations replaced the external DP port with a
350 * interrupt on hotplug. On generations which cannot switch external ports,
352 * The ability to switch AUX on these generations could be used to improve
357 * Our switching policy for the external port is that on those generations
364 * On all newer generations, the external port can only be driven by the
528 * MCP79, on all following generations it's GPIO pin 6 of the Intel PCH.
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | adm1021.rst | 149 Previous generations of the Xeon processor (based on Pentium II/III)
150 didn't have these sensors. Next generations of Xeon processors (533 MHz
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | adm1021.rst | 149 Previous generations of the Xeon processor (based on Pentium II/III)
150 didn't have these sensors. Next generations of Xeon processors (533 MHz
|
| /kernel/linux/linux-6.6/drivers/platform/x86/ |
| D | apple-gmux.c | 385 * MacBook Pro generations, MBP5 2008/09 and MBP6 2010. This is done by an
389 * The following MacBook Pro generations replaced the external DP port with a
399 * interrupt on hotplug. On generations which cannot switch external ports,
401 * The ability to switch AUX on these generations could be used to improve
406 * Our switching policy for the external port is that on those generations
413 * On all newer generations, the external port can only be driven by the
614 * MBP5 2008/09 it's GPIO pin 22 of the Nvidia MCP79, on following generations
|
| /kernel/linux/linux-6.6/drivers/net/dsa/mv88e6xxx/ |
| D | devlink.c | 304 /* The ATU entry varies between mv88e6xxx chipset generations. Define
306 * mv88e6xxx generations
429 * The VTU entry format varies between chipset generations, the
513 * The STU entry format varies between chipset generations. Peridot
|
| /kernel/linux/linux-5.10/arch/x86/lib/ |
| D | retpoline.S | 87 * target buffer of Zen3/4 generations, leading to any potential
143 * must all start at a cacheline boundary for Zen1/2 generations. That
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/ |
| D | nvidia,tegra20-ictlr.txt | 14 Tegra generations later than Tegra30 the compatible value should
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/interrupt-controller/ |
| D | nvidia,tegra20-ictlr.txt | 14 Tegra generations later than Tegra30 the compatible value should
|
| /kernel/linux/linux-6.6/arch/loongarch/include/asm/ |
| D | xor.h | 53 * appropriate to revisit this after one or two more uarch generations.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/fuse/ |
| D | nvidia,tegra20-fuse.txt | 14 available in later generations such as fab code, lot code, wafer id,..
|
| /kernel/linux/linux-6.6/drivers/platform/surface/ |
| D | Kconfig | 117 generations).
139 The KIP subsystem is used on newer Surface generations to handle
|
| /kernel/linux/linux-6.6/arch/x86/lib/ |
| D | retpoline.S | 145 * target buffer of Zen3/4 generations, leading to any potential
202 * must all start at a cacheline boundary for Zen1/2 generations. That
|
| /kernel/linux/linux-6.6/Documentation/gpu/amdgpu/display/ |
| D | display-manager.rst | 54 DC Color Capabilities between DCN generations
75 generations. What's possible to do before and after blending depends on
|
| /kernel/linux/linux-5.10/arch/openrisc/include/asm/ |
| D | elf.h | 56 For the moment, we have only optimizations for the Intel generations,
|
| /kernel/linux/linux-6.6/arch/openrisc/include/asm/ |
| D | elf.h | 56 For the moment, we have only optimizations for the Intel generations,
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | mediatek,smi-common.txt | 5 Mediatek SMI have two generations of HW architecture, here is the list
|
| /kernel/linux/linux-6.6/drivers/platform/surface/aggregator/ |
| D | Kconfig | 36 only 5th and later generations are currently supported. Specifically,
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | mmzone.h | 328 * Evictable pages are divided into multiple generations. The youngest and the
339 * This process, AKA second chance, requires a minimum of two generations,
341 * LRU, e.g., /proc/vmstat, these two generations are considered active; the
342 * rest of generations, if they exist, are considered inactive. See
366 * In contrast to moving across generations which requires the LRU lock, moving
405 /* whether to keep historical stats from evicted generations */
506 * For each node, memcgs are divided into two generations: the old and the
543 * 2. There are only two valid generations: old (seq) and young (seq+1).
645 /* evictable pages divided into generations */
|
123456789