This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:tools-software:linuxdsp:docs:linux-kernel-and-drivers:mcapi:mcapi_introduction [26 Jul 2020 05:41] – Sunny Feng | resources:tools-software:linuxdsp:docs:linux-kernel-and-drivers:mcapi:mcapi_introduction [01 Sep 2020 11:37] (current) – jian chen | ||
---|---|---|---|
Line 59: | Line 59: | ||
\\ | \\ | ||
- | ===== Performance of MCAPI ===== | + | ---- |
- | The test method of the performance data of MCAPI is to measure the time required of doing message transactions about 1000 rounds between 2 endpoints on ARM and SHARC, and one round includes sending and receiving one message for each endpoint, | + | **BACK TO** [[resources/ |
- | + | ||
- | ==== Dependencies ==== | + | |
- | + | ||
- | There are many influences in measuring the MCAPI performance: | + | |
- | * Different platform We' | + | |
- | System load We assume that the system load should be normal, and can be ingored, we disable all logs of | + | |
- | * MCAPI(both Linux and Baremetal) | + | |
- | * MCAPI operation mode | + | |
- | + | ||
- | + | ||
- | ==== Result ==== | + | |
- | + | ||
- | Below table is the interval time of 1000 rounds message transaction under different conditions: | + | |
- | + | ||
- | + | ||
- | + | ||
- | ^Board | + | |
- | |sc589-ezkit |190.98ms |186.48ms |174.34ms |150.49ms | + | |
- | |sc584-ezkit |188.72ms |180.95ms |176.29ms |145.65ms | + | |
- | |sc573-ezkit |191.28ms |184.99ms |178.85ms |147.92ms | + |