Session ID: SFO17-209
Session Name: Realtime Performance of Networking Stack - SFO17-209
Speaker: Ivan Khoronzhuk - Pekka Varis
Track: LNG
★ Session Summary ★
Realtime applications have traditionally used interrupt latency as the performance metric. Many industrial , automotive and audio/video applications require deterministic performance from networking. Fixed latency can often be dealt with but jitter is especially problematic. New Ethernet features such as time sensitive networking (TSN) ensure single digit microsecond level jitter in a LAN. The networking driver and stack jitter measurements are presented and analyzed.
---------------------------------------------------
★ Resources ★
Event Page: http://connect.linaro.org/resource/sfo17/sfo17-209/
Presentation:
Video:
---------------------------------------------------
★ Event Details ★
Linaro Connect San Francisco 2017 (SFO17)
25-29 September 2017
Hyatt Regency San Francisco Airport
---------------------------------------------------
Keyword:
http://www.linaro.org
http://connect.linaro.org
---------------------------------------------------
Follow us on Social Media
https://www.facebook.com/LinaroOrg
https://twitter.com/linaroorg
https://www.youtube.com/user/linaroorg?sub_confirmation=1
https://www.linkedin.com/company/1026961
IAC 2024 - IA Fast Track to Search Focused AI Solutions
Realtime Performance of Networking Stack - SFO17-209
1. SFO17-209 - Realtime Performance
of Networking Stack
Pekka Varis (Texas Instruments)
Ivan Khoronzhuk (TI / GlobalLogic), most of the work
Ilias Apalodimas (Linaro), measurements on Armada
2. ENGINEERS AND DEVICES
WORKING TOGETHER
Why is Deterministic Networking Needed?
● Isochronous Control Loop
● For correctness application A needs to talk application B in a bounded amount
of time over Ethernet
4. ENGINEERS AND DEVICES
WORKING TOGETHERhttps://projects.linaro.org/browse/LNG-387
Measure Networking Driver and Stack Latency
and Jitter
Use PTP packets because of
HW support to include
timestamps.
5. ENGINEERS AND DEVICES
WORKING TOGETHER
Tested Hardware
AM572x Sitara SoC board:
- TI -rt kernel 4.9, rt SDK
- applied one fix to allow sw timestamping
- Driver: cpsw
- CPU freq used: 1GHz (supports 1.5GHz)
- CPU num: 2
- CPU type: ARM Cortex-A15
- 1Gbps Ethernet
Marvell Armada 8040
- Linux-4.4.52-armada-17.08
- Driver: mvpp2x
- CPU freq used: 1GHz (supports 2GHz)
- CPU num: 4
- CPU type: ARM Cortex-A72
- 10Gbps Ethernet
8. ENGINEERS AND DEVICES
WORKING TOGETHER
Latency Plot per Packet RX (Armada 8040)
:~# ./plget -i eth0 -u 380 -m rx-lat -n 100000 -t >
macchiato_rx_udp_load_prio_noaff.txt &
packet num: 100000; packet size: 512; pps: 100;
latency, us driver stack complete
maximum - 897.68 -
minimum - 9.80 -
mean +- RMS - 110.33 ±19.95 -
For reference, goal is to clarify jitter is present on all HW. Issues with core affinity and
support for HW timestamps per packet limited to testing just stack.
9. ENGINEERS AND DEVICES
WORKING TOGETHER
Analysis
IEEE 802 TSN support will require Linux support for:
● Timing over packet, seems to be well covered in open source
● Configuration of switches and shapers, AVNU seems to address
Applications to leverage single digit jitter is not addressed. Tens of microseconds
of jitter in both transmit and receive.
measurements with different tools ftrace, systemtap, to verify that the results are
100% accurate
TSN Patches for Intel NIC and Cisco/Henrik