From: NAGENDRA BALAGANI <nagendra.balagani@oracle.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Kapil Kumar Jain <kapil.k.jain@oracle.com>
Subject: Strange behavior with rte_pktmbuf_clone cal
Date: Fri, 23 Dec 2022 07:00:40 +0000 [thread overview]
Message-ID: <DM6PR10MB4124C6E61BBC5AD77E5F206696E99@DM6PR10MB4124.namprd10.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1798 bytes --]
Hi,
I am seeing strange behavior where rte_pktmbuf_clone is not giving desired result.
Here is the detailed info, in my dpdk application , once I received the packet info in mbuf, I need to send the same packet to two destinations, the sequence I should follow is,
(i) First, Tunnel the packet to one of desired destination, so I created the shallow copy using rte_pktmbuf_clone, had another mbuf for Outer IP Header for IPinIP tunnel and sent to NIC.
(ii) Second, I need to modify the source and destination ip addresses of the packet and send out.
The issue, I am seeing is the tunneled packet (clone) have modified IP addresses from (ii).
Code flow:
Main()
{
Struct rte_mbuf *org_mbuf; //lets assume this org_mbuf is holding the packet info.
(i) Towards First destination.
Build_tunnel_packet(org_mbuf) {
- Struct rte_mbuf *clone_buffer;
- Allocate a clone buffer Clone_buffer = rte_pktmbuf_clone(org_mbuf, clone_pool);
- Constructed IPinIP info in another mbuf and prepended in clone_buffer
- Call rte_pktmbuf_tx_burst();
}
(ii) Towards another destination.
Modify_l3_and_route(org_mbuf)
{
- Modify L3 information of 'org_mbuf'
- and Call rte_pkt_mbuf_tx_burst();
}
}
[cid:image001.jpg@01D916CA.5B7CCA10]
In the above screenshot, the packet 37 should tunneled as it is by adding the outer ip layer(i.e 182.16.146.*), but the inner L3 information also getting changed (which I am modifying in the second step) for some packets.
Using, rte_pktmbuf_copy(), solving the issue, but in expense of extra mbuf.
Please, help me in understanding what is wrong in the case of rte_pktmbuf_clone()?
Regards,
Nagendra
[-- Attachment #1.2: Type: text/html, Size: 15596 bytes --]
[-- Attachment #2: image001.jpg --]
[-- Type: image/jpeg, Size: 159359 bytes --]
next reply other threads:[~2022-12-23 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 7:00 NAGENDRA BALAGANI [this message]
2022-12-23 16:25 ` Konstantin Ananyev
2022-12-23 16:43 ` Stephen Hemminger
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=DM6PR10MB4124C6E61BBC5AD77E5F206696E99@DM6PR10MB4124.namprd10.prod.outlook.com \
--to=nagendra.balagani@oracle.com \
--cc=dev@dpdk.org \
--cc=kapil.k.jain@oracle.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).