eth_ring: perf test and usability improvements
Status from this message: Applied, thanks
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | ring: enhance rte_eth_from_ringsdrivers/ | +41 | 0 replies | |
| 2/4 | rte_ring: store memzone pointer inside ringlib/ lib/ | +5 | 1 reply | |
| 3/4 | ring: add rte_eth_from_ring functiondrivers/ drivers/ drivers/ | +27 | 0 replies | |
| 4/4 | test: Add perf test for ring pmdapp/ app/ | +189 | 0 replies |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Olivier Matz | Pablo de Lara |
|---|---|---|
| Series | Series-acked-by | |
| 1/4 | ||
| 2/4 | A-b | |
| 3/4 | ||
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] eth_ring: perf test and usability improvements
This patchset makes it easier to create ring pmd instances from code, by providing a simple ring->ethdev wrapper function and also ensuring that any created rings are ready for use immediately, without having to call configure and rx/tx queue setup.
This set also contains a set of unit tests to compare the performance of basic ring operations against the same operations via the ring ethdev. This shows how the perf penalty can be significant for small bursts, but is much less so for larger bursts of 32 packets.
Bruce Richardson (4):
ring: enhance rte_eth_from_rings
rte_ring: store memzone pointer inside ring
ring: add rte_eth_from_ring function
test: Add perf test for ring pmd
app/test/Makefile | 1 + app/test/test_pmd_ring_perf.c | 188 ++++++++++++++++++++++++++++++ drivers/net/ring/rte_eth_ring.c | 55 ++++++++- drivers/net/ring/rte_eth_ring.h | 14 +++ drivers/net/ring/rte_eth_ring_version.map | 5 + lib/librte_ring/rte_ring.c | 1 + lib/librte_ring/rte_ring.h | 4 + 7 files changed, 262 insertions(+), 6 deletions(-) create mode 100644 app/test/test_pmd_ring_perf.c
Signature · 1 line
2.4.3