| /linux-4.1.27/drivers/cpufreq/ |
| D | freq_table.c | 111 struct cpufreq_frequency_table optimal = { in cpufreq_frequency_table_target() local
131 optimal.frequency = ~0; in cpufreq_frequency_table_target()
142 optimal.driver_data = i; in cpufreq_frequency_table_target()
148 if (freq >= optimal.frequency) { in cpufreq_frequency_table_target()
149 optimal.frequency = freq; in cpufreq_frequency_table_target()
150 optimal.driver_data = i; in cpufreq_frequency_table_target()
161 if (freq <= optimal.frequency) { in cpufreq_frequency_table_target()
162 optimal.frequency = freq; in cpufreq_frequency_table_target()
163 optimal.driver_data = i; in cpufreq_frequency_table_target()
174 if (diff < optimal.frequency || in cpufreq_frequency_table_target()
[all …]
|
| /linux-4.1.27/Documentation/cpuidle/ |
| D | governor.txt | 23 with different governors. By default, most optimal governor based on your
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/can/ |
| D | mpc5xxx-mscan.txt | 27 If this property is not present, an optimal CAN
|
| /linux-4.1.27/Documentation/networking/ |
| D | s2io.txt | 90 b. Set TCP windows size to optimal value.
103 A MOST value of 2 has been found optimal for Opterons and 3 for Itanium.
|
| D | fib_trie.txt | 82 or shrinking it repeatedly until it fulfills the criteria for optimal
|
| D | e1000e.txt | 122 systems and is a good starting point, but the optimal value will
|
| D | cxgb.txt | 112 includes the optimal settings for your system.
|
| D | e1000.txt | 164 systems and is a good starting point, but the optimal value will
|
| D | scaling.txt | 84 decreases queue length. For low latency networking, the optimal setting
|
| D | ip-sysctl.txt | 212 queue. Applications can still use TCP_CORK for optimal behavior
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | adt7462 | 45 determining an optimal configuration for the automatic PWM control.
|
| D | adt7470 | 47 determining an optimal configuration for the automatic PWM control.
|
| D | adt7475 | 91 an optimal configuration for the automatic PWM control.
|
| D | nct6775 | 70 is lower than optimal. Some fans might not be present because they share pins
|
| D | lm85 | 122 determining an optimal configuration for the automatic PWM control.
|
| /linux-4.1.27/arch/sh/include/mach-kfr2r09/mach/ |
| D | partner-jet-setup.txt | 30 LIST "The PLL and FLL values are updated here for the optimal"
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | sh_mobile_ceu_camera.txt | 64 Do not touch input rectangle - it is already optimal.
|
| D | omap3isp.txt | 125 IOCTLs it is not possible to obtain optimal image quality this way. The AEWB,
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-block | 131 Storage devices may report an optimal I/O size, which is
137 throughput is desired. If no optimal I/O size is
|
| D | sysfs-class-net-mesh | 108 uses to find the optimal paths through the mesh.
|
| D | sysfs-block-bcache | 122 SSD for optimal performance.
|
| /linux-4.1.27/drivers/devfreq/ |
| D | Kconfig | 79 This does not yet operate with optimal voltages.
|
| /linux-4.1.27/Documentation/arm/nwfpe/ |
| D | README | 8 emits as the first target. I have attempted to be as optimal as
|
| /linux-4.1.27/Documentation/x86/i386/ |
| D | IO-APIC.txt | 74 the PCI chipset. Most cards issue INTA, this creates optimal distribution
|
| /linux-4.1.27/Documentation/block/ |
| D | queue-sysfs.txt | 101 This is the optimal IO size reported by the device.
|
| D | biodoc.txt | 984 optimal disk scan and request servicing performance (based on generic
|
| /linux-4.1.27/arch/powerpc/platforms/ps3/ |
| D | Kconfig | 46 system will have optimal runtime performance.
|
| /linux-4.1.27/Documentation/power/ |
| D | opp.txt | 85 in multiple contexts and this synchronization mechanism is optimal for a read
112 used by SoC framework to define a optimal list as per the demands of
|
| D | runtime_pm.txt | 800 the heuristic ends up being non-optimal, it will still prevent devices from
|
| /linux-4.1.27/Documentation/ |
| D | xz.txt | 75 in XZ Utils may not be optimal when creating files for the kernel,
|
| D | static-keys.txt | 242 However, we have not yet implemented optimal no-op sizes (they are currently
|
| D | unaligned-memory-access.txt | 108 resident memory size of structure instances. The optimal layout of the
|
| D | workqueue.txt | 126 stalling should be optimal. As long as there are one or more runnable
|
| D | md.txt | 525 arrays is degraded. So an optimal array will show '0'. A
|
| /linux-4.1.27/Documentation/input/ |
| D | ntrig.txt | 104 I don't know what the optimal values are for these filters. If the defaults
|
| /linux-4.1.27/Documentation/crypto/ |
| D | api-intro.txt | 86 When using the API for ciphers, performance will be optimal if each
|
| /linux-4.1.27/fs/squashfs/ |
| D | Kconfig | 178 the optimal I/O size is 4K (even though the devices can support
|
| /linux-4.1.27/Documentation/fb/ |
| D | uvesafb.txt | 37 or most optimal resolution/refresh rate for your setup will not work
|
| /linux-4.1.27/arch/x86/math-emu/ |
| D | README | 71 "optimal" polynomial approximations. My definition of "optimal" was
|
| /linux-4.1.27/Documentation/timers/ |
| D | hrtimers.txt | 43 - the timer wheel code is most optimal for use cases which can be
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | xfs.txt | 116 If "nolargeio" is specified, the optimal I/O reported in
|
| D | xfs-delayed-logging-design.txt | 503 not particularly flexible and is difficult to select the "optimal value" for
|
| /linux-4.1.27/fs/btrfs/ |
| D | volumes.c | 4838 int optimal, int dev_replace_is_ongoing) in find_live_mirror() argument
4857 if (map->stripes[optimal].dev->bdev && in find_live_mirror()
4858 (tolerance || map->stripes[optimal].dev != srcdev)) in find_live_mirror()
4859 return optimal; in find_live_mirror()
4870 return optimal; in find_live_mirror()
|
| /linux-4.1.27/Documentation/gpio/ |
| D | consumer.txt | 282 Note that for optimal performance GPIOs belonging to the same chip should be
|
| /linux-4.1.27/Documentation/arm64/ |
| D | arm-acpi.txt | 100 not be optimal, with the earliest kernel version that first provides support
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.sym53c8xx | 463 PCI controller behing a PCI-PCI bridge seems sub-optimal).
|
| D | sym53c8xx_2.txt | 594 with this safe configuration but performances will not be optimal.
|
| D | ncr53c8xx.txt | 1253 with this safe configuration but performances will not be optimal.
|
| /linux-4.1.27/Documentation/m68k/ |
| D | kernel-options.txt | 631 can be performed in optimal order. Not all SCSI devices support
|
| /linux-4.1.27/Documentation/x86/ |
| D | boot.txt | 566 alignment preferred for optimal performance; it is possible for the
|
| /linux-4.1.27/init/ |
| D | Kconfig | 879 hotplugging making the compuation optimal for the the worst case
|
| /linux-4.1.27/Documentation/sound/alsa/ |
| D | ALSA-Configuration.txt | 1805 This magic number seems to give pretty optimal throughput
|