mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-22 18:58:25 +00:00
25307d5331
For stream-based protocols (TCP), adding less data than requested
("short write") is generally not a problem - the rest of data can
be sent in the next packet. So, make net_pkt_append() return length
of written data instead of just bool flag, which makes it closer
to the behavior of POSIX send()/write() calls.
There're many users of older net_pkt_append() in the codebase
however, so net_pkt_append_all() convenience function is added which
keeps returning a boolean flag. All current users were converted to
this function, except for two:
samples/net/http_server/src/ssl_utils.c
samples/net/mbedtls_sslclient/src/tcp.c
Both are related to TLS and implement mbedTLS "tx callback", which
follows POSIX short-write semantics. Both cases also had a code to
workaround previous boolean-only behavior of net_pkt_append() - after
calling it, they measured length of the actual data added (but only
in case of successful return of net_pkt_append(), so that didn't
really help). So, these 2 cases are already improved.
Jira: ZEP-1984
Change-Id: Ibaf7c029b15e91b516d73dab3612eed190ee982b
Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
|
||
|---|---|---|
| .. | ||
| src | ||
| Makefile | ||
| prj_bt.conf | ||
| prj_frdm_k64f_prof.conf | ||
| prj_frdm_k64f.conf | ||
| prj_galileo_prof.conf | ||
| prj_galileo.conf | ||
| prj_qemu_x86.conf | ||
| prj_quark_se_c1000_devboard.conf | ||
| README.rst | ||
| testcase.ini | ||
.. _zperf-sample: zperf: Network Traffic Generator ################################ Description *********** zperf is a network traffic generator for Zephyr that may be used to evaluate network bandwidth. Features ********* - Compatible with iPerf_2.0.5. - Client or server mode allowed without need to modify the source code. - Working with task profiler (PROFILER=1 to be set when building zperf) Supported Boards **************** zperf is board-agnostic. However, to run the zperf sample application, the target platform must provide a network interface supported by Zephyr. This sample application has been tested on the following platforms: - Freedom Board (FRDM K64F) - Quark SE C1000 Development Board - QEMU x86 Requirements ************ - iPerf 2.0.5 installed on the host machine - Supported board Depending on the network technology chosen, extra steps may be required to setup the network environment. Usage ***** If Zephyr acts as a client, iPerf must be executed in server mode. For example, the following command line must be used for UDP testing: .. code-block:: console $ iperf -s -l 1K -u -V -B 2001:db8::2 For TCP testing, the command line would look like this: .. code-block:: console $ iperf -s -l 1K -V -B 2001:db8::2 In the Zephyr console, zperf can be executed as follows: .. code-block:: console zperf> udp.upload 2001:db8::2 5001 10 1K 1M For TCP the zperf command would look like this: .. code-block:: console zperf> tcp.upload 2001:db8::2 5001 10 1K 1M If the IP addresses of Zephyr and the host machine are specified in the config file, zperf can be started as follows: .. code-block:: console zperf> udp.upload2 v6 10 1K 1M or like this if you want to test TCP: .. code-block:: console zperf> tcp.upload2 v6 10 1K 1M If Zephyr is acting as a server, set the download mode as follows for UDP: .. code-block:: console zperf> udp.download 5001 or like this for TCP: .. code-block:: console zperf> tcp.download 5001 and in the host side, iPerf must be executed with the following command line if you are testing UDP: .. code-block:: console $ iperf -l 1K -u -V -c 2001:db8::1 -p 5001 and this if you are testing TCP: .. code-block:: console $ iperf -l 1K -V -c 2001:db8::1 -p 5001 iPerf output can be limited by using the -b option if Zephyr is not able to receive all the packets in orderly manner.