DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1112] MLX5: Not able to configure flows on PPPoE, stacked vlan tunnels & enable multiple tunnels at a time
Date: Wed, 19 Oct 2022 13:25:18 +0000	[thread overview]
Message-ID: <bug-1112-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=1112

            Bug ID: 1112
           Summary: MLX5: Not able to configure flows on PPPoE, stacked
                    vlan tunnels & enable multiple tunnels at a time
           Product: DPDK
           Version: 22.03
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: cagniburto@vusra.com
  Target Milestone: ---

Hello Team,

We need to distribute packets on Inner-Hash5Tuple (IP-IP-Port-Port-Protocol) on
Rx queues of below mentioned packet hierarchies. 
we're using rte_flow to create rules on group 0 with action RSS.

Packet hierarchy:
Case 1:
ETH->VLAN1_QinQ->VLAN2_QinQ->VLAN3_QinQ->VLAN4_QinQ->PPPoE->PPP->IPv4/v6->TCP/UDP.

We tried following:
1. If we configure flow rte_flow_item pattern as ETH->VLAN->VLAN, API throws
error for multiple VLANs
2. If we configure ETH->ANY->PPPoES->.., API throws "item not supported"

Please suggest way to support the hierarchy.


Secondly, 
we want to enable GTP, IPinIP & other tunnels at same time, to enable GTP, mlx5
has configure to FLEX_PARSER_PROFILE_ENABLE=3 & to other value to support
another. 

Card Model: Connectx-6 Dx
OS: Ubuntu 20.04
Firmware: 22.32.2004

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

                 reply	other threads:[~2022-10-19 13:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-1112-3@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).