/freebsd/sys/contrib/device-tree/Bindings/dvfs/ |
H A D | performance-domain.yaml | 4 $id: http://devicetree.org/schemas/dvfs/performance-domain.yaml# 7 title: Generic performance domains 13 This binding is intended for performance management of groups of devices or 14 CPUs that run in the same performance domain. Performance domains must not 15 be confused with power domains. A performance domain is defined by a set 16 of devices that always have to run at the same performance level. For a given 17 performance domain, there is a single point of control that affects all the 18 devices in the domain, making it impossible to set the performance level of 21 have a common frequency control, is said to be in the same performance 24 This device tree binding can be used to bind performance domain consumer [all …]
|
/freebsd/sys/contrib/device-tree/Bindings/cpufreq/ |
H A D | cpufreq-mediatek-hw.yaml | 29 "#performance-domain-cells": 31 Number of cells in a performance domain specifier. 33 performance domains. 39 - "#performance-domain-cells" 53 performance-domains = <&performance 0>; 64 performance: performance-controller@11bc00 { 68 #performance-domain-cells = <1>;
|
H A D | apple,cluster-cpufreq.yaml | 15 operating-points-v2 table to define the CPU performance states, with the 34 '#performance-domain-cells': 40 - '#performance-domain-cells' 58 performance-domains = <&cpufreq_e>; 66 performance-domains = <&cpufreq_p>; 106 cpufreq_e: performance-controller@210e20000 { 109 #performance-domain-cells = <0>; 112 cpufreq_p: performance-controller@211e20000 { 115 #performance-domain-cells = <0>;
|
/freebsd/contrib/ofed/infiniband-diags/man/ |
H A D | perfquery.8 | 39 perfquery uses PerfMgt GMPs to obtain the PortCounters (basic performance and 265 perfquery # read local port performance counters 266 perfquery 32 1 # read performance counters from lid 32, port 1 267 perfquery \-x 32 1 # read extended performance counters from lid 32, port 1 269 perfquery \-r 32 1 # read performance counters and reset 270 perfquery \-x \-r 32 1 # read extended performance counters and reset 271 perfquery \-R 0x20 1 # reset performance counters of port 1 only 272 perfquery \-x \-R 0x20 1 # reset extended performance counters of port 1 only 273 perfquery \-R \-a 32 # reset performance counters of all ports 276 perfquery \-a 32 1\-10 # read performance counters from lid 32, port 1\-10, aggregate output [all …]
|
/freebsd/share/doc/papers/sysperf/ |
H A D | 0.t | 30 Measuring and Improving the Performance of Berkeley UNIX* 66 performance of the system. 74 the performance problems encountered and describes 79 performance of the existing facilities, 81 Performance improvements in the kernel include cacheing of path name 84 Performance improvements in the libraries and utilities include replacement of 110 Performance \- 115 system performance, 121 performance. 169 .B "4. Performance Improvements [all …]
|
H A D | 7.t | 33 performance tuning required of a good system. We found that 36 user programs severely limited the overall performance of the 88 ``A User-Process Oriented Performance Study of Ethernet Networking Under 94 ``The Impact of Buffer Management on Networking Software Performance 105 ``Comments on the performance of UNIX on the VAX'', 110 ``UNIX and VMS, Some Performance Comparisons'', 114 ``UNIX System V and 4BSD Performance,'' 119 ``Measuring and Improving the Performance of 4.2BSD,'' 124 ``Performance Improvements and Functional Enhancements in 4.3BSD'' 138 ``UNIX Performance, an Introspection'',
|
H A D | 1.t | 48 no longer provided adequate performance for 4.2BSD. 51 highlighted the performance shortcomings of 4.2BSD. 54 the release of 4.2BSD to measure the performance of the system, 68 available to us for measuring system performance. 70 has the performance improvements
|
/freebsd/lib/libpmc/ |
H A D | pmc.core.3 | 46 performance measurement architecture. 59 performance measurement architecture contain two programmable PMCs of 235 This is an architectural performance event. 240 This is an architectural performance event. 479 This is an architectural performance event. 554 This is an architectural performance event. 558 This is an architectural performance event. 560 This is an architectural performance event. 590 This is an architectural performance event. 711 This is an architectural performance event. [all …]
|
H A D | pmc.3 | 29 .Nd library for accessing hardware performance monitoring counters 38 hardware performance counters to gather performance data about 45 Performance monitoring counters (PMCs) are represented by the library 178 performance measurement architecture. 186 performance measurement architecture. 195 performance measurement architecture. 222 performance measurement architecture version 2 and later. 226 performance measurement architecture version 1 and later. 249 Capabilities of performance monitoring hardware are denoted using 274 The ability to read from performance counters. [all …]
|
/freebsd/sys/contrib/libsodium/test/default/ |
H A D | index.html.tpl | 31 var performance; 32 if (typeof performance !== 'object') { 33 performance = { 40 var Module = { preRun: function() { performance.mark('bench_start') } }; 56 performance.mark('bench_end') 57 performance.measure('bench', 'bench_start', 'bench_end'); 58 var duration = Math.round(performance.getEntriesByName('bench')[0].duration);
|
/freebsd/usr.sbin/powerd/ |
H A D | powerd.8 | 54 Choose the highest performance values. 58 Choose the lowest performance values to get the most power savings. 62 Attempt to strike a balance by degrading performance when the system 64 It offers a good balance between a small performance loss for greatly 71 mode, but tuned for systems where performance and interactivity are 98 mode should begin to degrade performance to save power. 120 mode should consider the CPU running and increase performance.
|
/freebsd/sys/contrib/device-tree/src/arm64/apple/ |
H A D | t6002.dtsi | 78 performance-domains = <&cpufreq_e_die1>; 92 performance-domains = <&cpufreq_e_die1>; 106 performance-domains = <&cpufreq_p0_die1>; 120 performance-domains = <&cpufreq_p0_die1>; 134 performance-domains = <&cpufreq_p0_die1>; 148 performance-domains = <&cpufreq_p0_die1>; 162 performance-domains = <&cpufreq_p1_die1>; 176 performance-domains = <&cpufreq_p1_die1>; 190 performance-domains = <&cpufreq_p1_die1>; 204 performance-domains = <&cpufreq_p1_die1>;
|
H A D | t600x-common.dtsi | 70 performance-domains = <&cpufreq_e>; 84 performance-domains = <&cpufreq_e>; 98 performance-domains = <&cpufreq_p0>; 112 performance-domains = <&cpufreq_p0>; 126 performance-domains = <&cpufreq_p0>; 140 performance-domains = <&cpufreq_p0>; 154 performance-domains = <&cpufreq_p1>; 168 performance-domains = <&cpufreq_p1>; 182 performance-domains = <&cpufreq_p1>; 196 performance-domains = <&cpufreq_p1>;
|
/freebsd/sys/contrib/zstd/ |
H A D | CONTRIBUTING.md | 179 ## Performance section in Contributing to Zstandard 180 Performance is extremely important for zstd and we only merge pull requests whose performance 182 This high bar for performance means that every PR which has the potential to 183 impact performance takes a very long time for us to properly review. That being said, we 184 always welcome contributions to improve performance (or worsen performance for the trade-off of 185 something else). Please keep the following in mind before submitting a performance related PR: 189 particular performance optimization has already been considered in the past. Please take some 194 2. The distinction between noise and actual performance gains can unfortunately be very subtle 201 Performance section which might be helpful for you. 202 3. Optimizing performance for a certain OS, processor vendor, compiler, or network system is a perf… [all …]
|
/freebsd/libexec/rc/rc.d/ |
H A D | power_profile | 6 # Arguments: 0x00 (AC offline, economy) or 0x01 (AC online, performance) 25 # $value: HIGH for the highest performance value, LOW for the best 68 # Find the next state (performance or economy). 72 ${LOGGER} "changed to 'performance'" 73 profile="performance"
|
/freebsd/contrib/llvm-project/clang/lib/Headers/ |
H A D | raointintrin.h | 24 /// result in bad performance for hot data used by single thread only. 46 /// result in bad performance for hot data used by single thread only. 68 /// result in bad performance for hot data used by single thread only. 90 /// result in bad performance for hot data used by single thread only. 113 /// result in bad performance for hot data used by single thread only. 136 /// result in bad performance for hot data used by single thread only. 159 /// result in bad performance for hot data used by single thread only. 182 /// result in bad performance for hot data used by single thread only.
|
/freebsd/share/doc/papers/diskperf/ |
H A D | methodology.ms | 32 Our goal was to evaluate the performance of the target peripherals 36 The approach used by DEC in producing most of the performance data 42 First, the environment in which performance is to be evaluated 99 Small changes in the performance of the disk controller 101 changes in the file system performance,
|
/freebsd/sys/contrib/openzfs/contrib/intel_qat/patch/ |
H A D | 0001-timespec.diff | 11 …sample_code/performance/framework/linux/kernel_space/cpa_sample_code_utils.c b/quickassist/lookasi… 13 --- a/quickassist/lookaside/access_layer/src/sample_code/performance/framework/linux/kernel_space/c… 14 +++ b/quickassist/lookaside/access_layer/src/sample_code/performance/framework/linux/kernel_space/c…
|
/freebsd/share/doc/papers/contents/ |
H A D | contents.ms | 49 Performance Effects of Disk Subsystem Choices 58 .tl '\fBDisk Performance''diskperf\fP' 64 Performance Effects of Disk Subsystem Choices 161 .tl '\fBSystem Performance''sysperf\fP' 167 Measuring and Improving the Performance of Berkeley UNIX.
|
/freebsd/usr.bin/clang/llvm-mca/ |
H A D | llvm-mca.1 | 38 \fBllvm\-mca\fP is a performance analysis tool that uses information 39 available in LLVM (e.g. scheduling models) to statically measure the performance 42 Performance is measured in terms of throughput as well as processor resource 46 The main goal of this tool is not just to predict the performance of the code 47 when run on the target, but also help with diagnosing potential performance 90 If you see that the performance report is not accurate for a processor, 326 is analyzed in isolation, and the final performance report is the union of all 538 to generate a performance report. 545 Here is an example of a performance report generated by the tool for a 626 few performance numbers; the goal of this section is to give a very quick [all …]
|
/freebsd/share/man/man7/ |
H A D | tuning.7 | 30 .Nd performance tuning under FreeBSD 82 Softupdates drastically improves meta-data performance, mainly file 100 There is no loss of performance since the root 151 the performance of a file system by splitting I/O operations across two 164 You should only stripe partitions that require serious I/O performance, 233 improve performance on systems where space for mapping pipe buffers 271 however, when on, it will substantially improve the performance of services 274 Turning on this option will generally not reduce performance even with the 284 cache with dirty buffers when it would not benefit I/O performance. 302 bad clustering performance. [all …]
|
/freebsd/share/man/man4/ |
H A D | hwpstate_intel.4 | 41 driver provides support for hardware-controlled performance states on Intel 48 allowing other compatible drivers to manage performance states, like 77 Energy/Performance Preference. 80 performance (at value 0), energy efficiency (at value 100), or somewhere in
|
/freebsd/usr.sbin/pmccontrol/ |
H A D | pmccontrol.8 | 29 .Nd "control hardware performance monitoring counters" 42 utility controls the operation of the system's hardware performance 89 List available hardware performance counters and their current 92 List available hardware performance counter classes and their
|
/freebsd/share/doc/papers/kerntune/ |
H A D | 3.t | 31 Techniques for Improving Performance 35 applied to the 4.2BSD kernel to improve its performance. 106 in the long term system performance is negligible, 108 but the long term system performance improves significantly. 199 The small performance improvement 270 Statistics on the performance of both caches show 271 the large performance improvement is
|
/freebsd/contrib/sendmail/src/ |
H A D | TUNING | 17 required performance, there are several configuration options that 18 can be changed to accomplish higher performance. However, before 20 performance is not as good as desired. This may also involve hardware 24 the scope of this guide. In almost all other cases performance will 40 to configure sendmail to achieve good performance in all cases, but 55 better disk I/O performance the queue directories can be spread 212 enhance performance, especially compared to normal disk subsystems, e.g., 235 Other options that are interesting to tweak performance are
|