From: Ciara Loftus <ciara.loftus@intel.com>
To: dev@dpdk.org
Cc: Ciara Loftus <ciara.loftus@intel.com>
Subject: [PATCH 0/2] iavf: use ptype for LLDP and add AVX2 ctx paths
Date: Mon, 9 Feb 2026 15:20:47 +0000 [thread overview]
Message-ID: <20260209152049.1640121-1-ciara.loftus@intel.com> (raw)
This series changes the iavf driver to use the mbuf packet type
field instead of a dynamic field for LLDP packets, and adds new AVX2
context descriptor Tx paths which support LLDP.
Ciara Loftus (2):
net/iavf: use mbuf packet type instead of dynfield for LLDP
net/iavf: add AVX2 context descriptor Tx paths
doc/guides/nics/intel_vf.rst | 16 +-
doc/guides/rel_notes/release_26_03.rst | 2 +
drivers/net/intel/iavf/iavf.h | 2 +
drivers/net/intel/iavf/iavf_ethdev.c | 13 +-
drivers/net/intel/iavf/iavf_rxtx.c | 21 +-
drivers/net/intel/iavf/iavf_rxtx.h | 12 +-
drivers/net/intel/iavf/iavf_rxtx_vec_avx2.c | 386 ++++++++++++++++++++
drivers/net/intel/iavf/iavf_testpmd.c | 20 +-
drivers/net/intel/iavf/rte_pmd_iavf.h | 10 +
9 files changed, 448 insertions(+), 34 deletions(-)
--
2.43.0
next reply other threads:[~2026-02-09 15:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 15:20 Ciara Loftus [this message]
2026-02-09 15:20 ` [PATCH 1/2] net/iavf: use mbuf packet type instead of dynfield for LLDP Ciara Loftus
2026-02-09 16:10 ` Bruce Richardson
2026-03-06 11:49 ` Loftus, Ciara
2026-02-09 15:20 ` [PATCH 2/2] net/iavf: add AVX2 context descriptor Tx paths Ciara Loftus
2026-03-06 11:52 ` [PATCH v2 0/3] iavf: LLDP ptype and AVX2 ctx paths Ciara Loftus
2026-03-06 11:52 ` [PATCH v2 1/3] net/iavf: support LLDP Tx based on mbuf ptype or dynfield Ciara Loftus
2026-03-06 11:52 ` [PATCH v2 2/3] net/iavf: add AVX2 context descriptor Tx paths Ciara Loftus
2026-03-06 11:52 ` [PATCH v2 3/3] doc: announce change to LLDP packet detection in iavf PMD Ciara Loftus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260209152049.1640121-1-ciara.loftus@intel.com \
--to=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox