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. 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 ac667e91a6..e450f9e56d 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -139,3 +139,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 method of detecting an LLDP packet on the transmit path + in the iavf PMD will be changed. Instead of using either a dynamic mbuf + field or the mbuf ptype, only the mbuf ptype will be used. -- 2.43.0
