From: Tarun Badnora <tarun.badnora@clear-trail.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "dev-owner@dpdk.org" <dev-owner@dpdk.org>
Subject: RE: RSS on L2TP, Teredo, PPPoE Tunnels
Date: Tue, 15 Nov 2022 08:45:29 +0000 [thread overview]
Message-ID: <PN1PR0101MB190134F10E0DBD49D332B220A4049@PN1PR0101MB1901.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <PN1PR0101MB19018A89F6A38660F1FD6B23A4019@PN1PR0101MB1901.INDPRD01.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hello Team,
A gentle reminder.
Regards,
From: Tarun Badnora
Sent: 10 November 2022 20:18
To: dev@dpdk.org
Subject: RSS on L2TP, Teredo, PPPoE Tunnels
Hello DPDK Team,
Hope you guys are doing great !!
We are developing application with dpdk 22.03 & Mellanox Connectx-6 adapter,
Want to use IP-Port tuples (Inner in case of tunnels) to RSS traffic to multiple queues.
We need to handle L2TPv2/3, Teredo, PPPoE etc, but adapter have limited tunnels support.
Is there a way/possibility in DPDK to support mentioned or define user specific tunnels & achieve RSS on inner tuples ?
From documentation, we came across these approaches:
1. Rte flow Flex item:
a. This is not supported by adapter.
2. testpmd> flow tunnel create 0 type "":
a. Not getting documentation to check.
Please suggest.
Environment:
* OS: Ubuntu 20.04
* Driver: MLNX_OFED_LINUX-5.5-1.0.3.2
* Firmware: 22.32.2004
Regards,
Tarun Badnora
[-- Attachment #2: Type: text/html, Size: 10534 bytes --]
next prev parent reply other threads:[~2022-11-15 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 14:47 Tarun Badnora
2022-11-15 8:45 ` Tarun Badnora [this message]
2022-11-21 5:23 ` Gregory Etelson
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=PN1PR0101MB190134F10E0DBD49D332B220A4049@PN1PR0101MB1901.INDPRD01.PROD.OUTLOOK.COM \
--to=tarun.badnora@clear-trail.com \
--cc=dev-owner@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).