DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Abdulrahman Alshawi <ashawi@wirefilter.com>
To: dev <dev@dpdk.org>
Cc: bharat <bharat@chelsio.com>, stable <stable@dpdk.org>
Subject: [PATCH 0/2] net/cxgbe: fix packed Rx handling and flow port scoping
Date: Mon, 27 Apr 2026 19:30:18 +0300 (AST)	[thread overview]
Message-ID: <2136264989.15868282.1777307418083.JavaMail.zimbra@wirefilter.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

 
 
 

This series fixes two correctness issues in the cxgbe PMD that can cause
traffic loss on Chelsio T6 adapters, especially when rte_flow QUEUE
rules concentrate ingress on a small set of RX queues. 

Patch 1 fixes packed Rx response handling. The current PMD assumes every
response descriptor starts a new Free List buffer by requiring
F_RSPD_NEWBUF on each response. That assumption does not always hold for
packed ingress responses. Under sustained small-packet traffic to a
single ingress queue, the FL/IQ state goes out of sync and the affected
Rx path stops making forward progress. 

Patch 2 scopes rte_flow rules to the ingress port they were created on.
Chelsio filters are programmed in adapter-wide tables, and the PMD
already supports the iport field in the hardware filter spec. However,
the flow parser never fills it for normal per-port rules, so a rule
created on one port can also match traffic arriving on sibling ports of
the same adapter. 

Both issues reproduce with stock testpmd on T62100-LP-CR. The per-patch
commit messages include the details and reproducers. 

Abdulrahman Alshawi (2):
net/cxgbe: fix Rx handling for packed responses
net/cxgbe: restrict rte_flow rules to ingress port 

.mailmap | 1 +
drivers/net/cxgbe/base/adapter.h | 1 +
drivers/net/cxgbe/cxgbe_flow.c | 19 +++++
drivers/net/cxgbe/sge.c | 122 ++++++++++++++++++++++++-------
4 files changed, 118 insertions(+), 25 deletions(-) 

--
2.39.5   
 

[-- Attachment #2: Type: text/html, Size: 1841 bytes --]

             reply	other threads:[~2026-04-29  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 16:30 Abdulrahman Alshawi [this message]
2026-04-27 16:40 ` [PATCH 1/2] net/cxgbe: fix Rx handling for packed responses Abdulrahman Alshawi
2026-04-28  7:05   ` Abdulrahman Alshawi
2026-04-27 16:42 ` [PATCH 2/2] net/cxgbe: restrict rte flow rules to ingress port Abdulrahman Alshawi
2026-04-28  7:03   ` Abdulrahman Alshawi

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=2136264989.15868282.1777307418083.JavaMail.zimbra@wirefilter.com \
    --to=ashawi@wirefilter.com \
    --cc=bharat@chelsio.com \
    --cc=dev@dpdk.org \
    --cc=stable@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