On 07/07/2017 06:06 PM, Ferruh Yigit wrote:
On 7/7/2017 11:55 AM, Andrew Rybchenko wrote:
<...>
+TSO
+---
+
+Supports TCP Segmentation Offloading.
+
+* **mbuf**: ``mbuf.ol_flags:PKT_TX_TCP_SEG``.
DEV_TX_OFFLOAD_*_TSO in tx_offload_capa
Is support of one TSO option sufficient to say Yes?
This is common question for a few offload features, like ones that can
be valid for Rx and Tx path, I guess feature should be "Yes" if all are
supported, otherwise "P(artial)".
IMHO, it would be more informative to have separate features for TCP,
UDP and
encapsulated TSO offloads.
Otherwise when a new TSO offload flag is added, it should change all Y to P
(and update PMDs documentation to provide details).
But this is hard to trace and if marked as "P", makes hard to figure out
what is supported.
Ideally for all "P" it should be a hyperlink to PMD documentation section
which provides details.
<...>
<...>
