public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v4 2/3] net/iavf: add AVX2 context descriptor Tx paths
Date: Fri, 17 Apr 2026 13:59:54 +0100	[thread overview]
Message-ID: <aeIuyj5mGdEwI8Td@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260417105610.1161242-3-ciara.loftus@intel.com>

On Fri, Apr 17, 2026 at 10:56:09AM +0000, Ciara Loftus wrote:
> Prior to this commit the transmit paths implemented for AVX2 used the
> transmit descriptor only, making some offloads and features unavailable
> on the AVX2 path, like LLDP. Enable two new AVX2 transmit paths, both
> of which support using a context descriptor, one which performs offload
> and the other which does not.
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2026-04-17 13:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 15:20 [PATCH 0/2] iavf: use ptype for LLDP and add AVX2 ctx paths Ciara Loftus
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
2026-04-17 10:08   ` [PATCH v3 0/3] iavf: LLDP ptype and AVX2 ctx paths Ciara Loftus
2026-04-17 10:08     ` [PATCH v3 1/3] net/iavf: support LLDP Tx via mbuf ptype or dynfield Ciara Loftus
2026-04-17 10:57       ` Bruce Richardson
2026-04-22  9:19         ` Loftus, Ciara
2026-04-17 10:08     ` [PATCH v3 2/3] net/iavf: add AVX2 context descriptor Tx paths Ciara Loftus
2026-04-17 10:08     ` [PATCH v3 3/3] doc: announce change to LLDP packet detection in iavf PMD Ciara Loftus
2026-04-17 10:56     ` [PATCH v4 0/3] iavf: LLDP ptype and AVX2 ctx paths Ciara Loftus
2026-04-17 10:56       ` [PATCH v4 1/3] net/iavf: support LLDP Tx via mbuf ptype or dynfield Ciara Loftus
2026-04-17 13:00         ` Bruce Richardson
2026-04-17 10:56       ` [PATCH v4 2/3] net/iavf: add AVX2 context descriptor Tx paths Ciara Loftus
2026-04-17 12:59         ` Bruce Richardson [this message]
2026-04-17 10:56       ` [PATCH v4 3/3] doc: announce change to LLDP packet detection in iavf PMD Ciara Loftus
2026-04-22  9:16         ` [PATCH v5 0/3] iavf: LLDP ptype and AVX2 ctx paths Ciara Loftus
2026-04-22  9:16           ` [PATCH v5 1/3] net/iavf: support LLDP Tx via mbuf ptype or dynfield Ciara Loftus
2026-04-22  9:16           ` [PATCH v5 2/3] net/iavf: add AVX2 context descriptor Tx paths Ciara Loftus
2026-04-22  9:16           ` [PATCH v5 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=aeIuyj5mGdEwI8Td@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=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