/linux/Documentation/driver-api/ |
H A D | spi.rst | 26 SPI shift register (maximizing throughput). Such drivers bridge between
|
/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/Documentation/devicetree/bindings/remoteproc/ |
H A D | ti,k3-r5f-rproc.yaml | 182 if omitted. Recommended to enable it for maximizing TCMs.
|
/linux/tools/perf/pmu-events/arch/x86/sandybridge/ |
H A D | snb-metrics.json | 512 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
/linux/Documentation/core-api/ |
H A D | workqueue.rst | 589 better than "cache (strict)" and maximizing workqueue utilization is
|
/linux/tools/perf/pmu-events/arch/x86/jaketown/ |
H A D | jkt-metrics.json | 532 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
/linux/drivers/platform/x86/ |
H A D | Kconfig | 1097 CPU and GPU, maximizing performance in a given TDP. This driver,
|
/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 | 882 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
/linux/drivers/net/ethernet/3com/ |
H A D | 3c515.c | 378 Unfortunately maximizing the shared code between the integrated and
|
/linux/tools/perf/pmu-events/arch/x86/ivybridge/ |
H A D | ivb-metrics.json | 943 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
/linux/mm/damon/ |
H A D | core.c | 1813 * user-specified maximum number of regions. This is for maximizing the
|
/linux/tools/perf/pmu-events/arch/x86/broadwell/ |
H A D | bdw-metrics.json | 1049 …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 | 1039 …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 | 991 …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 | 1132 …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 | 1299 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
/linux/Documentation/RCU/ |
H A D | RTFP.txt | 557 ,Title="Tornado: Maximizing Locality and Concurrency in a Shared Memory
|
/linux/tools/perf/pmu-events/arch/x86/tigerlake/ |
H A D | tgl-metrics.json | 1556 …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 | 1474 …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 | 1642 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|
/linux/tools/perf/pmu-events/arch/x86/rocketlake/ |
H A D | rkl-metrics.json | 1662 …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 | 1802 …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 | 1851 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
|