Skip to content

A real-time media transport(DPDK, AF_XDP, RDMA) stack for both raw and compressed video based on COTS hardware.

License

Notifications You must be signed in to change notification settings

OpenVisualCloud/Media-Transport-Library

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Media Transport Library

Ubuntu Windows Test OpenSSF Scorecard CodeQL Dependency Review Coverity Scan Build Status

1. Overview

The Media Transport Library(MTL) is a software based solution designed for high-throughput, low-latency transmission and reception of media data. It features an efficient user-space LibOS UDP stack specifically crafted for media transport, and comes equipped with a built-in SMPTE ST 2110-compliant implementation for Professional Media over Managed IP Networks.

The Media Transport Library solves the strict timing challenges of transporting ST2110 compliant media streams using a software library and through IP networks. Instead of specialized hardware, this library leverages existing commonly available CPU platforms with conventional NICs that incorporate rate limiting to meet the strict timing challenges in the SMPTE ST 2110 standard.

If you find value in our project, please consider giving it a star. Your support helps us grow and reach more people in the open-source community. Every star counts and is greatly appreciated.

1.1 Features

  • Supported data path backend: DPDK PMD, native kernel socket, and AF_XDP with eBPF filter.
  • The User-space LibOS UDP stack features a POSIX socket compatible API.
  • Non-root run.
  • Multi-process handling, allowing for up to 8 NICs per process.
  • Virtualization support by SR-IOV.
  • Built-in PTP protocol with hardware timestamp offload.
  • FFMPEG plugin, OBS(Open Broadcaster Software) plugin, and Intel® Media SDK support.
  • In addition to the native C/C++ API, it also offers bindings for Python and Rust.

1.1.1 ST2110 features

  • Narrow and wide pacing. Please see compliance page for the ST2110 narrow report on our software solution.
  • ST2110-10, ST2110-20, ST2110-21, ST2110-30, ST2110-40, ST2022-7.
  • 1080p, 1080i, 720p, 4k, 8k and others.
  • FPS: 120, 119.88, 100, 60, 59.94, 50, 30, 29.97, 25, 24, 23.98.
  • All video formats listed in ST2110-20, including YUV 4:2:2 10-bit and others, are supported.
  • SIMD color space converter between big-endian and little-endian.
  • ST2110-22 with encoder/decoder plugin interface.
  • ST2022-6 by RTP passthrough interface.
  • ST2110-20 RX timing compliance parser with hardware RX timestamp offload.

1.2 Architecture

The Media Transport Library leverages DPDK (Data Plane Development Kit) EAL (Environment Abstraction Layer including the memory and core management) to implement a highly efficient, real-time, and low-latency media transport solution. This software-based media transport stack enables deployment on edge and cloud environments using COTS hardware.

The library incorporates a virtual data path backend layer, designed to abstract various NIC implementation and provide a unified packet TX/RX interface to the upper network layer. It currently supports three types of NIC devices:

  • DPDK Poll-Mode Drivers (PMDs): These drivers fully bypass the kernel's networking stack, utilizing the 'poll mode' driver. This approach provides direct hardware access, eliminates heavy user/kernel context switches, and avoids IRQ (Interrupt Request) switches. As a result, DPDK PMDs deliver ultra-low latency and high throughput, making them ideal for demanding networking applications.
  • Native Linux Kernel Network Socket Stack: This option supports the full range of kernel ecosystems.
  • AF_XDP with eBPF filter: AF_XDP represents a significant advancement in the Linux networking stack, striking a balance between raw performance and integration with the kernel's networking ecosystem. It's particularly valuable in scenarios where performance is critical, but a full kernel bypass solution like DPDK is not feasible or desired.

The library introduces a tasklet-based asynchronous scheduler that optimizes CPU resource utilization, facilitating integration with various packet processing units and accelerators.

Additionally, the packet pacing module offers support for various pacing algorithms, including RL (Rate Limit), which is partially hardware-offloaded, and TSC (timestamp Counter), which is fully software-based.

MTL also incorporates SIMD (Single Instruction, Multiple Data) for CSC (Color Space Format Conversion) of the big-endian and little-endian, DMA (Direct Memory Access), and plugin interfaces, enabling the creation of a comprehensive video production ecosystem.

For the detail design, please refer to design guide.

/Overall Architecture

1.3 Ethernet supported

