Searched refs:scalable (Results  1 – 20 of 20) sorted by relevance
| /linux-4.4.14/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 | 246 		if (!voltdm->scalable)  in omap_voltage_late_init()
  | 
| /linux-4.4.14/kernel/time/ | 
| D | Kconfig | 142 	 are idle.  This Kconfig option enables scalable detection of 144 	 tick to be disabled when all CPUs are idle.  Note that scalable 162 	 therefore uses a fast but non-scalable algorithm for small 163 	 systems and a lazier but scalable algorithm for large systems.
  | 
| /linux-4.4.14/fs/ceph/ | 
| D | Kconfig | 12 	  scalable file system designed to provide high performance,
  | 
| /linux-4.4.14/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 | 205 For making accounting scalable, RSS related information are handled in an
  | 
| /linux-4.4.14/Documentation/vm/ | 
| D | numa | 36 lives interesting.  Rather, this architecture is a means to provide scalable 37 memory bandwidth.  However, to achieve scalable memory bandwidth, system and
  | 
| /linux-4.4.14/Documentation/networking/ | 
| D | tcp.txt | 42 simplest ones are derived from TCP reno (highspeed, scalable) and just
  | 
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ | 
| D | design_notes.txt | 23  * Fast and scalable multithreaded userspace server. Being in userspace it works
  | 
| /linux-4.4.14/Documentation/ | 
| D | robust-futexes.txt | 24 method makes futexes very lightweight and scalable.
  | 
| D | kernel-docs.txt | 298        want a mechanism that is scalable. This means a large number of
  | 
| /linux-4.4.14/Documentation/virtual/kvm/ | 
| D | mmu.txt | 408 To make it be more scalable, kvm maintains a global generation number 429 shadow pages, and is made more scalable with a similar technique.
  | 
| /linux-4.4.14/Documentation/hwmon/ | 
| D | pmbus-core | 32 To make device specific extensions as scalable as possible, and to avoid having
  | 
| /linux-4.4.14/Documentation/development-process/ | 
| D | 1.Intro | 65 robust, efficient, and scalable solution for almost any situation.
  | 
| /linux-4.4.14/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-4.4.14/net/ipv4/ | 
| D | Kconfig | 535 	See http://www.deneholme.net/tom/scalable/
  |