You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docs: order documentation in MTL (and also paralely in BCS and MCM repos
(as MTL will be used as sub-module there)).
Style of chapters change,
comas, points, colons, numbering of sections,
style of source code blocks consistent,
source code with commend lines to be paste'able for user,
isolate some parts of the text to be reused also in the documents of
others repositories.
Sphinx added generating the documentaries.
Added ST41 to the architecture diagram.
Added X540-AT2/X550T NICs to the architecture diagram.
Copy file name to clipboardExpand all lines: README.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ The Media Transport Library solves the strict timing challenges of transporting
17
17
18
18
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.
19
19
20
-
### 1.1 Features
20
+
### 1.1. Features
21
21
22
22
* Supported data path backend: DPDK PMD, native kernel socket, and AF_XDP with eBPF filter.
23
23
* The User-space LibOS UDP stack features a POSIX socket compatible API.
@@ -28,7 +28,7 @@ If you find value in our project, please consider giving it a star. Your support
28
28
* FFMPEG plugin, OBS(Open Broadcaster Software) plugin, and Intel® Media SDK support.
29
29
* In addition to the native C/C++ API, it also offers bindings for [Python](python/README.md) and [Rust](rust/README.md).
30
30
31
-
#### 1.1.1 ST2110 features
31
+
#### 1.1.1. ST2110 features
32
32
33
33
* Narrow and wide pacing. Please see [compliance](doc/compliance.md) page for the ST2110 narrow report on our software solution.
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.
46
46
@@ -56,13 +56,13 @@ Additionally, the packet pacing module offers support for various pacing algorit
56
56
57
57
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.
58
58
59
-
For the detail design, please refer to [design guide](doc/design.md).
59
+
For the detail design, please refer to [Design Guide](doc/design.md).
MTL offers versatile Ethernet support, thanks to its compatibility with DPDK PMD, kernel socket, and AF_XDP backends.
68
68
@@ -76,25 +76,25 @@ An important point to note is that narrow pacing of TX is only supported for the
76
76
77
77
## 2. Build
78
78
79
-
Please refer to [build guide](doc/build.md) for instructions on how to build DPDK, the library, and the sample application.
79
+
Please refer to [Build Guide](doc/build.md) for instructions on how to build DPDK, the library, and the sample application.
80
80
81
-
For Windows, please refer to the [Win build guide](doc/build_WIN.md) for instructions on how to build.
81
+
For Windows, please refer to the [Windows Build Guide](doc/build_WIN.md) for instructions on how to build.
82
82
83
83
## 3. Run ST2110
84
84
85
-
Please refer to [run guide](doc/run.md) for instructions on how to set up and run the demo pipeline application based on DPDK PMD backend.
85
+
Please refer to [Run Guide](doc/run.md) for instructions on how to set up and run the demo pipeline application based on DPDK PMD backend.
86
86
87
-
For Windows, please refer to [Windows run guide](doc/run_WIN.md).
87
+
For Windows, please refer to [Run Guide on Windows](doc/run_WIN.md).
88
88
89
-
Additionally, please refer to the [VM guide](doc/vm.md) and [Windows VM guide](doc/vm_WIN.md) for instructions on setting up Linux and Windows guest VMs based on VF passthrough.
89
+
Additionally, please refer to the [VM Guide](doc/vm.md) and [Windows VM Guide](doc/vm_WIN.md) for instructions on setting up Linux and Windows guest VMs based on VF passthrough.
90
90
91
-
For AWS (cloud environment), please refer to [AWS run guide](doc/aws.md) for instructions on how to set up and run the demo.
91
+
For AWS (cloud environment), please refer to [AWS Run Guide](doc/aws.md) for instructions on how to set up and run the demo.
92
92
93
93
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](doc/kernel_socket.md).
94
94
95
95
## 4. ST2110 Programmers guide
96
96
97
-
To quickly develop applications based on the Media Transport Library, please refer to `## 6. ST2110 API` from [design guide](doc/design.md).
97
+
To quickly develop applications based on the Media Transport Library, please refer to section ["ST2110 API" in Design Guide](doc/design.md#6-st2110-api).
98
98
99
99
## 5. User space LibOS UDP stack guide
100
100
@@ -115,7 +115,7 @@ Whitepaper: Open Source Library Enables Real-Time Media over IP Networks. <https
115
115
116
116
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.
117
117
118
-
### 7.1 Fork this repository
118
+
### 7.1. Fork this repository
119
119
120
120
Before opening a pull request, please follow these steps:
121
121
@@ -127,19 +127,19 @@ Before opening a pull request, please follow these steps:
127
127
128
128
If you do not want the main branch automatically synced to the upstream, please go to `Actions` and disable the `Upstream Sync` workflow.
129
129
130
-
### 7.2 Coding style
130
+
### 7.2. Coding style
131
131
132
132
We use the super-linter action for style checks.
133
133
134
-
#### 7.2.1 C/C++
134
+
#### 7.2.1. C/C++
135
135
136
136
For C/C++ coding, you can run the following command to quickly fix the style:
137
137
138
138
```bash
139
139
./format-coding.sh
140
140
```
141
141
142
-
#### 7.2.2 Python
142
+
#### 7.2.2. Python
143
143
144
144
For Python, `black` and `isort` formatter is used.
0 commit comments