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 D6E26A00C4 for ; Thu, 17 Nov 2022 23:52:51 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E426142C4D; Thu, 17 Nov 2022 23:52:46 +0100 (CET) Received: from mail-pg1-f180.google.com (mail-pg1-f180.google.com [209.85.215.180]) by mails.dpdk.org (Postfix) with ESMTP id B475B40DFB for ; Thu, 17 Nov 2022 23:52:44 +0100 (CET) Received: by mail-pg1-f180.google.com with SMTP id r18so3392294pgr.12 for ; Thu, 17 Nov 2022 14:52:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=VXNRTmIJ4poMSr90eLTqjR7lobIzIhCDTG4ohLag6QY=; b=sjy8urehUZKGT+6i6LKMQvxqWyftz5sjVEdiINCwMrULRsTrCkXTaId1W3pQjb7FMt kb3s3UrE529EyzjHNhLJyHpmyD8QU07gSnuzCGzosTWkxCWPdzrTwc5R1ATgCXkJSZTa /p9kMsKhTb5GwDeVNsiTNpLF27QXQB2vwtSeAxewGeNlTmliVG90LsSBg2uOSgqWsfBg i6gcJgUe1N8ta/Dkn3RBjNvNpfwUw+B6yGCScRKbnRyXTAVHxtMB3crVt879cDoQPkUm 0uB52co2DX3c3mpPOEJF+2otJn73SX973dU/UA/Yg9R2tR8m9udopz0YWQd+ucT2AcK5 FVcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=VXNRTmIJ4poMSr90eLTqjR7lobIzIhCDTG4ohLag6QY=; b=ypnCUZN8Vto7e2kbXYnSIlZnQny67KcaZtOCtsB+bdJ2paB3lP4Js9RAl32603kXSP TCTNS0vvN6Vcn2bjx1n1AxHGBUYYwPf+63xrP/g1nlRCZ4+de0m0cGv8L/oVyl9g18dC l/nqJUf6noz2br7x4HZpHEGVgRrdSfyaKOK/Acy3GhXZMFsbTaX9eYP+T2/RIhcZCf44 CQp5h3xxIzs/bvB81xZ+p5RcuHMWYGDk+itnJd2qKC0PGQhkqILsKFk7kakHES6nt37O pwUM8sxTSAdsOolChGNIZ5X0jCWU3IHeBRVcW7VmzOy2rPPik1MqZQBja3NJFBzcBlpy de6g== X-Gm-Message-State: ANoB5pnYHxss0X7gQ/sAt9a532nP+ffVfO22l+3H8W789McRgDor/7nj DfXab9M03OtNWzQhITp7IUTC1w== X-Google-Smtp-Source: AA0mqf7w3IL4kpjcRe9ajUhBgIQXIbhwdaoXcktXJxn5bITVhyQ1yvkXRa2KlnYM4PtH82XsG482qA== X-Received: by 2002:a63:5114:0:b0:476:a62d:9fe with SMTP id f20-20020a635114000000b00476a62d09femr4077537pgb.162.1668725563691; Thu, 17 Nov 2022 14:52:43 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id t15-20020a170902b20f00b00188ef2314b0sm1945625plr.39.2022.11.17.14.52.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 17 Nov 2022 14:52:43 -0800 (PST) Date: Thu, 17 Nov 2022 14:52:41 -0800 From: Stephen Hemminger To: venkatesh bs Cc: users@dpdk.org, dev@dpdk.org Subject: Re: Regarding User Data in DPDK ACL Library. Message-ID: <20221117145241.503fd10b@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 On Thu, 17 Nov 2022 19:28:12 +0530 venkatesh bs wrote: > Hi DPDK Team, >=20 > After the ACL match for highest priority DPDK Classification API returns > User Data Which is as mentioned below in the document. >=20 > 53. Packet Classification and Access Control =E2=80=94 Data Plane Develop= ment Kit > 22.11.0-rc2 documentation (dpdk.org) >=20 >=20 > - *userdata*: A user-defined value. For each category, a successful > match returns the userdata field of the highest priority matched rule.= When > no rules match, returned value is zero >=20 > 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. >=20 > 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. >=20 > Thanks In Advance. > Regards, > Venkatesh B Siddappa. It looks like all users of this API use the userdata to be the index into a table of application specific rules.