From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 618F9427F2 for ; Tue, 21 Mar 2023 06:10:43 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 28F2A40A7F; Tue, 21 Mar 2023 06:10:43 +0100 (CET) Received: from APC01-SG2-obe.outbound.protection.outlook.com (mail-sgaapc01on2063.outbound.protection.outlook.com [40.107.215.63]) by mails.dpdk.org (Postfix) with ESMTP id A6C9140A7A for ; Tue, 21 Mar 2023 06:10:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tatacommunications.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L5zgym0pLy+ZRKzuT9ajnywj6wyC8eP8FP/fr8G+Bi8=; b=GbCo8hnSCGOzeHwO21GyebqRq9eV0o/n12AQH012IVgb/i0f3lmSyMwH886u5DYe/jc6LoIEShmXJ6aJj/IOBSOoTA5dy73xJqzaH7RSixpujFiwTXn6Ujw6Vbm6fXSPVg7N2abgo5ozEXdFZ1M1pWRl/7fZwT1rKbNR7f+9VTpJne7gaigaQYSz2X5R1YDWlVyUsjVQNa110v8xHoJFluv8vGPnw3KNgN+wt6x59rHouvFJ339t8s3mW3evhFMT6JYf1lBW5oWTsUdW+ZrCPTwZYdXHPwgssCMAiOywwXTqx0GwXe0/XveYzIfmsbs1SffgXQduyNRGGsJi46hCCg== Received: from TY2PR02CA0070.apcprd02.prod.outlook.com (2603:1096:404:e2::34) by SEYPR04MB5715.apcprd04.prod.outlook.com (2603:1096:101:8a::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6178.37; Tue, 21 Mar 2023 05:10:38 +0000 Received: from TYZAPC01FT022.eop-APC01.prod.protection.outlook.com (2603:1096:404:e2:cafe::21) by TY2PR02CA0070.outlook.office365.com (2603:1096:404:e2::34) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6178.37 via Frontend Transport; Tue, 21 Mar 2023 05:10:38 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 54.79.123.149) smtp.mailfrom=tatacommunications.com; dkim=pass (signature was verified) header.d=tatacommunications.com;dmarc=pass action=none header.from=tatacommunications.com; Received-SPF: Pass (protection.outlook.com: domain of tatacommunications.com designates 54.79.123.149 as permitted sender) receiver=protection.outlook.com; client-ip=54.79.123.149; helo=sydapipop-haraka-inline01.vpc-a3a96cc4.ase2.shn; pr=C Received: from sydapipop-haraka-inline01.vpc-a3a96cc4.ase2.shn (54.79.123.149) by TYZAPC01FT022.mail.protection.outlook.com (10.118.152.106) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6222.16 via Frontend Transport; Tue, 21 Mar 2023 05:10:36 +0000 Received: from APC01-PSA-obe.outbound.protection.outlook.com (mail-psaapc01lp2046.outbound.protection.outlook.com [104.47.26.46]) by sydapipop-haraka-inline01.vpc-a3a96cc4.ase2.shn (Haraka/2.8.24) with ESMTPS id 5F4BFAEF-96AB-4F4B-84C3-B00CEAC102EB.1 envelope-from (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 verify=FAIL); Tue, 21 Mar 2023 05:10:33 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DmDtQPNA8vIMeA8pIPiFacN5JYDcFccCKYujZ6gm1/M0d5K3LXZqkaR1xAZTPH2gpn1+CCfvy4gFos7KD6zuT4fNVMwG5/sqJ0i44t1dC/8JtG2Bs6VMa9x0pqkx11EcQ0RtVQADuV2BBKriBIQFf+zVrKFec/K3VrSMlqL3/E9XYG7LhpXawYcUIVq1ufMTzF5mOfL8FJJHFlPHVDkH2hDYPOofBaNxaxjSry9pZfoMqLdyyb8CrwebkVnQZv1fB5nCRKOqdQv4eJB8J37F9y3pF1VMLoF+BmxVC3TSId8EPa+vpul9JXPW9NUePACdvuuBGvQEcOMQbiT8i/A9Ww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=L5zgym0pLy+ZRKzuT9ajnywj6wyC8eP8FP/fr8G+Bi8=; b=GGcS0NMhiwpMPE2EKLZ6aem6Ush6NrfztCbkq4KheCB7rxFhVjI2wQYT0vsgKImKFHzpWVFYOKpwioZ4pwtNNMpRMOOu4ngCcccIgGpHaXncgsJcnadYA6jYPUzHplR6dxgxYVJzHm+wSkVmgXi1jomoipLjVHud39WaojYU9UqwEcZewbSRYkOV9DAFke/iOsttJOAPdnSImawxO4GraCu24T3dK41n3OWoUfvtK6sZxNW+PJnZwOnBXPY5ffRNa7VY6G6SNQ5pjT8KS3JeisrIs+3WcQkm9f7/5msBuyQR8/jHeUu8q19Z2GtEqIlMKBlMDh5fQiFdd++w6i0R/A== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=tatacommunications.com; dmarc=pass action=none header.from=tatacommunications.com; dkim=pass header.d=tatacommunications.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tatacommunications.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L5zgym0pLy+ZRKzuT9ajnywj6wyC8eP8FP/fr8G+Bi8=; b=GbCo8hnSCGOzeHwO21GyebqRq9eV0o/n12AQH012IVgb/i0f3lmSyMwH886u5DYe/jc6LoIEShmXJ6aJj/IOBSOoTA5dy73xJqzaH7RSixpujFiwTXn6Ujw6Vbm6fXSPVg7N2abgo5ozEXdFZ1M1pWRl/7fZwT1rKbNR7f+9VTpJne7gaigaQYSz2X5R1YDWlVyUsjVQNa110v8xHoJFluv8vGPnw3KNgN+wt6x59rHouvFJ339t8s3mW3evhFMT6JYf1lBW5oWTsUdW+ZrCPTwZYdXHPwgssCMAiOywwXTqx0GwXe0/XveYzIfmsbs1SffgXQduyNRGGsJi46hCCg== Received: from PSAPR04MB5516.apcprd04.prod.outlook.com (2603:1096:301:5c::9) by PSAPR04MB4264.apcprd04.prod.outlook.com (2603:1096:301:31::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6178.37; Tue, 21 Mar 2023 05:10:30 +0000 Received: from PSAPR04MB5516.apcprd04.prod.outlook.com ([fe80::b875:f958:cdad:7e08]) by PSAPR04MB5516.apcprd04.prod.outlook.com ([fe80::b875:f958:cdad:7e08%5]) with mapi id 15.20.6178.037; Tue, 21 Mar 2023 05:10:30 +0000 From: Balakrishnan K To: Volodymyr Fialko , "users@dpdk.org" Subject: RE: Reg.dpdk reorder library usage Thread-Topic: Reg.dpdk reorder library usage Thread-Index: AdlbGEnJUrbOTDLTQ82/Ohx5oZty2wAA6ZhQAAGhq+MAI+LKIA== Date: Tue, 21 Mar 2023 05:10:30 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_ContentBits=0; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_Enabled=True; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_Method=Privileged; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_Name=General-Test; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_SetDate=2023-03-20T10:53:48.0000000Z; MSIP_Label_5cbf6393-50e2-4904-bc3e-1804619f2b03_SiteId=20210462-2c5e-4ec8-b3e2-0be950f292ca; Authentication-Results-Original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=tatacommunications.com; x-ms-traffictypediagnostic: PSAPR04MB5516:EE_|PSAPR04MB4264:EE_|TYZAPC01FT022:EE_|SEYPR04MB5715:EE_ X-MS-Office365-Filtering-Correlation-Id: df6624ef-aa99-4e03-9268-08db29ca9b50 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam-Untrusted: BCL:0; X-Microsoft-Antispam-Message-Info-Original: EoQcA/NbXcrr0okc+nv0UuPvnwVbFG1XA0shclKEQ0qJ9C2OdH68I9ZfhacUITPjF4jowOAXmBW9ftu9t+OvkTIjsat8j0g0fscZSHPzIuKURRlD6XMoZHVRH+6zzPyKfop+eiFxDIh+q8OhS55XeR0hBfAQf5F6Zc3SaFPGEImKZlNyhQk5bjjrmb9sxCJQ7hjZ7oCuMy/vZYd7i6x/dNO1ttU3fnU04f5NHkCuXTbgx+nVRvP9kWHuGEd7IZ9NOy3Ozh20wOxG8suMiGC40g4c4AEL/Cg24Jo2DZ4I/hh6AVAN0aEC4XMpAzwmrURma1+TI+V3Su9Px9jVA6Rg+9ZOE7ULFdQf/U3gFWMEosp3Q9GVqQohGVRChe5RPYkRZcWgxdOxV7hPtTGP9J0nxwN0GZFU1pKlHw+R+iuUAe5RhphjdWEXVmltxlbi+KXJinBBVZ250idtz/n6atAu5wWqP4Sm6ucsy8hJjVxqm5wtCdTUZa+A8g+z9Jj7eyKYdTbbr+eOaN3yLNDIGCnKwLQj3s/hqIV8TgFEN7FpNpR/vHVd92cmLPTxv5mshJRNrLhSZDnnUgaOfRAqkqQBSn6RPqrefQUiaxhbd+d6mXisAMqOdqlCuRPPESwgly4A0cUR3sZU393iZrUgAee8D3dyuTN8mGKaoau48c8Hf51LrO5rREvkmoQ/o3LXXY+r X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:PSAPR04MB5516.apcprd04.prod.outlook.com; PTR:; CAT:NONE; SFS:(13230025)(4636009)(346002)(376002)(396003)(136003)(39860400002)(366004)(451199018)(52536014)(8936002)(41300700001)(5660300002)(55016003)(33656002)(86362001)(38070700005)(122000001)(38100700002)(2906002)(166002)(966005)(83380400001)(478600001)(71200400001)(7696005)(9686003)(55236004)(186003)(26005)(6506007)(53546011)(3480700007)(110136005)(316002)(8676002)(76116006)(66946007)(64756008)(66476007)(66446008)(66556008); DIR:OUT; SFP:1101; Content-Type: multipart/alternative; boundary="_000_PSAPR04MB551693A1B11CAFCD63D2A039D6819PSAPR04MB5516apcp_" MIME-Version: 1.0 X-MS-Exchange-Transport-CrossTenantHeadersStamped: PSAPR04MB4264 Original-Authentication-Results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=tatacommunications.com; X-SHN-DLP-SCAN: success X-EOPAttributedMessage: 0 X-MS-Exchange-Transport-CrossTenantHeadersStripped: TYZAPC01FT022.eop-APC01.prod.protection.outlook.com X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id-Prvs: 6eb88ef4-ec2b-4ed3-cda5-08db29ca9742 X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: 8IXmfuA1aLwfomZsFsYvjFGrEVnC7WSj58IrSlWOHJ7aQYCMqTCgxsAWU3AuZO59GdsaKzVYt40RRuZocXmjF+TWsTeaSkiwuxaldlQbVqvs+36cbG7/pp/RFZrWQXuZch1/pxu/zyE6cKTlGe0wDVHAQ1cJWrS2D3U67D5le5ZqP3B09xspoGm2jAAFYxi1qIaYBC3B9AqrsFgSpjBZGtBEpnapKe861rMzsvqZqRieUeWtTCMX5cBuQPuY7TfUCQ2VOQ0veEkTjMfixVt417VGsysRvY5Vy1XOHtpJWiQF8YLURjVqvPfQs5nFMuO/Cex1+VryUxihWnpxY8tUxJmmUb+XaJZWCKQCE/70spVv0MXxCCK8dCprqA7+OAqdA6gt0ezVuK0edfqBZqrRJdUvD3RQk7VKCngrY88ETJuehhbYzVzH3zKFohyiSxmoW/3EgEB+ZCDCgYr4YiTK40CqQbCtpJuKrozYHjOQf41/JeV2g5V54j922Nx/L5/5zaawG24UlNjnIh60gfzLLSQ78Yk7lbxhZNWY6B/zgkLknl94n5VDaj34P+7DiKY5hvrUbyTNaA1//hVU/4D8jHhWa3pNXGfe2KYGkd9V87rEEl8uIaHt793U/l+Yu0kOTrpcoRl8OmW7VoEVVkpCmJ+Wwfugw6F5hnN+la5k8fsc54jiFSh0i8tcVT8yuUAi X-Forefront-Antispam-Report: CIP:54.79.123.149; CTRY:AU; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:sydapipop-haraka-inline01.vpc-a3a96cc4.ase2.shn; PTR:send1.mail-inline.syd-pop.i-shn.net; CAT:NONE; SFS:(13230025)(4636009)(136003)(39860400002)(396003)(346002)(376002)(451199018)(36840700001)(46966006)(40470700004)(52536014)(8936002)(5660300002)(41300700001)(36860700001)(40480700001)(55016003)(356005)(82310400005)(33656002)(86362001)(40460700003)(82740400003)(81166007)(2906002)(166002)(6506007)(45080400002)(336012)(83380400001)(966005)(47076005)(7696005)(478600001)(186003)(9686003)(53546011)(110136005)(3480700007)(26005)(70206006)(316002)(70586007)(8676002); DIR:OUT; SFP:1101; X-OriginatorOrg: tatacommunications.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Mar 2023 05:10:36.3314 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: df6624ef-aa99-4e03-9268-08db29ca9b50 X-MS-Exchange-CrossTenant-Id: 20210462-2c5e-4ec8-b3e2-0be950f292ca X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=20210462-2c5e-4ec8-b3e2-0be950f292ca; Ip=[54.79.123.149]; Helo=[sydapipop-haraka-inline01.vpc-a3a96cc4.ase2.shn] X-MS-Exchange-CrossTenant-AuthSource: TYZAPC01FT022.eop-APC01.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: SEYPR04MB5715 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --_000_PSAPR04MB551693A1B11CAFCD63D2A039D6819PSAPR04MB5516apcp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi volodymyr, I checked the app/test/test_reorder.c code. Could you please provide some clarification on below queries: Reorder library ensure packet goes out in the same order they are received = in RX? Sequence number in the mbuf decides the packet index in buffer? Is the reorder works based on the sequence number that we insert in mbuf no= t based on the sequence number present in the packet header? Sequence number should be incremental ? In my use case TCP packets are coming in out of order to the RX itself , ho= w can I use the reorder library to fix the ordering while sending out. TCP sequence number cannot be incremental , sequence number will be decide = based on the number bytes transferred . Thanks , Bala From: Balakrishnan K Sent: Monday, March 20, 2023 5:24 PM To: Volodymyr Fialko ; users@dpdk.org Subject: Re: Reg.dpdk reorder library usage Hi volodymyr, Thanks for the quick response. Let me go through the test code and come back if i need any clarifications. Thanks, Bala ________________________________ From: Volodymyr Fialko > Sent: Monday, March 20, 2023, 4:50 PM To: Balakrishnan K >; users@dpdk.org > Subject: RE: Reg.dpdk reorder library usage CAUTION: This email originated from outside of the organization. Do not cli= ck links or open attachments unless you recognize the sender and know the c= ontent is safe. 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 descri= be the internal state of buffers, which could be helpful during debugging. From: Balakrishnan K > Sent: Monday, March 20, 2023 11:54 AM To: users@dpdk.org Cc: Volodymyr Fialko > 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 existin= g buffer. 3.iterate through the rx packets and set the sequence number using *rte_reo= rder_seqn(pkt) =3D 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 reorde= r 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 app= lication example page. https://doc.dpdk.org/guides/sample_app_ug/packet_ordering.html Regards, Bala --_000_PSAPR04MB551693A1B11CAFCD63D2A039D6819PSAPR04MB5516apcp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi volodymyr,

 &nb= sp;    I checked the app/test/test_reorder.c code.

 

Could you please provide some clarification on below= queries:

Reorder library ensure packet goes out in the same o= rder they are received in RX?

Sequence number in the mbuf decides the packet index= in buffer?

Is the reorder works based on the sequence number th= at we insert in mbuf not based on the sequence number present in the packet= header?

Sequence number should be incremental ?

 

In my use case TCP packets are coming in out of orde= r to the RX itself , how can I use the reorder library to fix the ordering = while sending out.

TCP sequence number cannot be incremental , sequence= number will be decide based on the number bytes transferred .

 

 

Thanks ,

Bala

&nbs= p;

&nbs= p;

From: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>
Sent: Monday, March 20, 2023 5:24 PM
To: Volodymyr Fialko <vfialko@marvell.com>; users@dpdk.org
Subject: Re: Reg.dpdk reorder library usage

 

Hi volodymyr,

  Thanks for the quick response.

Let me go through the test code and come back if i n= eed any clarifications.

 

Thanks,
Bala

 

From: Volodymyr Fialko <vfialko@marvell.com>
Sent: Monday, March 20, 2023, 4:50 PM
To: Balakrishnan K <Balakrishnan.K1@tatacommunications.com>; users@dpdk.org <users@dpdk.org>
Subject:= RE: Reg.dpdk reorder library usage

 

CAUTION: This email = originated from outside of the organization. Do not click links or open att= achments unless you recognize the sender and know the content is safe.

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 descri= be the internal state of buffers, which could be helpful during debugging.<= o:p>

 

From: Balakrishnan K <Balakrishnan.K1@tatacommunications.co= m>
Sent: Monday, March 20, 2023 11:54 AM
To: users@dpdk.org
Cc: Volodymyr Fialko <vfia= lko@marvell.com>
Subject: [EXT] Reg.dpdk reorder library usage

 

External = Email

Hi All,

     I am planning to use dpdk r= eorder 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 alr= eady or use the existing buffer.

3.iterate through the rx packets and set the sequenc= e number using *rte_reorder_seqn(pkt) =3D seqn++.

4.insert the packets using the API rte_reorder_inser= t(ro_buf, pkt);

5.after insert completed I am using rte_reorder_drai= n API to get the reorder packets .

 

In step 5 always getting zero packets.

Even though all the rx packets are in order rte_reod= er_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 port= s .

Sent traffic in port 1 there is no packet out in por= t 1 as mentioned in application example page.

https://doc.dpdk.org/guides/sample_app_u= g/packet_ordering.html

 

 

Regards,

Bala

 

--_000_PSAPR04MB551693A1B11CAFCD63D2A039D6819PSAPR04MB5516apcp_--