net/gve: out of order completion processing for DQO
Status from this message: Queued to next-net
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | net/gve: free Rx mbufs if allocation fails on ring setupdrivers/ | +5 | 0 replies | |
| 2/4 | net/gve: add datapath-specific logging for gvedrivers/ drivers/ drivers/ | +12 | 0 replies | |
| 3/4 | net/gve: support for out of order completions on DQ Txdrivers/ drivers/ drivers/ | +160 | 0 replies | |
| 4/4 | net/gve: support for out of order completions on DQ Rxdrivers/ drivers/ | +92 | 0 replies |
Reviews trailers per patch
All 4 patches have a Reviewed-by or Acked-by.
| Patch | Ankit Garg | Ziwei Xiao |
|---|---|---|
| 1/4 | R-b | R-b |
| 2/4 | R-b | |
| 3/4 | R-b | |
| 4/4 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] net/gve: out of order completion processing for DQO
Both RX and TX processing on DQ were originally implemented with the asusmption that descriptor completions will be written by the hardware in the order that they are posted. In certain cases, such as RSC on RX and double completions on TX, this will not necessarily be the case.
Depends-on: series-35656 ("net/gve: Tx datapath fixes for GVE DQO")
Joshua Washington (4):
net/gve: free Rx mbufs if allocation fails on ring setup net/gve: add datapath-specific logging for gve net/gve: support for out of order completions on DQ Tx net/gve: support for out of order completions on DQ Rx
drivers/net/gve/base/gve_adminq.c | 2 +- drivers/net/gve/gve_ethdev.h | 20 ++- drivers/net/gve/gve_logs.h | 3 + drivers/net/gve/gve_rx_dqo.c | 135 +++++++++++----- drivers/net/gve/gve_tx_dqo.c | 250 ++++++++++++++++++------------ 5 files changed, 267 insertions(+), 143 deletions(-)
Signature · 1 line
2.51.0.rc1.167.g924127e9c0-goog