DPDK usage discussions
 help / color / mirror / Atom feed
From: Ido Goshen <Ido@cgstowernetworks.com>
To: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: Does ACL support field size of 8 bytes?
Date: Mon, 16 May 2022 06:28:20 +0000	[thread overview]
Message-ID: <AM0PR09MB3972D15DAE506D6E758B62EFD6CF9@AM0PR09MB3972.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <59727248-59ac-ab74-5ac3-e6eb7163647e@yandex.ru>

> -----Original Message-----
> From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
> Sent: Sunday, 15 May 2022 23:54
> To: Ido Goshen <Ido@cgstowernetworks.com>; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; users@dpdk.org; dev@dpdk.org
> Subject: Re: Does ACL support field size of 8 bytes?
> 
> 
> My concern was it is sort of awkward in terms of input_field value for rules with
> 8B long.

[idog] I'm always puzzled with the input_index field. 
I just randomly group the small size fields (u8, u16) without any applicative meaning.
Feels like it's redundant in the API an can be done internally by the lib like you do now for u64  
(though it'll be less trivial to do) 


  reply	other threads:[~2022-05-16  6:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 13:55 Ido Goshen
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 [this message]
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=AM0PR09MB3972D15DAE506D6E758B62EFD6CF9@AM0PR09MB3972.eurprd09.prod.outlook.com \
    --to=ido@cgstowernetworks.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --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).