Reg.dpdk reorder library usage
Volodymyr Fialko
vfialko at marvell.com
Mon Mar 20 12:19:47 CET 2023
Hi,
Could you take a look at the app/test/test_reorder.c `test_reorder_drain()` test case. It follows your steps closely and includes comments that describe the internal state of buffers, which could be helpful during debugging.
From: Balakrishnan K <Balakrishnan.K1 at tatacommunications.com>
Sent: Monday, March 20, 2023 11:54 AM
To: users at dpdk.org
Cc: Volodymyr Fialko <vfialko at marvell.com>
Subject: [EXT] Reg.dpdk reorder library usage
External Email
________________________________
Hi All,
I am planning to use dpdk reorder library in my application.
Used reorder library API's by refereeing the packet ordering example.
Steps:
Our application uses dpdk pipeline.
1.read the packet from rx
2.Create the rte_reorder_create() if not created already or use the existing buffer.
3.iterate through the rx packets and set the sequence number using *rte_reorder_seqn(pkt) = seqn++.
4.insert the packets using the API rte_reorder_insert(ro_buf, pkt);
5.after insert completed I am using rte_reorder_drain API to get the reorder packets .
In step 5 always getting zero packets.
Even though all the rx packets are in order rte_reoder_drain API not giving the output.
Could any please help on this am I missing anything in the implementation .
How to use this library properly.
Tried to run the packet ordering example with 4 ports .
Sent traffic in port 1 there is no packet out in port 1 as mentioned in application example page.
https://doc.dpdk.org/guides/sample_app_ug/packet_ordering.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__doc.dpdk.org_guides_sample-5Fapp-5Fug_packet-5Fordering.html&d=DwMFAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=4iVvgx5PfauIDNaDpT1Ph7naVrkBkhwh2wdQ1AUXVjo&m=LRnVWVWJFPG262ii-XDMQhsmNnSxIXzBIwBY_fRUQsmMdsEDvqC9-T16uF0eYOxo&s=1Oji8GpXbRO608Vsx4e_m1MT1oOXqYA1hx5C6JSiDLY&e=>
Regards,
Bala
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mails.dpdk.org/archives/users/attachments/20230320/84b99f2e/attachment.htm>
More information about the users
mailing list