| /linux/drivers/net/wireless/ath/ath5k/ |
| H A D | ani.h | 45 * maximizing sensitivity. ANI will not run.
|
| /linux/Documentation/accounting/ |
| H A D | psi.rst | 31 This allows maximizing hardware utilization without sacrificing
|
| /linux/drivers/md/dm-pcache/ |
| H A D | cache.c | 304 * of cache keys across multiple queues, maximizing multiqueue concurrency. in cache_init_req_keys()
|
| /linux/drivers/platform/x86/ |
| H A D | Kconfig | 960 CPU and GPU, maximizing performance in a given TDP. This driver,
|
| /linux/tools/perf/pmu-events/arch/x86/sandybridge/ |
| H A D | snb-metrics.json | 531 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | jkt-metrics.json | 552 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | 4965.h | 365 * assumes that high accuracy is needed for maximizing legal txpower,
|
| /linux/tools/perf/pmu-events/arch/x86/haswell/ |
| H A D | hsw-metrics.json | 904 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/ivybridge/ |
| H A D | ivb-metrics.json | 965 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/broadwellde/ |
| H A D | bdwde-metrics.json | 1061 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/ivytown/ |
| H A D | ivt-metrics.json | 1016 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/broadwell/ |
| H A D | bdw-metrics.json | 1071 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/haswellx/ |
| H A D | hsx-metrics.json | 1157 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/broadwellx/ |
| H A D | bdx-metrics.json | 1324 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/mm/damon/ |
| H A D | core.c | 2751 * user-specified maximum number of regions. This is for maximizing the
|
| /linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
| H A D | rkl-metrics.json | 1701 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/icelake/ |
| H A D | icl-metrics.json | 1680 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/skylake/ |
| H A D | skl-metrics.json | 1591 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
| H A D | tgl-metrics.json | 1701 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/cascadelakex/ |
| H A D | clx-metrics.json | 1971 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/skylakex/ |
| H A D | skx-metrics.json | 1919 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/icelakex/ |
| H A D | icx-metrics.json | 2051 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/graniterapids/ |
| H A D | gnr-metrics.json | 2232 "PublicDescription": "This category represents fraction of slots utilized by useful work i.e. issued uops that eventually get retired. Ideally; all pipeline slots would be attributed to the Retiring category. Retiring of 100% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typically increases the Instructions-per-cycle (see IPC metric). Note that a high Retiring value does not necessary mean there is no room for more performance. For example; Heavy-operations or Microcode Assists are categorized under Retiring. They often indicate suboptimal performance and can often be optimized or avoided. Sample with: UOPS_RETIRED.SLOTS",
|
| /linux/tools/perf/pmu-events/arch/x86/emeraldrapids/ |
| H A D | emr-metrics.json | 2114 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
| /linux/tools/perf/pmu-events/arch/x86/sapphirerapids/ |
| H A D | spr-metrics.json | 2190 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|