MTL offers versatile Ethernet support, thanks to its compatibility with DPDK PMD, kernel socket, and AF_XDP backends.

For DPDK PMD support, you can refer to the DPDK PMD site https://doc.dpdk.org/guides/nics/ for a comprehensive list of supported Ethernet hardware.

In cases where your NIC is not supported by DPDK, MTL provides a fallback option with kernel (Linux) socket transport support.

However, please note that our daily development and validation is primarily conducted on the Intel E810 series and AWS ENA, so we can't guarantee the status for other network interface cards (NICs).

An important point to note is that narrow pacing of TX is only supported for the Intel E810 series together with DPDK PMD due to the rate limit feature. All other type of usage have to use TSC (Timestamp Counter) as the pacing source, which can only ensure a broad wide pacing.

2. Build

Please refer to build guide for instructions on how to build DPDK, the library, and the sample application.

For Windows, please refer to the Win build guide for instructions on how to build.

3. Run ST2110

Please refer to run guide for instructions on how to set up and run the demo pipeline application based on DPDK PMD backend.

For Windows, please refer to Windows run guide.

Additionally, please refer to the VM guide and Windows VM guide for instructions on setting up Linux and Windows guest VMs based on VF passthrough.

For AWS (cloud environment), please refer to AWS run guide for instructions on how to set up and run the demo.

To run this library on the kernel network stack with the built-in kernel NIC driver, please follow the instructions provided in the kernel socket guide.

4. ST2110 Programmers guide

To quickly develop applications based on the Media Transport Library, please refer to ## 6. ST2110 API from design guide.

5. User space LibOS UDP stack guide

MTL has support for a LD preload POSIX-compatible user-space UDP stack that operates directly within the current process context. This enhancement significantly boosts performance by eliminating the cross-core message costs typically associated with client-service architectures used in other user-space UDP stacks. MTL's stack allows the NIC transmission and reception functions to run directly from the sendto/recvfrom API, eliminating the need for cross-core calls and maintaining data affinity (LLC) to the UDP consumer, thereby optimizing performance.

To learn how to use the LibOS UDP stack, please refer to the udp doc.

6. Publication

MHV'23: A Real-time Media Transport Stack Based on Commercial Off-the-shelf Hardware. https://dl.acm.org/doi/10.1145/3588444.3591002

Whitepaper: Open Source Library Enables Real-Time Media over IP Networks. https://www.intel.com/content/www/us/en/content-details/786203/open-source-library-enables-real-time-media-over-ip-networks.html

2022 DPDK Userspace Summit: Real-time and low latency media transport stack based on DPDK. https://www.youtube.com/watch?v=fiiOvHezpBs

7. How to Contribute

We welcome community contributions to the Media Transport Library project. If you have any ideas or issues, please share them with us by using GitHub issues or opening a pull request.

7.1 Fork this repository

Before opening a pull request, please follow these steps:

  1. Fork this repository to your own space.
  2. Create a new branch for your changes.
  3. Make your changes and commit them.
  4. Push your changes to your forked repository.
  5. Open a pull request to the main repository.

If you do not want the main branch automatically synced to the upstream, please go to Actions and disable the Upstream Sync workflow.

7.2 Coding style

We use the super-linter action for style checks.

7.2.1 C/C++

For C/C++ coding, you can run the following command to quickly fix the style:

./format-coding.sh

7.2.2 Python

For Python, black and isort formatter is used.

sudo pip install black
sudo pip install isort
sudo pip install pylint
black python/
isort python/
find python/example/ -name "*.py" -exec pylint {} \;

7.2.3 Others

For other languages, please check with the following example command inside the Docker container:

# super-linter
docker run -it --rm  -v "$PWD":/opt/ --entrypoint /bin/bash github/super-linter

cd /opt/

# echo "shfmt check"
find ./ -type f -name "*.sh" -exec shfmt -w {} +
# echo "shell check"
find ./ -name "*.sh" -exec shellcheck {} \;

# hadolint check
hadolint docker/ubuntu.dockerfile

# actionlint check
actionlint

# markdownlint check
find ./ -name "*.md" -exec markdownlint {} -c .markdown-lint.yml \;
# find ./ -name "*.md" -exec markdownlint {} --fix -c .markdown-lint.yml \;

# textlint
find ./ -name "*.md" -exec textlint {} \;
# find ./ -name "*.md" -exec textlint {} --fix \;