fix missing Tx multi segs capabilities
Status from this message: Applied to dpdk-next-net-intel.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | net/e1000: fix missing Tx multi segs capabilitydrivers/ | +1 | 0 replies | |
| 2/4 | net/fm10k: fix missing Tx multi segs capabilitydrivers/ | +1 | 0 replies | |
| 3/4 | net/i40e: fix missing Tx multi segs capabilitydrivers/ | +1 | 0 replies | |
| 4/4 | net/ixgbe: fix missing Tx multi segs capabilitydrivers/ | +1 | 0 replies |
Reviews trailers per patch
None of the 4 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Konstantin Ananyev |
|---|---|
| Series | A-b |
| 1/4 | |
| 2/4 | |
| 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] fix missing Tx multi segs capabilities
In former API, ETH_TXQ_FLAGS_NOMULTSEGS was merely a hint indicating that application will never send multisegmented packets, allowing pmd to choose different tx methods accordingly.
In new API, DEV_TX_OFFLOAD_MULTI_SEGS became an offload capability that is advertised by pmds, some of them do not advertise it and expect to never receive fragmented packets (octeontx, axgbe) So an ethdev that supports multisegmented packets should properly advertise it.
Didier Pallard (4):
net/e1000: fix missing Tx multi segs capability
net/fm10k: fix missing Tx multi segs capability
net/i40e: fix missing Tx multi segs capability
net/ixgbe: fix missing Tx multi segs capability
drivers/net/e1000/em_rxtx.c | 1 + drivers/net/fm10k/fm10k_ethdev.c | 1 + drivers/net/i40e/i40e_vf_representor.c | 1 + drivers/net/ixgbe/ixgbe_vf_representor.c | 2 +- 4 files changed, 4 insertions(+), 1 deletion(-)
Signature · 1 line
2.11.0