From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Heng Wang <heng.wang@ericsson.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: Filip Pudak <filip.pudak@ericsson.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Coyle, David" <david.coyle@intel.com>
Subject: Re: [dpdk-dev] Offloading L4 checksum to crypto device
Date: Wed, 5 Feb 2020 17:22:46 +0000 [thread overview]
Message-ID: <BN6PR11MB179626E245BA2043A55F109BE4020@BN6PR11MB1796.namprd11.prod.outlook.com> (raw)
In-Reply-To: <AM0PR07MB5396CD719CC621707B026CB29C2E0@AM0PR07MB5396.eurprd07.prod.outlook.com>
Hi Heng,
This may be of interest for your use-case.
https://patches.dpdk.org/patch/65559/
Fiona
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Heng Wang
> Sent: Monday, December 23, 2019 2:28 PM
> To: Doherty, Declan <declan.doherty@intel.com>
> Cc: Filip Pudak <filip.pudak@ericsson.com>; dev@dpdk.org
> Subject: [dpdk-dev] Offloading L4 checksum to crypto device
>
> Hi,
> This is Heng from Ericsson. We are now developing a platform based on dpdk. The platform usually
> processes the ipsec packets encapsulating udp packets.
> You know, calculating udp checksum is always time consuming. We found a hardware solution where
> our crypto device can calculate the udp checksum during encryption.
> Unfortunately, in DPDK, I didn't find any feature flag for it. Also the API rte_cryptodev_configure
> doesn't allow us to pass any offload flag to the crypto device.
> I think this could be a common case to calculate something, like checksums, before encryption in
> crypto devices. Should we consider add some new feature flag and offload support in dpdk crypto
> device?
>
> Regards,
> Heng
next prev parent reply other threads:[~2020-02-05 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 14:27 Heng Wang
2020-02-05 17:22 ` Trahe, Fiona [this message]
2020-02-06 8:02 ` Heng Wang
2020-02-10 2:01 ` Trahe, Fiona
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=BN6PR11MB179626E245BA2043A55F109BE4020@BN6PR11MB1796.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=david.coyle@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=filip.pudak@ericsson.com \
--cc=heng.wang@ericsson.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).