From: Stephen Hemminger <stephen@networkplumber.org>
To: venkatesh bs <venki.bsv@gmail.com>
Cc: users@dpdk.org, dev@dpdk.org
Subject: Re: Regarding User Data in DPDK ACL Library.
Date: Thu, 17 Nov 2022 14:52:41 -0800 [thread overview]
Message-ID: <20221117145241.503fd10b@hermes.local> (raw)
In-Reply-To: <CAM3UhOgRGygyoHge1ngLXp+z8seQM43TV1VY+HaY2GWkh+RKLw@mail.gmail.com>
On Thu, 17 Nov 2022 19:28:12 +0530
venkatesh bs <venki.bsv@gmail.com> wrote:
> 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 — Data Plane Development 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. When
> 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.
It looks like all users of this API use the userdata to be the index
into a table of application specific rules.
next prev parent reply other threads:[~2022-11-17 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 13:58 venkatesh bs
2022-11-17 22:52 ` Stephen Hemminger [this message]
2022-11-18 10:30 ` Konstantin Ananyev
2022-11-19 13:13 ` venkatesh bs
2022-11-21 5:40 ` Honnappa Nagarahalli
2022-11-21 14:15 ` Konstantin Ananyev
2022-11-21 16:56 ` Honnappa Nagarahalli
2022-11-22 13:38 ` Konstantin Ananyev
2022-11-22 15:53 ` Honnappa Nagarahalli
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 13:58 venkatesh bs
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=20221117145241.503fd10b@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=users@dpdk.org \
--cc=venki.bsv@gmail.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).