DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kishore Padmanabha <kishore.padmanabha@broadcom.com>,
	Thomas Monjalon <thomas@monjalon.net>
Cc: Ferruh.yigit@xilinx.com, qi.z.zhang@intel.com, dev@dpdk.org
Subject: Re: MPLS Push action
Date: Mon, 3 Mar 2025 09:04:03 -0800	[thread overview]
Message-ID: <CACZ4nhuSCiD6gNzF2GFXVoAD__f0oOgu8fXCwRYy6UGMDy3atQ@mail.gmail.com> (raw)
In-Reply-To: <b62e330e086126415f7b4987a9747ce2@mail.gmail.com>

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

+Thomas Monjalon

On Mon, Mar 3, 2025 at 8:02 AM Kishore Padmanabha
<kishore.padmanabha@broadcom.com> wrote:
>
> Hi,
>
>
>
> Anyone has any inputs on this. Or should I add new CLI commands in testpmd to support action for push MPLS tag.
>
>
>
> Thanks,
>
> Kishore
>
>
>
>
>
> From: Kishore Padmanabha <kishore.padmanabha@broadcom.com>
> Sent: Thursday, February 27, 2025 6:35 PM
> To: 'dev@dpdk.org' <dev@dpdk.org>
> Subject: MPLS Push action
>
>
>
> Hi,
>
>
>
> When MPLS push action is used, using testpmd action  of_push_mpls, it accepts the ethertype only. How do I specify the MPLS label and other fields for the MPLS header to be added ? In the doc, in section 7.2.3.7 there is mention of OFXPMT_OFB_MPLS_LABEL and other MPLS fields, but I could not find that in dpdk implementation.
>
>
>
> Thanks,
>
> Kishore
>
>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]

  reply	other threads:[~2025-03-03 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 16:02 Kishore Padmanabha
2025-03-03 17:04 ` Ajit Khaparde [this message]
2025-03-03 19:25   ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27 23:35 Kishore Padmanabha

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=CACZ4nhuSCiD6gNzF2GFXVoAD__f0oOgu8fXCwRYy6UGMDy3atQ@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=Ferruh.yigit@xilinx.com \
    --cc=dev@dpdk.org \
    --cc=kishore.padmanabha@broadcom.com \
    --cc=qi.z.zhang@intel.com \
    --cc=thomas@monjalon.net \
    /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).