DPDK usage discussions
 help / color / mirror / Atom feed
From: 최영민 <youngminchoi94@gmail.com>
To: users@dpdk.org
Subject: tunnel offload + TX with rte_flow
Date: Mon, 15 May 2023 00:06:13 +0900	[thread overview]
Message-ID: <CAJzpdK52AKYTimxix5FDKs=Xc8Z8v6Ubf-Xd0sDf9i8eKyodXw@mail.gmail.com> (raw)

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

Hi, all

Previously, I used RAW_ENCAP/RAW_DECAP actions to create flow rules for
tunnel offload. But, what I want to do is forward packets directly after
performing RAW_ENCAP/RAW_DECAP.

For example, the current packet processing pipeline is
 1. tunneled packets arrived at NIC -> 2. RAW_ENCAP/DECAP by rte_flow -> 3.
rte_eth_rx_burst() -> 4. processing packet -> 5. rte_eth_tx_burst()

But, for some packets, I don't need to process packets and want to
forward them as fast as possible. So, what I want is 1.  tunneled packets
arrived at NIC -> 2. RAW_ENCAP/DECAP by rte_flow and Tx them directly.

If it is possible with rte_flow or other methods, please let me know.

Thank you.
Regard
Youngmin

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

                 reply	other threads:[~2023-05-17 14:35 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='CAJzpdK52AKYTimxix5FDKs=Xc8Z8v6Ubf-Xd0sDf9i8eKyodXw@mail.gmail.com' \
    --to=youngminchoi94@gmail.com \
    --cc=users@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).