Re: [PATCH 0/8] Fixes for ice and iavf docs

[Bruce Richardson <bruce.richardson@intel.com>]

On Tue, Sep 16, 2025 at 02:21:05PM +0000, Ciara Loftus wrote:
> This series is a collection of fixes to the documentation (specifically
> the ini files) for the ice and iavf drivers.
> 
> Ciara Loftus (8):
>   net/ice: document support for free Tx mbuf on demand
>   net/ice: fix documentation of support for TSO
>   net/iavf: fix documentation for speed capabilities
>   net/iavf: document support for fast mbuf free
>   net/iavf: document support for free Tx mbuf on demand
>   net/iavf: document support for burst mode info
>   net/iavf: fix documentation of support for TSO
>   net/iavf: document support for extended statistics
> 
>  doc/guides/nics/features/iavf.ini | 7 +++++--
>  doc/guides/nics/features/ice.ini  | 3 ++-
>  2 files changed, 7 insertions(+), 3 deletions(-)
> 
> -- 

When reviewing these, I'm not convinced about using "P" (Partial) as a flag
to indicate features that don't work on vector drivers. Since the feature
is present in the driver and works - all be it with a perf hit, as happens
with many features, even those that don't change the actual Rx/Tx function
chosen - I think it should be marked as just "Y", and that using "P" is
confusing. Can we maybe investigate other options here, maybe a footnote or
asterisk on the entry that says: "May not be present in all Rx/Tx paths, for
example, may force driver to use scalar, rather than vector, code paths"

Since the rest of the changes are trivial, I've just applied the other
five patches, (1, 3, 5, 6, 8) to next-net-intel, rather than carry a whole
series through multiple versions.

Thanks,
/Bruce