patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Prashant Gupta <prashant.gupta_3@nxp.com>
To: dev@dpdk.org, stephen@networkplumber.org, david.marchand@redhat.com
Cc: stable@dpdk.org, Brick Yang <brick.yang@nxp.com>
Subject: [PATCH 04/15] net/dpaa2: fix to recv packets with additional parse errors
Date: Tue, 14 Oct 2025 12:10:24 +0530	[thread overview]
Message-ID: <20251014064035.1312896-5-prashant.gupta_3@nxp.com> (raw)
In-Reply-To: <20251014064035.1312896-1-prashant.gupta_3@nxp.com>

From: Brick Yang <brick.yang@nxp.com>

Also receive packets with HW parser length errors.
Thus this option allow to let HW drop packets for any kind of parser
errors.

Fixes: 4690a6114ff6 ("net/dpaa2: enable error queues optionally")
Cc: stable@dpdk.org

Signed-off-by: Brick Yang <brick.yang@nxp.com>
---
 drivers/net/dpaa2/dpaa2_ethdev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/net/dpaa2/dpaa2_ethdev.c b/drivers/net/dpaa2/dpaa2_ethdev.c
index 41678ce09b..0fd577c448 100644
--- a/drivers/net/dpaa2/dpaa2_ethdev.c
+++ b/drivers/net/dpaa2/dpaa2_ethdev.c
@@ -1240,7 +1240,7 @@ dpaa2_dev_start(struct rte_eth_dev *dev)
 		err_cfg.errors = DPNI_ERROR_L3CE | DPNI_ERROR_L4CE;
 
 		/* if packet with parse error are not to be dropped */
-		err_cfg.errors |= DPNI_ERROR_PHE;
+		err_cfg.errors |= DPNI_ERROR_PHE | DPNI_ERROR_BLE;
 
 		err_cfg.error_action = DPNI_ERROR_ACTION_CONTINUE;
 	}
-- 
2.43.0


  parent reply	other threads:[~2025-10-16 19:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251014064035.1312896-1-prashant.gupta_3@nxp.com>
2025-10-14  6:40 ` [PATCH 01/15] net/dpaa2: fix uninitialized variable issue Prashant Gupta
2025-10-14  6:40 ` [PATCH 02/15] net/dpaa2: fix to free buffers from error queue Prashant Gupta
2025-10-14  6:40 ` [PATCH 03/15] net/dpaa2: fix L3/L4 csum results in packet parse Prashant Gupta
2025-10-15 15:34   ` Hemant Agrawal
2025-10-14  6:40 ` Prashant Gupta [this message]
2025-10-15 15:35   ` [PATCH 04/15] net/dpaa2: fix to recv packets with additional parse errors Hemant Agrawal
2025-10-14  6:40 ` [PATCH 05/15] net/dpaa2: fix error frame dump issue Prashant Gupta
2025-10-14  6:40 ` [PATCH 06/15] net/dpaa2: fix flow rule's resizing issue Prashant Gupta
     [not found] ` <20251016102805.2453687-1-prashant.gupta_3@nxp.com>
2025-10-16 10:27   ` [PATCH v2 01/15] net/dpaa2: fix uninitialized variable issue Prashant Gupta
2025-10-16 10:27   ` [PATCH v2 02/15] net/dpaa2: fix to free buffers from error queue Prashant Gupta
2025-10-16 10:27   ` [PATCH v2 03/15] net/dpaa2: fix L3/L4 csum results in packet parse Prashant Gupta
2025-10-16 10:27   ` [PATCH v2 04/15] net/dpaa2: fix to recv packets with additional parse errors Prashant Gupta
2025-10-16 10:27   ` [PATCH v2 05/15] net/dpaa2: fix error frame dump issue Prashant Gupta
2025-10-16 10:27   ` [PATCH v2 06/15] net/dpaa2: fix flow rule's resizing issue Prashant Gupta
     [not found] <20251014060045.1304694-1-prashant.gupta_3@nxp.com>
2025-10-14  6:00 ` [PATCH 04/15] net/dpaa2: fix to recv packets with additional parse errors Prashant Gupta
     [not found] <20251014055605.1303410-1-prashant.gupta_3@nxp.com>
2025-10-14  5:55 ` Prashant Gupta

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=20251014064035.1312896-5-prashant.gupta_3@nxp.com \
    --to=prashant.gupta_3@nxp.com \
    --cc=brick.yang@nxp.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).