Searched refs:scalable (Results 1 – 21 of 21) sorted by relevance
| /Linux-v4.19/arch/arm/mach-omap2/ |
| D | voltagedomains54xx_data.c | 38 .scalable = true,
49 .scalable = true,
60 .scalable = true,
|
| D | voltagedomains44xx_data.c | 52 .scalable = true,
63 .scalable = true,
74 .scalable = true,
|
| D | voltagedomains3xxx_data.c | 53 .scalable = true,
64 .scalable = true,
|
| D | voltage.h | 67 bool scalable; member
|
| D | voltage.c | 252 if (!voltdm->scalable) in omap_voltage_late_init()
|
| /Linux-v4.19/fs/ceph/ |
| D | Kconfig | 12 scalable file system designed to provide high performance,
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ceph.txt | 32 system extremely efficient and scalable.
35 in-memory cache above the file namespace that is extremely scalable,
44 independent metadata servers, allowing scalable concurrent access.
|
| D | path-lookup.txt | 29 slows things down. It is not scalable because many parallel applications that
|
| D | proc.txt | 212 For making accounting scalable, RSS related information are handled in an
|
| /Linux-v4.19/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-v4.19/Documentation/networking/ |
| D | tcp.txt | 43 simplest ones are derived from TCP reno (highspeed, scalable) and just
|
| /Linux-v4.19/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 23 * Fast and scalable multithreaded userspace server. Being in userspace it works
|
| /Linux-v4.19/Documentation/ |
| D | robust-futexes.txt | 28 method makes futexes very lightweight and scalable.
|
| /Linux-v4.19/Documentation/virtual/kvm/ |
| D | mmu.txt | 412 To make it be more scalable, kvm maintains a global generation number
433 shadow pages, and is made more scalable with a similar technique.
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | pmbus-core | 32 To make device specific extensions as scalable as possible, and to avoid having
|
| /Linux-v4.19/Documentation/doc-guide/ |
| D | sphinx.rst | 342 ``kernel-image`` directives. E.g. to insert a figure with a scalable
|
| /Linux-v4.19/Documentation/process/ |
| D | 1.Intro.rst | 57 robust, efficient, and scalable solution for almost any situation.
|
| D | kernel-docs.rst | 268 want a mechanism that is scalable. This means a large number of
|
| /Linux-v4.19/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-v4.19/net/ipv4/ |
| D | Kconfig | 583 See http://www.deneholme.net/tom/scalable/
|
| /Linux-v4.19/Documentation/kernel-hacking/ |
| D | locking.rst | 234 going so far as to use a softirq, you probably care about scalable
|
