average (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:average (Results 1 – 25 of 653) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...27

/linux/tools/perf/pmu-events/arch/powerpc/power10/
H A D	metrics.json	10 "BriefDescription": "Average cycles per completed instruction", 16 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled for any re… 22 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled because th… 28 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled because Fe… 34 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled because th… 40 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled waiting to… 46 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled waiting to… 52 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled due to an … 58 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled while the … 64 …"BriefDescription": "Average cycles per completed instruction when dispatch was stalled while the … [all …]
/linux/Documentation/devicetree/bindings/input/
H A D	microchip,qt1050.txt	`38 - microchip,average-samples: 41 - microchip,average-scaling: 42 The scaling factor which is used to scale the average-samples. 60 microchip,average-samples = <64>; 61 microchip,average-scaling = <16>; 68 microchip,average-samples = <64>; 69 microchip,average-scaling = <8>; 75 microchip,average-samples = <256>; 76 microchip,average-scaling = <16>;`
/linux/Documentation/translations/zh_CN/accounting/
H A D	delay-accounting.rst	`92 CPU count real total virtual total delay total delay average 94 IO count delay total delay average 96 SWAP count delay total delay average 98 RECLAIM count delay total delay average 100 THRASHING count delay total delay average 102 COMPACT count delay total delay average 104 WPCOPY count delay total delay average`
/linux/Documentation/hwmon/
H A D	lochnagar.rst	30 power1_average Measured average power for DBVDD1 (microWatts) 37 power2_average Measured average power for 1V8 DSP (microWatts) 44 power3_average Measured average power for 1V8 CDC (microWatts) 51 power4_average Measured average power for VDDCORE DSP (microWatts) 58 power5_average Measured average power for AVDD 1V8 (microWatts) 63 power6_average Measured average power for SYSVDD (microWatts) 70 power7_average Measured average power for VDDCORE CDC (microWatts) 77 power8_average Measured average power for MICVDD (microWatts)
H A D	lm25066.rst	`100 in1_average Average measured input voltage. 116 in3_average Average measured output voltage. 122 curr1_average Average measured input current. 128 power1_average Average measured input power.`
H A D	fam15h_power.rst	`62 calculate the average power consumed by a processor during a 91 CPU average power 110 v. Calculate the average power consumption for a compute unit over`
H A D	sysfs-interface.rst	`130 Average voltage 335 Average current use. 367 Average power use. 379 Historical average maximum power use 382 Historical average minimum power use 585 Average sample configuration 589 attributes for controlling number of samples used to compute average. 592 \| samples \| Sets number of average samples for all types of measurements. \| 596 \| in_samples \| Sets number of average samples for specific type of \|`
/linux/tools/perf/bench/
H A D	synthesize.c	39 "Number of iterations used to compute single-threaded average"), 41 "Number of iterations used to compute multi-threaded average"), 97 printf(" Average %ssynthesis took: %.3f usec (+- %.3f usec)\n", in do_run_single_threaded() 102 printf(" Average num. events: %.3f (+- %.3f)\n", in do_run_single_threaded() 105 printf(" Average time per event %.3f usec\n", in do_run_single_threaded() 191 printf(" Average synthesis took: %.3f usec (+- %.3f usec)\n", in do_run_multi_threaded() 196 printf(" Average num. events: %.3f (+- %.3f)\n", in do_run_multi_threaded() 199 printf(" Average time per event %.3f usec\n", in do_run_multi_threaded()
/linux/tools/perf/pmu-events/arch/x86/elkhartlake/
H A D	ehl-metrics.json	`34 "BriefDescription": "Average per-core data fill bandwidth to the L3 cache [GB / sec]", 39 "BriefDescription": "Average CPU Utilization", 44 "BriefDescription": "Measured Average Frequency for unhalted processors [GHz]", 49 "BriefDescription": "Average Frequency Utilization relative nominal frequency",`
/linux/drivers/gpu/drm/amd/pm/swsmu/smu11/
H A D	vangogh_ppt.c	378 *value = (metrics->Average.CurrentSocketPower << 8) / in vangogh_get_smu_metrics_data() 1793 gpu_metrics->average_temperature_gfx = metrics.Average.GfxTemperature; in vangogh_get_gpu_metrics_v2_3() 1794 gpu_metrics->average_temperature_soc = metrics.Average.SocTemperature; in vangogh_get_gpu_metrics_v2_3() 1796 &metrics.Average.CoreTemperature[0], in vangogh_get_gpu_metrics_v2_3() 1798 gpu_metrics->average_temperature_l3[0] = metrics.Average.L3Temperature[0]; in vangogh_get_gpu_metrics_v2_3() 1808 &metrics.Average.CorePower[0], in vangogh_get_gpu_metrics_v2_3() 1811 gpu_metrics->average_gfxclk_frequency = metrics.Average.GfxclkFrequency; in vangogh_get_gpu_metrics_v2_3() 1812 gpu_metrics->average_socclk_frequency = metrics.Average.SocclkFrequency; in vangogh_get_gpu_metrics_v2_3() 1813 gpu_metrics->average_uclk_frequency = metrics.Average.MemclkFrequency; in vangogh_get_gpu_metrics_v2_3() 1814 gpu_metrics->average_fclk_frequency = metrics.Average.MemclkFrequency; in vangogh_get_gpu_metrics_v2_3() [all …]
H A D	cyan_skillfish_ppt.c	162 *value = (metrics->Average.CurrentSocketPower << 8) / in cyan_skillfish_get_smu_metrics_data() 405 gpu_metrics->average_gfxclk_frequency = metrics.Average.GfxclkFrequency; in cyan_skillfish_get_gpu_metrics() 406 gpu_metrics->average_socclk_frequency = metrics.Average.SocclkFrequency; in cyan_skillfish_get_gpu_metrics() 407 gpu_metrics->average_uclk_frequency = metrics.Average.MemclkFrequency; in cyan_skillfish_get_gpu_metrics() 408 gpu_metrics->average_fclk_frequency = metrics.Average.MemclkFrequency; in cyan_skillfish_get_gpu_metrics() 409 gpu_metrics->average_vclk_frequency = metrics.Average.VclkFrequency; in cyan_skillfish_get_gpu_metrics() 410 gpu_metrics->average_dclk_frequency = metrics.Average.DclkFrequency; in cyan_skillfish_get_gpu_metrics() 421 gpu_metrics->average_core_power[i] = metrics.Average.CorePower[i]; in cyan_skillfish_get_gpu_metrics()
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A D	uncore-memory.json	472 …average occupancy (in conjunction with the Read Pending Queue Occupancy count). The RPQ is used t… 483 …average occupancy (in conjunction with the Read Pending Queue Occupancy count). The RPQ is used t… 513 …en be used to calculate both the average occupancy (in conjunction with the number of cycles not e… 522 …en be used to calculate both the average occupancy (in conjunction with the number of cycles not e… 552 …average queue occupancy (in conjunction with the WPQ Occupancy Accumulation count). The WPQ is us… 563 …average queue occupancy (in conjunction with the WPQ Occupancy Accumulation count). The WPQ is us… 573 …ns into the Write Pending Queue. This can then be used to calculate the average queuing latency (… 583 …ns into the Write Pending Queue. This can then be used to calculate the average queuing latency (… 593 …average queue occupancy (in conjunction with the number of cycles not empty) and the average laten… 602 …average queue occupancy (in conjunction with the number of cycles not empty) and the average laten…
/linux/drivers/crypto/intel/qat/qat_common/
H A D	adf_gen4_tl.c	`32 /* Read latency average[ns]. / 39 / Get to put latency average[ns]. / 49 / Page request latency average[ns]. / 53 / Page translation latency average[ns]. / 111 / Get to put latency average[ns]. */`
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-interconnect.json	48 …cle. This can be used with the write transaction count to calculate the average write latency in … 58 …cle. This can be used with the write transaction count to calculate the average write latency in … 68 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 78 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 108 …cle. This can be used with the transaction count event to calculate the average latency in the un… 118 …cle. This can be used with the transaction count event to calculate the average latency in the un… 332 … be used in conjunction with the allocations event in order to calculate average latency of outbou… 864 … conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy.", 873 …nction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This … 883 …nction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This … [all …]
/linux/include/uapi/linux/netfilter/
H A D	xt_hashlimit.h	`34 __u32 avg; /* Average secs between packets * scale / 58 __u32 avg; / Average secs between packets * scale / 71 __u64 avg; / Average secs between packets * scale / 85 __u64 avg; / Average secs between packets * scale */`
/linux/tools/perf/pmu-events/arch/powerpc/power8/
H A D	metrics.json	1326 …"BriefDescription": "Average number of stores that gather in the store buffer before being sent to… 1344 "BriefDescription": "average L1 miss latency using marked events", 1350 "BriefDescription": "Average icache miss latency", 1356 "BriefDescription": "average service time for SYNC", 1362 "BriefDescription": "Cycles LMQ slot0 was active on an average", 1368 …"BriefDescription": "Average number of cycles LRQ stays active for one load. Slot 0 is VALID ONLY… 1374 …"BriefDescription": "Average number of cycles LRQ stays active for one load. Slot 43 is valid ONL… 1380 …"BriefDescription": "Average number of cycles SRQ stays active for one load. Slot 0 is VALID ONLY… 1386 …"BriefDescription": "Average number of cycles SRQ stays active for one load. Slot 39 is valid ONL… 1416 "BriefDescription": "Distant L4 average load latency", [all …]
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-interconnect.json	48 …cle. This can be used with the write transaction count to calculate the average write latency in … 58 …cle. This can be used with the write transaction count to calculate the average write latency in … 68 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 78 …ycle. This can be used with the read transaction count to calculate the average read latency in t… 108 …cle. This can be used with the transaction count event to calculate the average latency in the un… 118 …cle. This can be used with the transaction count event to calculate the average latency in the un… 322 … be used in conjunction with the allocations event in order to calculate average latency of outbou… 523 … conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy.", 692 …njunction with the Flit Buffer Occupancy event in order to calculate the average flit buffer lifet… 701 …njunction with the Flit Buffer Occupancy event in order to calculate the average flit buffer lifet… [all …]
H A D	uncore-memory.json	362 …he high-priority request at the expense of lower bandwidth and increased overall average latency.", 372 …he high-priority request at the expense of lower bandwidth and increased overall average latency.", 411 …average occupancy (in conjunction with the Read Pending Queue Occupancy count). The RPQ is used t… 429 …en be used to calculate both the average occupancy (in conjunction with the number of cycles not e… 447 …average queue occupancy (in conjunction with the WPQ Occupancy Accumulation count). The WPQ is us… 456 …ns into the Write Pending Queue. This can then be used to calculate the average queuing latency (… 465 …average queue occupancy (in conjunction with the number of cycles not empty) and the average laten…
/linux/drivers/gpu/drm/amd/include/
H A D	kgd_pp_interface.h	`266 * moving average of APU power (default ~5000 ms). 267 * @PP_PWR_TYPE_FAST: manages the ~10 ms moving average of APU power, 548 /* Average clocks / 600 / Average clocks / 659 / Average clocks / 721 / Average clocks / 1237 / Average clocks / 1287 / Average clocks / 1337 / Average clocks / 1390 / Average clocks */ [all …]`
/linux/Documentation/ABI/testing/
H A D	debugfs-driver-qat_telemetry	`12 and average for each counter over 2, 3 or 4 samples 24 used to calculate the minimum, maximum and average for each 54 rd_lat_acc_avg average read latency [ns] 57 gp_lat_acc_avg average get to put latency [ns] 60 at_page_req_lat_avg Address Translator(AT), average page 62 at_trans_lat_avg AT, average page translation latency [ns] 131 gp_lat_acc_avg average get to put latency [ns]`
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-interconnect.json	532 "PublicDescription": "Accumulates the number of outstanding outbound requests from the IRP to the switch (towards the devices). This can be used in conjunction with the allocations event in order to calculate average latency of outbound requests.", 824 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy.", 833 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 843 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 853 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 863 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 873 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 883 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 893 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCS flits only.", 903 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupanc [all...]
/linux/kernel/locking/
H A D	qspinlock_stat.h	`30 * Average kick latency (ns) = pv_latency_kick/pv_kick_unlock 32 * Average wake latency (ns) = pv_latency_wake/pv_kick_wake 34 * Average hops/hash = pv_hash_hops/pv_kick_unlock`
/linux/tools/include/uapi/linux/
H A D	pkt_sched.h	235 __u32 qth_min; /* Min average length threshold (bytes) / 236 __u32 qth_max; / Max average length threshold (bytes) / 265 __u32 qth_min; / Min average length threshold (bytes) / 266 __u32 qth_max; / Max average length threshold (bytes) / 328 __u32 qth_min; / Min average length threshold (bytes) / 329 __u32 qth_max; / Max average length threshold (bytes) / 368 __u32 qth_min; / Min average threshold (packets) / 369 __u32 qth_max; / Max average threshold (packets) / 851 __u32 avg_dq_rate; / current average dq_rate in bits/pie_time */
/linux/drivers/cpuidle/governors/
H A D	menu.c	53 * menu uses a running average for this correction factor, but it uses a set of 106 * average of these 8 points as the estimated value. 116 /* Compute the average and variance of past intervals. / in get_typical_interval() 160 deviation is small compared to the average interval (avg > in get_typical_interval() 161 * 6stddev, avg^2 > 36variance). The average is smaller than in get_typical_interval() 163 * overflow a u64. We simply reject this candidate average if in get_typical_interval() 177 * data points at a large enough distance from the average, then in get_typical_interval() 178 * calculate the average and standard deviation again. Once we get in get_typical_interval()
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-interconnect.json	532 "PublicDescription": "Accumulates the number of outstanding outbound requests from the IRP to the switch (towards the devices). This can be used in conjunction with the allocations event in order to calculate average latency of outbound requests.", 823 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy.", 832 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 842 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors DRS flits only.", 852 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 862 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors HOM flits only.", 872 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 882 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCB flits only.", 892 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupancy. This monitors NCS flits only.", 902 "PublicDescription": "Counts the number of cycles that the QPI RxQ was not empty. Generally, when data is transmitted across QPI, it will bypass the RxQ and pass directly to the ring interface. If things back up getting transmitted onto the ring, however, it may need to allocate into this buffer, thus increasing the latency. This event can be used in conjunction with the Flit Buffer Occupancy Accumulator event to calculate the average occupanc [all...]

12 3 4 5 6 7 8 9 10 >>...27