Lines Matching full:performance

38 	performance [inst/s]
48 while still getting 'good' performance. It is essentially an alternative
49 optimization objective to the current performance-only objective for the
51 performance.
78 task/CPU is, and to take this into consideration when evaluating performance vs
84 per 'performance domain' in the system (see Documentation/power/energy-model.rst
85 for futher details about performance domains).
89 scheduler maintains a singly linked list of all performance domains intersecting
95 necessarily match those of performance domains, the lists of different root
99     Let us consider a platform with 12 CPUs, split in 3 performance domains
136 each performance domain since it is the one which will allow us to keep the
145 which computes the expected energy consumption of each performance domain for
151     Let us consider a (fake) platform with 2 independent performance domains
160     Each performance domain has three Operating Performance Points (OPPs).
185     maximum spare capacity in the two performance domains. In this example,
261 result in raising the OPP of the entire performance domain, and that will
285 throughput. In order to avoid hurting performance with EAS, CPUs are flagged as
363 too complex (too many CPUs, too many performance domains, too many performance
369 with: Nd the number of performance domains; Nc the number of CPUs; and Ns the
411 In order to make accurate prediction across CPUs and for all performance
425 CPUs, which can actually be counter-productive for both performance and energy.