From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: track the physical port in the pipeline
Date: Tue, 19 Jul 2022 05:09:52 +0000 [thread overview]
Message-ID: <PSAPR04MB551607026CC92684F07203D4D68F9@PSAPR04MB5516.apcprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
Hi All,
Is there any configuration or struct store the physical port where the packet is comes in.
Trying below scenario:
I have two pipeline in pipeline1 reading the packets from two links.
Link 0 bound to port 0 and link 1 bound to port 1.
After reading the packets in the pipeline 1 doing the packets match and action using tables.
Finally, it will be sent to pipeline2.
Pipeline2 forward the packets to another physical port.
If packets received in physical port 0 need to forward the traffic to port 2.
If the packets received in physical port 1 need to forward the traffic to port3.
I am unable to decide the out port because packets doesn't info about the port in.
Is there any option available to track the physical port_in?
Any help would be appreciated.
Regards,
Bala
[-- Attachment #2: Type: text/html, Size: 3637 bytes --]
next reply other threads:[~2022-07-19 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 5:09 Balakrishnan K [this message]
2022-07-19 13:08 ` Purnima, Kompella V
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=PSAPR04MB551607026CC92684F07203D4D68F9@PSAPR04MB5516.apcprd04.prod.outlook.com \
--to=balakrishnan.k1@tatacommunications.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).