track the physical port in the pipeline

[Purnima, Kompella V]

struct rte_mbuf in DPDK 19.11 has a field called port
When packets are received using rte_eth_rx_burst API, struct rte_mbuf::port will be filled with index value of the ethernet port on which the packet was received.

This works with MLX ConnectX4. Hope this helps.

Regards
Purnima

From: Balakrishnan K <Balakrishnan.K1 at tatacommunications.com>
Sent: July 19, 2022 10:40 AM
To: users at dpdk.org
Subject: track the physical port in the pipeline

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 bo
External (balakrishnan.k1 at tatacommunications.com<mailto:balakrishnan.k1 at tatacommunications.com>)
  Report This Email<https://protection.inkyphishfence.com/report?id=Y29tbXNjb3BlL2tvbXBlbGxhLnB1cm5pbWFAY29tbXNjb3BlLmNvbS82ZDNjMGVkN2M0ODZhYWMxMjIwYmU0ZWEzMmZjOGY3Yi8xNjU4MjA3NDE1Ljcx#key=8b4a8f5e9f14d75233fae3f9d1a64991>  FAQ<https://www.inky.com/banner-faq>  Protection by INKY<https://www.inky.com/protection-by-inky>

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



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/users/attachments/20220719/285075d6/attachment.htm>