From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Ori Kam <orika@nvidia.com>,
"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
"cristian.dumitrescu@intel.com" <cristian.dumitrescu@intel.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [RFC] ethdev: introduce entropy calculation
Date: Tue, 12 Dec 2023 12:19:57 +0000 [thread overview]
Message-ID: <IA1PR12MB8311ECF66177A0C208480F8AA48EA@IA1PR12MB8311.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231210083100.7893-1-orika@nvidia.com>
> Subject: [RFC] ethdev: introduce entropy calculation
>
> When offloading rules with the encap action, the HW may calculate entropy
> based on the encap protocol.
> Each HW can implement a different algorithm.
>
> When the application receives packets that should have been encaped by the
> HW, but didn't reach this stage yet (for example TCP SYN packets), then when
> encap is done in SW, application must apply the same entropy calculation
> algorithm.
>
> Using the new API application can request the PMD to calculate the value as if
> the packet passed in the HW.
>
> Signed-off-by: Ori Kam <orika@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2023-12-12 12:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 8:30 Ori Kam
2023-12-12 12:19 ` Dariusz Sosnowski [this message]
2023-12-14 11:34 ` Ferruh Yigit
2023-12-14 14:16 ` Ori Kam
2023-12-14 15:25 ` Dumitrescu, Cristian
2023-12-14 17:18 ` Ori Kam
2023-12-14 17:26 ` Stephen Hemminger
2023-12-15 13:44 ` Ferruh Yigit
2023-12-15 16:21 ` Thomas Monjalon
2023-12-16 9:03 ` Andrew Rybchenko
2023-12-27 15:20 ` Ori Kam
2024-01-04 12:57 ` Dumitrescu, Cristian
2024-01-04 14:33 ` Ori Kam
2024-01-04 18:18 ` Thomas Monjalon
2024-01-07 9:37 ` Ori Kam
2023-12-16 9:19 ` Andrew Rybchenko
2023-12-17 10:07 ` Ori Kam
2024-01-12 7:46 ` Andrew Rybchenko
2024-01-21 9:36 ` Ori Kam
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=IA1PR12MB8311ECF66177A0C208480F8AA48EA@IA1PR12MB8311.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
/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).