| /linux-6.3-rc2/arch/arm/mach-omap2/ |
| A D | voltagedomains54xx_data.c | 35 .scalable = true,
46 .scalable = true,
57 .scalable = true,
|
| A D | voltagedomains44xx_data.c | 49 .scalable = true,
60 .scalable = true,
71 .scalable = true,
|
| A D | voltagedomains3xxx_data.c | 50 .scalable = true,
61 .scalable = true,
|
| A D | voltage.h | 64 bool scalable; member
|
| A D | voltage.c | 249 if (!voltdm->scalable) in omap_voltage_late_init()
|
| /linux-6.3-rc2/drivers/iommu/intel/ |
| A D | Kconfig | 88 bool "Enable Intel IOMMU scalable mode by default"
91 Selecting this option will enable by default the scalable mode if
92 hardware presents the capability. The scalable mode is defined in
93 VT-d 3.0. The scalable mode capability could be checked by reading
95 is not selected, scalable mode support could also be enabled by
|
| /linux-6.3-rc2/Documentation/devicetree/bindings/clock/ |
| A D | mstar,msc313-cpupll.yaml | 13 The MStar/SigmaStar MSC313 and later ARMv7 chips have a scalable
|
| /linux-6.3-rc2/Documentation/mm/damon/ |
| A D | index.rst | 15 - *scalable* (the upper-bound of the overhead is in constant range regardless
|
| /linux-6.3-rc2/fs/ceph/ |
| A D | Kconfig | 14 scalable file system designed to provide high performance,
|
| /linux-6.3-rc2/Documentation/filesystems/ |
| A 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.
|
| A D | path-lookup.txt | 29 slows things down. It is not scalable because many parallel applications that
|
| /linux-6.3-rc2/Documentation/mm/ |
| A D | numa.rst | 38 lives interesting. Rather, this architecture is a means to provide scalable
39 memory bandwidth. However, to achieve scalable memory bandwidth, system and
|
| /linux-6.3-rc2/Documentation/arm64/ |
| A D | sve.rst | 77 * Whenever SVE scalable register values (Zn, Pn, FFR) are exchanged in memory
162 * Each scalable register (Zn, Pn, FFR) is stored in an endianness-invariant
|
| /linux-6.3-rc2/Documentation/locking/ |
| A D | robust-futexes.rst | 28 method makes futexes very lightweight and scalable.
|
| /linux-6.3-rc2/tools/memory-model/Documentation/ |
| A D | simple.txt | 107 in a naturally scalable data structure.
|
| /linux-6.3-rc2/Documentation/hwmon/ |
| A D | pmbus-core.rst | 33 To make device specific extensions as scalable as possible, and to avoid having
|
| /linux-6.3-rc2/Documentation/x86/ |
| A D | sva.rst | 280 https://01.org/blogs/2019/assignable-interfaces-intel-scalable-i/o-virtualization-linux
|
| A D | resctrl.rst | 1439 …16124958/https://www.intel.com/content/www/us/en/processors/xeon/scalable/xeon-scalable-spec-updat…
|
| /linux-6.3-rc2/Documentation/process/ |
| A D | 1.Intro.rst | 59 robust, efficient, and scalable solution for almost any situation.
|
| /linux-6.3-rc2/Documentation/doc-guide/ |
| A D | sphinx.rst | 435 ``kernel-image`` directives. E.g. to insert a figure with a scalable
|
| /linux-6.3-rc2/Documentation/virt/kvm/x86/ |
| A D | mmu.rst | 447 shadow pages, and is made more scalable with a similar technique.
|
| /linux-6.3-rc2/Documentation/RCU/ |
| A 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-6.3-rc2/net/ipv4/ |
| A D | Kconfig | 581 See http://www.deneholme.net/tom/scalable/
|
| /linux-6.3-rc2/Documentation/RCU/Design/Memory-Ordering/ |
| A D | Tree-RCU-Memory-Ordering.rst | 445 | more scalable than a “big bang” all-at-once grace-period start could |
|
| /linux-6.3-rc2/Documentation/RCU/Design/Requirements/ |
| A D | Requirements.rst | 21 primitives can be exceedingly fast and scalable. In addition, updaters
1020 must therefore use scalable locking designs.
2307 which means that RCU must be extremely scalable. Algorithms that involve
|