DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ciara Loftus <ciara.loftus@intel.com>
To: dev@dpdk.org
Cc: Ciara Loftus <ciara.loftus@intel.com>
Subject: [PATCH 2/3] net/iavf: fix a log during Tx path selection
Date: Thu,  4 Sep 2025 10:44:39 +0000	[thread overview]
Message-ID: <20250904104440.2167205-3-ciara.loftus@intel.com> (raw)
In-Reply-To: <20250904104440.2167205-1-ciara.loftus@intel.com>

The vector offload context path is now selected for outerchecksum and
qinq insert offloads. Update logging to reflect this.

Fixes: abca31f780e1 ("net/iavf: support VLAN insertion for the AVX-512 path")

Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
---
 drivers/net/intel/iavf/iavf_rxtx.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/intel/iavf/iavf_rxtx.c b/drivers/net/intel/iavf/iavf_rxtx.c
index ce0a12c348..5b46fa724c 100644
--- a/drivers/net/intel/iavf/iavf_rxtx.c
+++ b/drivers/net/intel/iavf/iavf_rxtx.c
@@ -4097,7 +4097,7 @@ iavf_set_tx_function(struct rte_eth_dev *dev)
 					    dev->data->port_id);
 			} else if (check_ret == IAVF_VECTOR_CTX_OFFLOAD_PATH) {
 				PMD_DRV_LOG(DEBUG,
-					"AVX2 does not support outer checksum offload.");
+					"AVX2 does not support requested Tx offloads.");
 				goto normal;
 			} else {
 				tx_func_type = IAVF_TX_AVX2_OFFLOAD;
-- 
2.34.1


  parent reply	other threads:[~2025-09-04 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 10:44 [PATCH 0/3] Fixes for iavf " Ciara Loftus
2025-09-04 10:44 ` [PATCH 1/3] net/iavf: fix Tx vector path selection logic again Ciara Loftus
2025-09-04 16:59   ` Bruce Richardson
2025-09-04 10:44 ` Ciara Loftus [this message]
2025-09-04 17:00   ` [PATCH 2/3] net/iavf: fix a log during Tx path selection Bruce Richardson
2025-09-04 10:44 ` [PATCH 3/3] net/iavf: fix Tx path selection for VLAN offload Ciara Loftus
2025-09-04 17:10   ` Bruce Richardson
2025-09-04 17:18 ` [PATCH 0/3] Fixes for iavf Tx path selection Bruce Richardson

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=20250904104440.2167205-3-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;
as well as URLs for NNTP newsgroup(s).