The iavf PMD transmit paths currently use two methods to identify if an mbuf holds an LLDP packet: a dynamic mbuf field and the mbuf ptype. The ptype method is enabled via the enable_ptype_lldp devarg. A future release will remove the dynamic mbuf field approach at which point the ptype will be the only approach used.
Signed-off-by: Ciara Loftus <[email protected]> --- doc/guides/rel_notes/deprecation.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 35c9b4e06c..17f90a6352 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -154,3 +154,7 @@ Deprecation Notices * bus/vmbus: Starting DPDK 25.11, all the vmbus API defined in ``drivers/bus/vmbus/rte_bus_vmbus.h`` will become internal to DPDK. Those API functions are used internally by DPDK core and netvsc PMD. + +* net/iavf: The dynamic mbuf field used to detect LLDP packets on the + transmit path in the iavf PMD will be removed in a future release. + After removal, only packet type-based detection will be supported. -- 2.43.0
