Searched refs:scalable (Results 1 – 25 of 31) sorted by relevance
12
| /Linux-v5.15/arch/arm/mach-omap2/ |
| D | voltagedomains54xx_data.c | 35 .scalable = true,
46 .scalable = true,
57 .scalable = true,
|
| D | voltagedomains44xx_data.c | 49 .scalable = true,
60 .scalable = true,
71 .scalable = true,
|
| D | voltagedomains3xxx_data.c | 50 .scalable = true,
61 .scalable = true,
|
| D | voltage.h | 64 bool scalable; member
|
| D | voltage.c | 249 if (!voltdm->scalable) in omap_voltage_late_init()
|
| /Linux-v5.15/drivers/iommu/intel/ |
| D | Kconfig | 86 bool "Enable Intel IOMMU scalable mode by default"
89 Selecting this option will enable by default the scalable mode if
90 hardware presents the capability. The scalable mode is defined in
91 VT-d 3.0. The scalable mode capability could be checked by reading
93 is not selected, scalable mode support could also be enabled by
|
| /Linux-v5.15/Documentation/vm/damon/ |
| D | index.rst | 14 - *scalable* (the upper-bound of the overhead is in constant range regardless
|
| /Linux-v5.15/fs/ceph/ |
| D | Kconfig | 14 scalable file system designed to provide high performance,
|
| /Linux-v5.15/Documentation/filesystems/ |
| D | ceph.rst | 34 system extremely efficient and scalable.
37 in-memory cache above the file namespace that is extremely scalable,
46 independent metadata servers, allowing scalable concurrent access.
|
| D | path-lookup.txt | 29 slows things down. It is not scalable because many parallel applications that
|
| /Linux-v5.15/Documentation/devicetree/bindings/mfd/ |
| D | rohm,bd70528-pmic.txt | 9 1S battery charger with scalable charge currents.
|
| /Linux-v5.15/Documentation/vm/ |
| D | numa.rst | 40 lives interesting. Rather, this architecture is a means to provide scalable
41 memory bandwidth. However, to achieve scalable memory bandwidth, system and
|
| /Linux-v5.15/Documentation/arm64/ |
| D | sve.rst | 61 * Whenever SVE scalable register values (Zn, Pn, FFR) are exchanged in memory
141 * Each scalable register (Zn, Pn, FFR) is stored in an endianness-invariant
|
| /Linux-v5.15/Documentation/locking/ |
| D | robust-futexes.rst | 28 method makes futexes very lightweight and scalable.
|
| /Linux-v5.15/Documentation/x86/ |
| D | sva.rst | 251 https://01.org/blogs/2019/assignable-interfaces-intel-scalable-i/o-virtualization-linux
|
| D | resctrl.rst | 1296 …16124958/https://www.intel.com/content/www/us/en/processors/xeon/scalable/xeon-scalable-spec-updat…
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | pmbus-core.rst | 33 To make device specific extensions as scalable as possible, and to avoid having
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | simple.txt | 107 in a naturally scalable data structure.
|
| /Linux-v5.15/Documentation/process/ |
| D | 1.Intro.rst | 59 robust, efficient, and scalable solution for almost any situation.
|
| D | kernel-docs.rst | 258 want a mechanism that is scalable. This means a large number of
|
| /Linux-v5.15/Documentation/doc-guide/ |
| D | sphinx.rst | 373 ``kernel-image`` directives. E.g. to insert a figure with a scalable
|
| /Linux-v5.15/Documentation/virt/kvm/ |
| D | mmu.rst | 443 shadow pages, and is made more scalable with a similar technique.
|
| /Linux-v5.15/Documentation/RCU/ |
| D | RTFP.txt | 1672 ,title = {Portability events: a programming model for scalable system infrastructures}
1735 ,Title="{[PATCH 3/7]} barrier: a scalable synchonisation barrier"
2135 ,Title="Re: [{RFC}, {PATCH}] v4 scalable classic {RCU} implementation"
|
| /Linux-v5.15/net/ipv4/ |
| D | Kconfig | 572 See http://www.deneholme.net/tom/scalable/
|
| /Linux-v5.15/Documentation/RCU/Design/Memory-Ordering/ |
| D | Tree-RCU-Memory-Ordering.rst | 450 | more scalable than a “big bang” all-at-once grace-period start could |
|
12
