DPDK usage discussions
 help / color / mirror / Atom feed
From: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
To: Ido Goshen <Ido@cgstowernetworks.com>,
	"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: Wed, 18 May 2022 00:43:24 +0100
Message-ID: <d0ea310e-b465-4942-8b79-19fe201bc132@yandex.ru> (raw)
In-Reply-To: <AM0PR09MB3972D15DAE506D6E758B62EFD6CF9@AM0PR09MB3972.eurprd09.prod.outlook.com>


>> -----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)
> 

Yep agree, field_index and offset - seems enough,
other stuff can probably be figured out by analyzing these two fields.
Though as you said, it would require some extra effort.

      reply	other threads:[~2022-05-17 23:43 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
2022-05-17 23:43         ` Konstantin Ananyev [this message]

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=d0ea310e-b465-4942-8b79-19fe201bc132@yandex.ru \
    --to=konstantin.v.ananyev@yandex.ru \
    --cc=Ido@cgstowernetworks.com \
    --cc=dev@dpdk.org \
    --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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git