Home
last modified time | relevance | path

Searched full:throughput (Results 1 – 25 of 72) sorted by relevance

123

/Zephyr-latest/tests/bsim/bluetooth/ll/throughput/src/
Dmain.c21 * a stable 2M throughput value to be verified. If Central and Peripheral take
23 * the throughput calculated over one second duration will be low due to the
29 /* Write Throughput calculation:
42 * Throughput = 400 * 244 * 8 = 780800 bps
/Zephyr-latest/drivers/wifi/esp32/
DKconfig.esp3291 …A higher number may allow higher throughput but increases memory use. If ESP32_WIFI_AMPDU_RX_ENABL…
93 achieve better throughput and compatibility with both stations and APs.
246 higher throughput but more memory. Most of time we should NOT change the
248 UDP TX throughput with iperf etc. For iperf test in shieldbox,
266 higher throughput and better compatibility but more memory. Most of time
268 e.g. test the maximum UDP RX throughput with iperf etc. For iperf test in
271 should be 16 to achieve better throughput and compatibility with both
292 but Wi-Fi throughput will be reduced.
/Zephyr-latest/include/zephyr/drivers/wifi/nrf_wifi/off_raw_tx/
Doff_raw_tx_api.h108 * @brief- Throughput mode
109 * Throughput mode to be used for transmitting the packet.
114 /** High Throughput mode (11n) */
116 /** Very high throughput mode (11ac) */
124 /** Highest throughput mode currently defined */
152 /** Throughput mode for packet transmittion. Refer &enum nrf_wifi_off_raw_tx_tput_mode */
/Zephyr-latest/samples/bluetooth/iso_broadcast_benchmark/
Dprj.conf4 CONFIG_BT_DEVICE_NAME="ISO Broadcast Throughput"
DREADME.rst62 [00:00:00.447,845] <inf> iso_broadcast_main: Starting Bluetooth Throughput
96 [00:00:00.447,845] <inf> iso_broadcast_main: Starting Bluetooth Throughput
/Zephyr-latest/samples/bluetooth/iso_connected_benchmark/
Dprj.conf4 CONFIG_BT_DEVICE_NAME="ISO Connected Throughput"
DREADME.rst63 [00:00:00.392,333] <inf> iso_connected: Starting Bluetooth Throughput example
95 [00:00:00.459,869] <inf> iso_connected: Starting Bluetooth Throughput example
/Zephyr-latest/tests/bsim/bluetooth/host/misc/hfc_multilink/tester/
Dprj.conf12 # Work around bug in throughput calculation
/Zephyr-latest/tests/bsim/bluetooth/host/l2cap/split/tester/
Dprj.conf12 # Work around bug in throughput calculation
/Zephyr-latest/soc/espressif/esp32/
DKconfig77 Larger number of buffers could increase throughput somehow.
85 Larger number of buffers could increase throughput somehow.
/Zephyr-latest/subsys/fs/fcb/
DKconfig24 favor of increased write throughput.
/Zephyr-latest/tests/bsim/bluetooth/
Dtests.nrf54l15bsim_nrf54l15_cpuapp.txt3 tests/bsim/bluetooth/ll/throughput/
Dtests.nrf5340bsim_nrf5340_cpuapp.txt4 tests/bsim/bluetooth/ll/throughput/
Dcompile.nrf54l15bsim_nrf54l15_cpuapp.sh16 app=tests/bsim/bluetooth/ll/throughput compile
Dcompile.nrf5340bsim_nrf5340_cpuapp.sh18 app=tests/bsim/bluetooth/ll/throughput sysbuild=1 compile
/Zephyr-latest/drivers/ethernet/
DKconfig.cyclonev19 improve throughput, but that requires more transient memory.
DKconfig.dwmac47 improve throughput, but that requires more transient memory.
/Zephyr-latest/tests/bsim/bluetooth/ll/throughput/tests_scripts/
Dgatt_write.sh7 simulation_id="ll-throughput"
/Zephyr-latest/samples/subsys/logging/ble_backend/
DREADME.rst16 to change this configuration to increase the logger throughput over Bluetooth.
/Zephyr-latest/drivers/modem/
DKconfig112 Decreasing this value can help increase data throughput when high
115 high can reduce data throughput.
/Zephyr-latest/samples/bluetooth/iso_broadcast_benchmark/src/
Dmain.c58 LOG_INF("Starting Bluetooth Throughput example"); in main()
/Zephyr-latest/drivers/wifi/nrf_wifi/
DCMakeLists.txt67 # throughput issues.
/Zephyr-latest/tests/bsim/bluetooth/ll/
Dcompile.sh43 app=tests/bsim/bluetooth/ll/throughput compile
/Zephyr-latest/dts/bindings/qspi/
Dst,stm32-qspi.yaml69 effectively doubling the throughput as well as the capacity.
/Zephyr-latest/drivers/flash/
Dflash_shell.c360 double throughput = size; in speed_output() local
364 throughput /= (time_per_loop / 1000.0); in speed_output()
367 while (throughput >= (double)speed_divisor && speed_index < ARRAY_SIZE(speed_types)) { in speed_output()
368 throughput /= (double)speed_divisor; in speed_output()
373 total_time, time_per_loop, throughput, speed_types[speed_index]); in speed_output()

123