| /linux/init/ |
| A D | calibrate.c | 122 unsigned long estimate; in calibrate_delay_direct() local
126 estimate = (good_timer_sum/good_timer_count); in calibrate_delay_direct()
127 maxdiff = estimate >> 3; in calibrate_delay_direct()
131 return estimate; in calibrate_delay_direct()
136 if ((measured_times[max] - estimate) < in calibrate_delay_direct()
137 (estimate - measured_times[min])) { in calibrate_delay_direct()
|
| /linux/arch/powerpc/lib/ |
| A D | div64.S | 32 addc r9,r4,r10 # rounding up (so the estimate cannot
40 2: mullw r10,r11,r4 # to get an estimate of the quotient,
41 mulhwu r9,r11,r4 # multiply the estimate by the divisor,
43 add r8,r8,r11 # and add the estimate to the accumulated
|
| /linux/arch/powerpc/boot/ |
| A D | div64.S | 32 addc r9,r4,r10 # rounding up (so the estimate cannot
40 2: mullw r10,r11,r4 # to get an estimate of the quotient,
41 mulhwu r9,r11,r4 # multiply the estimate by the divisor,
43 add r8,r8,r11 # and add the estimate to the accumulated
|
| /linux/arch/arc/lib/ |
| A D | strcmp.S | 71 bic_s r2,r2,r0 ; get low estimate for r2 and get ...
73 or_s r3,r3,r0 ; ... high estimate r3 so that r2 > r3 will ...
|
| /linux/Documentation/misc-devices/ |
| A D | bh1770glc.rst | 23 but ALS side results are used to estimate reliability of the proximity sensor.
30 8 bit. Driver supports only one channel. Driver uses ALS results to estimate
|
| A D | apds990x.rst | 122 _rough_ estimate about the distance.
|
| /linux/net/netlink/ |
| A D | policy.c | 246 int estimate = netlink_policy_dump_attr_size_estimate(pt); in __netlink_policy_dump_write_attr() local
379 WARN_ON(attr->nla_len > estimate); in __netlink_policy_dump_write_attr()
|
| /linux/drivers/devfreq/event/ |
| A D | Kconfig | 32 (Platform Performance Monitoring Unit) counters to estimate the
|
| /linux/Documentation/driver-api/media/ |
| A D | dtv-common.rst | 10 estimate signal strength and signal to noise measurements in dB.
|
| /linux/Documentation/hwmon/ |
| A D | ibmaem.rst | 32 is a register that displays an estimate of raw energy consumption since the
|
| /linux/net/netfilter/ |
| A D | nft_set_hash.c | 701 .estimate = nft_rhash_estimate,
723 .estimate = nft_hash_estimate,
742 .estimate = nft_hash_fast_estimate,
|
| A D | nft_set_bitmap.c | 303 .estimate = nft_bitmap_estimate,
|
| A D | nft_set_pipapo.c | 2202 .estimate = nft_pipapo_estimate,
2224 .estimate = nft_pipapo_avx2_estimate,
|
| /linux/Documentation/driver-api/thermal/ |
| A D | power_allocator.rst | 63 An estimate of the sustainable dissipatable power (in mW) should be
71 simply an estimate, and may be tuned to affect the aggressiveness of
138 an estimate, which is the reason for closed-loop control such as this.
|
| /linux/drivers/thermal/qcom/ |
| A D | Kconfig | 32 real time die temperature if an ADC is present or an estimate of the
|
| /linux/Documentation/sound/designs/ |
| A D | timestamping.rst | 11 estimate with a delay. In the latter two cases, the low-level driver
15 provides a refined estimate with a delay.
75 audio_tstamp_config fields, thus get an estimate of the timestamp
|
| /linux/Documentation/scheduler/ |
| A D | sched-energy.rst | 77 to capacity and utilization values, EAS is able to estimate how big/busy a
141 find_energy_efficient_cpu() uses compute_energy() to estimate what will be the
186 CPU1 and CPU3. Then it will estimate the energy of the system if P was
345 EAS uses the EM of a platform to estimate the impact of scheduling decisions on
394 in order to estimate their energy consumption. To do so, it is assumed that OPPs
|
| A D | schedutil.txt | 125 the frequency invariant utilization estimate of the CPU. From this we compute
|
| /linux/Documentation/filesystems/ |
| A D | gfs2-glocks.rst | 227 srttvar Variance estimate for srtt
229 srttvarb Variance estimate for srttb
231 sirtvar Variance estimate for sirt
|
| /linux/Documentation/admin-guide/pm/ |
| A D | cpufreq.rst | 40 Typically, they are used along with algorithms to estimate the required CPU
59 Scaling governors implement algorithms to estimate the required CPU capacity.
402 given CPU as the CPU utilization estimate (see the *Per-entity load tracking*
442 In order to estimate the current CPU load, it measures the time elapsed between
445 time to the total CPU time is taken as an estimate of the load.
448 estimated for all of them and the greatest result is taken as the load estimate
535 hardware. That value can be used to estimate how the performance of the
|
| /linux/Documentation/ABI/testing/ |
| A D | sysfs-class-uwb_rc | 146 This gives an estimate on a suitable PHY rate. Refer
|
| A D | sysfs-timecard | 136 with the PHC time. This estimate may be wrong, as it depends
|
| /linux/drivers/gpu/drm/i915/ |
| A D | Kconfig.profile | 87 May be 0 to disable the initial spin. In practice, we estimate
|
| /linux/Documentation/bpf/ |
| A D | prog_flow_dissector.rst | 113 used by ``eth_get_headlen`` to estimate length of all headers for GRO.
|
| /linux/Documentation/admin-guide/mm/ |
| A D | idle_page_tracking.rst | 52 That said, in order to estimate the amount of pages that are not used by a
|