DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1266] net/mlx5: cannot create rte_flow rule matching ethernet multicast with jump action on bond mode 4
Date: Mon, 27 Oct 2025 14:07:17 +0000	[thread overview]
Message-ID: <bug-1266-3-1xT2p2f45L@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1266-3@http.bugs.dpdk.org/>

http://bugs.dpdk.org/show_bug.cgi?id=1266

mkashani@nvidia.com (mkashani@nvidia.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
                 CC|                            |mkashani@nvidia.com
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #1 from mkashani@nvidia.com (mkashani@nvidia.com) ---
Hi, 
Sorry for the late response,

**Root Cause**: MLX5 hardware/firmware steering on root table (group 0) has
limited support for jump actions combined with partial MAC address masks. The
bonding PMD directly passes the flow to slave ports without adaptation.

## Immediate Workarounds

### Workaround 1: Use Group 1 (Recommended)
Instead of group 0, use group 1:

```bash
flow create 2 group 1 priority 0 ingress pattern eth dst spec 01:00:00:00:00:00
dst mask 01:00:00:00:00:00 / end actions jump group 2 / end
```

First, create a catch-all rule in group 0 to reach group 1:
```bash
flow create 2 group 0 priority 1 ingress pattern eth / end actions jump group 1
/ end
```

-- 
You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2025-10-27 14:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 13:48 [Bug " bugzilla
2025-10-27 14:07 ` bugzilla [this message]

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=bug-1266-3-1xT2p2f45L@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).