| /linux/Documentation/block/ |
| H A D | bfq-iosched.rst | 14 throughput high). 17 throughput. So, when needed for achieving a lower latency, BFQ builds 18 schedules that may lead to a lower throughput. If your main or only 20 throughput at all times, then do switch off all low-latency heuristics 23 latency and throughput, or on how to maximize throughput. 31 instrumentation, and using the throughput-sync.sh script of the S 50 support is enabled), then the sustainable throughput with BFQ 117 High throughput 120 On hard disks, BFQ achieves up to 30% higher throughput than CFQ, and 121 up to 150% higher throughput than DEADLINE and NOOP, with all the [all …]
|
| H A D | deadline-iosched.rst | 41 throughput. When low latency is the primary concern, smaller is better (where 43 generally improves throughput, at the cost of latency variation.
|
| /linux/net/x25/ |
| H A D | x25_facilities.c | 103 facilities->throughput = p[1]; in x25_parse_facilities() 210 if (facilities->throughput && (facil_mask & X25_MASK_THROUGHPUT)) { in x25_create_facilities() 212 *p++ = facilities->throughput; in x25_create_facilities() 291 if (theirs.throughput) { in x25_negotiate_facilities() 292 int theirs_in = theirs.throughput & 0x0f; in x25_negotiate_facilities() 293 int theirs_out = theirs.throughput & 0xf0; in x25_negotiate_facilities() 294 int ours_in = ours->throughput & 0x0f; in x25_negotiate_facilities() 295 int ours_out = ours->throughput & 0xf0; in x25_negotiate_facilities() 297 net_dbg_ratelimited("X.25: inbound throughput negotiated\n"); in x25_negotiate_facilities() 298 new->throughput = (new->throughput & 0xf0) | theirs_in; in x25_negotiate_facilities() [all …]
|
| /linux/tools/testing/selftests/bpf/benchs/ |
| H A D | run_common.sh | 38 echo -n "throughput: " 39 echo -n "$*" | sed -E "s/.*throughput\s+([0-9]+\.[0-9]+ ± [0-9]+\.[0-9]+\sM\sops\/s).*/\1/" 46 echo -n "hits throughput: " 47 echo -n "$*" | sed -E "s/.* hits throughput\s+([0-9]+\.[0-9]+ ± [0-9]+\.[0-9]+\sM\sops\/s).*/\1/" 50 echo -n ", important_hits throughput: " 51 …echo "$*" | sed -E "s/.*important_hits throughput\s+([0-9]+\.[0-9]+ ± [0-9]+\.[0-9]+\sM\sops\/s).*…
|
| /linux/include/linux/dma/ |
| H A D | k3-psil.h | 16 * enum udma_tp_level - Channel Throughput Levels 18 * @UDMA_TP_HIGH: High Throughput channel 19 * @UDMA_TP_ULTRAHIGH: Ultra High Throughput channel 45 * @channel_tpl: Desired throughput level for the channel
|
| /linux/tools/testing/selftests/amd-pstate/ |
| H A D | tbench.sh | 5 # power consumption and throughput etc.when this script trigger tbench 10 # 4) Get power consumption and throughput by amd_pstate_trace.py. 98 …grep Throughput $OUTFILE_TBENCH-perf-$1-$2.log | awk '{print $2}' > $OUTFILE_TBENCH-throughput-$1-… 99 tp_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_TBENCH-throughput-$1-$2.log) 100 printf "Tbench-$1-#$2 throughput(MB/s): $tp_sum\n" | tee -a $OUTFILE_TBENCH.result 106 # Permance is throughput per second, denoted T/t, where T is throught rendered in t seconds. 150 …bench-$1-#" $OUTFILE_TBENCH.result | grep "throughput(MB/s):" | awk '{print $NF}' > $OUTFILE_TBENC… 151 tp_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_TBENCH-throughput-$1.log) 152 printf "Tbench-$1 total throughput(MB/s): $tp_sum\n" | tee -a $OUTFILE_TBENCH.result 154 …avg_tp=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum/'$LOOP_TIMES'}' $OUTFILE_TBENCH-throughput-… [all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-service-time.rst | 11 The performance value is a relative throughput value among all paths 25 The relative throughput value of the path 42 The relative throughput value of the path 79 and sda has an average throughput 1GB/s and sdb has 4GB/s,
|
| /linux/drivers/md/ |
| H A D | dm-ps-service-time.c | 9 * Throughput oriented path selector. 126 * <relative_throughput>: The relative throughput value of in st_add_path() 224 * Case 1: Both have same throughput value. Choose less loaded path. in st_compare_load() 230 * Case 2a: Both have same load. Choose higher throughput path. in st_compare_load() 231 * Case 2b: One path has no throughput value. Choose the other one. in st_compare_load() 272 * Case 4: Service time is equal. Choose higher throughput path. in st_compare_load() 362 MODULE_DESCRIPTION(DM_NAME " throughput oriented path selector");
|
| /linux/net/core/ |
| H A D | ieee8021q_helpers.c | 156 * [RFC4594], Section 4.8, recommends High-Throughput Data be marked in ietf_dscp_to_ieee8021q_tt() 160 * By default (as described in Section 2.3), High-Throughput Data will in ietf_dscp_to_ieee8021q_tt() 165 * Throughput Data service class within the constrained 4 Access in ietf_dscp_to_ieee8021q_tt() 166 * Category [IEEE.802.11-2016] model. If the High-Throughput Data in ietf_dscp_to_ieee8021q_tt() 177 * is generally RECOMMENDED to map High-Throughput Data to UP 0, thereby in ietf_dscp_to_ieee8021q_tt()
|
| /linux/drivers/gpu/drm/radeon/ |
| H A D | radeon_benchmark.c | 80 unsigned int throughput = (n * (size >> 10)) / time; in radeon_benchmark_log_results() local 82 " %d to %d in %u ms, throughput: %u Mb/s or %u MB/s\n", in radeon_benchmark_log_results() 84 throughput * 8, throughput); in radeon_benchmark_log_results()
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-xdata | 17 The user can read the current PCIe link throughput generated 42 The user can read the current PCIe link throughput generated
|
| /linux/tools/testing/selftests/net/ovpn/ |
| H A D | test-close-socket.sh | 66 ovpn_cmd_ok "run iperf throughput flow" \ 82 ovpn_run_stage "run iperf throughput" ovpn_run_iperf
|
| /linux/drivers/net/wireless/intel/iwlegacy/ |
| H A D | 4965-rs.c | 139 * The following tables contain the expected throughput metrics for all rates 379 * Static function to get the expected throughput from an il_scale_tbl_info 411 /* Get expected throughput */ in il4965_rs_collect_tx_data() 459 /* Calculate average throughput, if we have enough history. */ in il4965_rs_collect_tx_data() 974 * Set frame tx success limits according to legacy vs. high-throughput, 1002 * Find correct throughput table for given mode of modulation 1046 * Find starting rate for new "search" high-throughput mode of modulation. 1048 * above the current measured throughput of "active" mode, to give new mode 1054 * to decrease to match "active" throughput. When moving from MIMO to SISO, 1068 /* expected "search" throughput */ in il4965_rs_get_best_rate() [all …]
|
| /linux/drivers/interconnect/imx/ |
| H A D | imx.h | 24 * High throughput priority level in Regulator mode 29 * Low throughput priority level in Regulator mode
|
| /linux/Documentation/misc-devices/ |
| H A D | dw-xdata-pcie.rst | 40 Get link throughput in MB/s:: 56 Get link throughput in MB/s::
|
| /linux/Documentation/arch/arm/omap/ |
| H A D | omap_pm.rst | 7 throughput constraints to the kernel power management code. 20 latency and throughput, rather than units which are specific to OMAP 46 4. Set the minimum bus throughput needed by a device::
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | e1000.rst | 148 for bulk throughput traffic. 172 the overall throughput, we recommend that you load the driver as 215 extra latency to frame reception and can end up decreasing the throughput 240 along with RxIntDelay, may improve traffic throughput in specific network 297 along with TxIntDelay, may improve traffic throughput in specific 413 Degradation in throughput performance may be observed in some Jumbo frames
|
| H A D | e1000e.rst | 54 increased CPU utilization, though it may help throughput in some circumstances. 84 However, this is generally not suitable for bulk throughput traffic due 123 latency to frame reception and can end up decreasing the throughput of TCP 142 RxIntDelay, may improve traffic throughput in specific network conditions. 164 may improve traffic throughput in specific network conditions.
|
| /linux/tools/perf/pmu-events/arch/x86/silvermont/ |
| H A D | frontend.json | 30 …": "Counts the number of times a decode restriction reduced the decode throughput due to wrong ins… 34 …": "Counts the number of times a decode restriction reduced the decode throughput due to wrong ins…
|
| /linux/drivers/net/wireless/intel/iwlwifi/dvm/ |
| H A D | rs.h | 111 /* uCode API values for OFDM high-throughput (HT) bit rates */ 250 LQ_SISO, /* high-throughput types */ 280 s32 average_tpt; /* success ratio * expected throughput */ 298 const u16 *expected_tpt; /* throughput metrics; expected_tpt_G, etc. */
|
| H A D | rs.c | 150 * The following tables contain the expected throughput metrics for all rates 411 * Static function to get the expected throughput from an iwl_scale_tbl_info 441 /* Get expected throughput */ in rs_collect_tx_data() 489 /* Calculate average throughput, if we have enough history. */ in rs_collect_tx_data() 1035 * Set frame tx success limits according to legacy vs. high-throughput, 1062 * Find correct throughput table for given mode of modulation 1109 * Find starting rate for new "search" high-throughput mode of modulation. 1111 * above the current measured throughput of "active" mode, to give new mode 1117 * to decrease to match "active" throughput. When moving from MIMO to SISO, 1130 /* expected "search" throughput */ in rs_get_best_rate() [all …]
|
| /linux/Documentation/devicetree/bindings/input/touchscreen/ |
| H A D | cypress,cy8ctma340.yaml | 47 the device on the SPI bus. The throughput is maximum 2 Mbps so the 48 typical value is 2000000, if higher rates are used the total throughput
|
| /linux/drivers/perf/amlogic/ |
| H A D | Kconfig | 8 memory throughput and other related events. It
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | dwc_pcie_pmu.rst | 17 - one 64-bit counter for Time Based Analysis (RX/TX data throughput and 28 throughput and time spent in each low-power LTSSM state by the controller.
|
| /linux/drivers/net/wireless/ralink/rt2x00/ |
| H A D | rt2x00dev.c | 1105 { .throughput = 0 * 1024, .blink_time = 334 }, 1106 { .throughput = 1 * 1024, .blink_time = 260 }, 1107 { .throughput = 2 * 1024, .blink_time = 220 }, 1108 { .throughput = 5 * 1024, .blink_time = 190 }, 1109 { .throughput = 10 * 1024, .blink_time = 170 }, 1110 { .throughput = 25 * 1024, .blink_time = 150 }, 1111 { .throughput = 54 * 1024, .blink_time = 130 }, 1112 { .throughput = 120 * 1024, .blink_time = 110 }, 1113 { .throughput = 265 * 1024, .blink_time = 80 }, 1114 { .throughput = 586 * 1024, .blink_time = 50 },
|