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 BAA42A0551 for ; Thu, 17 Nov 2022 14:58:31 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 49B4F40F18; Thu, 17 Nov 2022 14:58:27 +0100 (CET) Received: from mail-pg1-f182.google.com (mail-pg1-f182.google.com [209.85.215.182]) by mails.dpdk.org (Postfix) with ESMTP id 694BE40DDA; Thu, 17 Nov 2022 14:58:24 +0100 (CET) Received: by mail-pg1-f182.google.com with SMTP id n17so2012019pgh.9; Thu, 17 Nov 2022 05:58:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=7erKxaUlGI9d1WCIaOl68VzoLd4OeYDdvmFcgKx8M7s=; b=dTPsSnIZ0RFQqZznkU3FCN5F2BHBk2TLPTWKh6+oxwBLa9fZdH09jnSF1DSVD0F1Qd bUh70CBLiNwKMXmraYaEkPi0dE/FoVwbVi84Dhl5Ph32kZjkM+w87O7X9HVyk+pNfgGP 4S2F9qGfiTPb6KTOnJbrEgksNZGbD7m6lQEalolWrOHSMd+wHeXzRDiuqxdAsbu1nhgl pxZKVsnVIjAiQGelVfKC+Lo837ZAAXYOw8qNFD0XvdzloHL7s7nYJGXSrxGyAX0F1PxZ NXPWRldQJNRlM8slBrgIdkSWwbDJjIgdtQKa55OzzctG1PoiWZ23ftRRzHrwjVTy4zBk JsfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=7erKxaUlGI9d1WCIaOl68VzoLd4OeYDdvmFcgKx8M7s=; b=MyZ4mCktUl3sya0Ukf/+PimQ8+xZ5J0gcu1v9oVO8K013Xl2Nd3iYqr1i19uKx8UdS OhDsXQgBzAI0eKBfQqv9XYmkeyqydKY9w12TlFM6YYyCMkOGsg9g9PxHmZfE9iHTPGM9 D7lBXauXSQDFPYV1Ene3kZqz8lB/eqw5o1Kt8bRd9tOvwUC1zW9fpcXca4B6hROgabFQ QKeCUGJv9/LG/butzJHIvv+dfmD6Kw4R829KsnQFtwYk3Rjyjbx/0o8SoFl8LP8YsS5L rljAEZNVQTeKkIRuiIoRHWfHl6jRX3RCS6SXt5B/yb/hOJsi+6CHOz4GkU3L2G59Ldem GjMw== X-Gm-Message-State: ANoB5pkgGLKZzsA4JnB/q2vS6zp1RFdogLmpChiPHdXEB9Vl3ZhAokye T34qb2E4HwTiqmr0NggikuaQ5BlgFK794EwXdNhbiZGaj9szUw== X-Google-Smtp-Source: AA0mqf5qPuHPYkhqfXOCqr/9b8gIksIMgSp4c9NGi0WSb/ML+8p2UB3y+U1m1ukY6vEOiqu5a791sREF5jtxgZm6qFE= X-Received: by 2002:a63:451a:0:b0:476:addf:767d with SMTP id s26-20020a63451a000000b00476addf767dmr2170915pga.140.1668693503095; Thu, 17 Nov 2022 05:58:23 -0800 (PST) MIME-Version: 1.0 From: venkatesh bs Date: Thu, 17 Nov 2022 19:28:12 +0530 Message-ID: Subject: Regarding User Data in DPDK ACL Library. To: users@dpdk.org, dev@dpdk.org Content-Type: multipart/alternative; boundary="0000000000007dba5405edaafbf4" 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 --0000000000007dba5405edaafbf4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi DPDK Team, After the ACL match for highest priority DPDK Classification API returns User Data Which is as mentioned below in the document. 53. Packet Classification and Access Control =E2=80=94 Data Plane Developme= nt Kit 22.11.0-rc2 documentation (dpdk.org) - *userdata*: A user-defined value. For each category, a successful match returns the userdata field of the highest priority matched rule. W= hen no rules match, returned value is zero I Wonder Why User Data Support does not returns 64 bit values, Always its possible that User Data in Application Can be 64bit long, But since 64 bit User data can't be returned by DPDK ACL Library, Application should have the conversion algorithm from 64 to 32 bit during Rule add and vice versa after classification. I Wonder if anyone would have faced this issue, Please suggest any suggestions if somewhere am wrong in understanding/Possible Solution if someone has already gone through this issue. Thanks In Advance. Regards, Venkatesh B Siddappa. --0000000000007dba5405edaafbf4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi DPDK Team,

After the ACL match for h= ighest priority DPDK Classification API returns User Data Which is as menti= oned below in the document.

53. Packet Classification and Access Con= trol =E2=80=94 Data Plane Development Kit 22.11.0-rc2 documentation (dpdk.org)

  • userdata: A user-defined value. For each category, a success= ful match returns the userdata field of the highest priority matched rule. = When no rules match, returned value is zero
I Wonder Wh= y User Data Support does not returns 64 bit values, Always its possible tha= t User Data in Application Can be 64bit long, But since 64 bit User data ca= n't be returned by DPDK ACL Library, Application should have the conver= sion algorithm=C2=A0from 64 to 32 bit during Rule add and vice versa after = classification.

I Wonder if anyone would have face= d this issue, Please suggest any suggestions if somewhere am wrong in under= standing/Possible Solution if someone has already gone through this issue.= =C2=A0=C2=A0

Thanks In=C2=A0Advance.=C2=A0
Regards,
Venkatesh B Siddappa.
--0000000000007dba5405edaafbf4--