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


[-- Attachment #1.1: Type: text/plain, Size: 1539 bytes --]

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
<https://opennetworking.org/wp-content/uploads/2014/10/openflow-switch-v1.5.1.pdf>,
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

-- 
This electronic communication and the information and any files transmitted 
with it, or attached to it, are confidential and are intended solely for 
the use of the individual or entity to whom it is addressed and may contain 
information that is confidential, legally privileged, protected by privacy 
laws, or otherwise restricted from disclosure to anyone else. If you are 
not the intended recipient or the person responsible for delivering the 
e-mail to the intended recipient, you are hereby notified that any use, 
copying, distributing, dissemination, forwarding, printing, or copying of 
this e-mail is strictly prohibited. If you received this e-mail in error, 
please return the e-mail to the sender, delete it from your computer, and 
destroy any printed copy of it.

[-- Attachment #1.2: Type: text/html, Size: 3533 bytes --]

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

             reply	other threads:[~2025-03-03 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 16:02 Kishore Padmanabha [this message]
2025-03-03 17:04 ` Ajit Khaparde
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=b62e330e086126415f7b4987a9747ce2@mail.gmail.com \
    --to=kishore.padmanabha@broadcom.com \
    --cc=Ferruh.yigit@xilinx.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    /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).