Home
last modified time | relevance | path

Searched full:maximizing (Results 1 – 25 of 31) sorted by relevance

12

/openbmc/openbmc/meta-openembedded/meta-gnome/recipes-gnome/devilspie/files/
H A Ddefault.lua5 -- * maximizing and undecorating all appplication's windows in apps_list
/openbmc/linux/Documentation/driver-api/
H A Dspi.rst26 SPI shift register (maximizing throughput). Such drivers bridge between
/openbmc/linux/drivers/net/wireless/ath/ath5k/
H A Dani.h45 * maximizing sensitivity. ANI will not run.
/openbmc/linux/Documentation/accounting/
H A Dpsi.rst31 This allows maximizing hardware utilization without sacrificing
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/
H A Dti,k3-r5f-rproc.yaml182 if omitted. Recommended to enable it for maximizing TCMs.
/openbmc/linux/Documentation/core-api/
H A Dworkqueue.rst569 better than "cache (strict)" and maximizing workqueue utilization is
/openbmc/linux/tools/perf/pmu-events/arch/x86/sandybridge/
H A Dsnb-metrics.json501 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/drivers/platform/x86/
H A DKconfig1025 CPU and GPU, maximizing performance in a given TDP. This driver,
/openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A Djkt-metrics.json502 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dadvanced.rst771 Here are repository organization strategies maximizing source reuse,
/openbmc/linux/drivers/net/wireless/intel/iwlegacy/
H A D4965.h365 * assumes that high accuracy is needed for maximizing legal txpower,
/openbmc/linux/mm/damon/
H A Dcore.c1256 * user-specified maximum number of regions. This is for maximizing the
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswell/
H A Dhsw-metrics.json889 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/drivers/net/ethernet/3com/
H A D3c515.c381 Unfortunately maximizing the shared code between the integrated and
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivybridge/
H A Divb-metrics.json932 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A Divt-metrics.json963 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwell/
H A Dbdw-metrics.json1063 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A Dbdwde-metrics.json1040 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A Dhsx-metrics.json1122 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/skylake/
H A Dskl-metrics.json1357 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A Dbdx-metrics.json1296 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/icelake/
H A Dicl-metrics.json1390 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/tools/perf/pmu-events/arch/x86/tigerlake/
H A Dtgl-metrics.json1404 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…
/openbmc/linux/Documentation/RCU/
H A DRTFP.txt557 ,Title="Tornado: Maximizing Locality and Concurrency in a Shared Memory
/openbmc/linux/tools/perf/pmu-events/arch/x86/rocketlake/
H A Drkl-metrics.json1416 …0% would indicate the maximum Pipeline_Width throughput was achieved. Maximizing Retiring typical…

12