From: Ido Goshen <Ido@cgstowernetworks.com>
To: "users@dpdk.org" <users@dpdk.org>
Cc: "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>
Subject: Does ACL support field size of 8 bytes?
Date: Wed, 13 Apr 2022 13:55:39 +0000 [thread overview]
Message-ID: <AS4PR09MB5525D74A4559B241F03BB981D6EC9@AS4PR09MB5525.eurprd09.prod.outlook.com> (raw)
Hi
I've lots of good experience with ACL but can't make it work with u64 values
I know it can be split to 2xu32 fields, but it makes it more complex to use and a wastes double number of fields (we hit the RTE_ACL_MAX_FIELDS 64 limit)
According to the documentation and rte_acl.h fields size can be 8 bytes (u64)
e.g.
'The size parameter defines the length of the field in bytes. Allowable values are 1, 2, 4, or 8 bytes.'
(from https://doc.dpdk.org/guides-21.11/prog_guide/packet_classif_access_ctrl.html#rule-definition)
Though there's a hint it's less recommended
'Also, it is best to define fields of 8 or more bytes as 4 byte fields so that the build processes can eliminate fields that are all wild.'
It's also not clear how it fits in a group (i.e. what's input_index stride) which is only 4 bytes
'All subsequent fields has to be grouped into sets of 4 consecutive bytes.'
I couldn't find any example or test app that's using 8 bytes
e.g. for IPv6 address 4xu32 fields are always used and not 2xu64
Should it work?
Did anyone try it successfully and/or can share an example?
Thanx,
- Ido
next reply other threads:[~2022-04-13 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 13:55 Ido Goshen [this message]
2022-04-26 17:56 ` Ananyev, Konstantin
2022-04-26 17:58 ` Fwd: " Konstantin Ananyev
2022-05-11 14:28 ` Ido Goshen
2022-05-15 20:53 ` Konstantin Ananyev
2022-05-16 6:28 ` Ido Goshen
2022-05-17 23:43 ` Konstantin Ananyev
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=AS4PR09MB5525D74A4559B241F03BB981D6EC9@AS4PR09MB5525.eurprd09.prod.outlook.com \
--to=ido@cgstowernetworks.com \
--cc=konstantin.ananyev@intel.com \
--cc=users@dpdk.org \
/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).