From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/8] Remove temporary digest allocation
Date: Tue, 5 Sep 2017 12:38:56 +0000 [thread overview]
Message-ID: <9F7182E3F746AB4EA17801C148F3C60433038C6F@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20170905022007.55749-1-pablo.de.lara.guarch@intel.com>
Hi Pablo,
Thanks, looks great!
Regards,
Fan
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Tuesday, September 5, 2017 3:20 AM
> To: Doherty, Declan <declan.doherty@intel.com>; Zhang, Roy Fan
> <roy.fan.zhang@intel.com>; jerin.jacob@caviumnetworks.com
> Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [PATCH v2 0/8] Remove temporary digest allocation
>
> When performing authentication verification, some crypto PMDs require
> extra memory where the generated digest can be placed.
> Currently, these PMDs are getting the memory from the end of the source
> mbuf, which might fail if there is not enough tailroom.
>
> To avoid this situation, some memory is allocated in each queue pair of the
> device, to store temporarily these digests.
>
> Changes in v2:
> - Removed incorrect indirection when getting the memory
> to store the generated digest (i.e. removed "&" in &temp_digest)
Series Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2017-09-05 12:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 7:20 [dpdk-dev] [PATCH " Pablo de Lara
2017-08-18 7:20 ` [dpdk-dev] [PATCH 1/8] crypto/aesni_gcm: do not append digest Pablo de Lara
2017-09-04 10:07 ` Zhang, Roy Fan
2017-09-05 8:49 ` De Lara Guarch, Pablo
2017-08-18 7:20 ` [dpdk-dev] [PATCH 2/8] crypto/armv8: " Pablo de Lara
2017-09-11 5:22 ` Jerin Jacob
2017-08-18 7:20 ` [dpdk-dev] [PATCH 3/8] crypto/openssl: " Pablo de Lara
2017-08-18 7:20 ` [dpdk-dev] [PATCH 4/8] crypto/kasumi: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 5/8] crypto/snow3g: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 6/8] crypto/zuc: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 7/8] crypto/aesni_mb: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 8/8] test/crypto: do not allocate extra memory for digest Pablo de Lara
2017-09-05 2:19 ` [dpdk-dev] [PATCH v2 0/8] Remove temporary digest allocation Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 1/8] crypto/aesni_gcm: do not append digest Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 2/8] crypto/armv8: " Pablo de Lara
2017-09-06 9:02 ` De Lara Guarch, Pablo
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 3/8] crypto/openssl: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 4/8] crypto/kasumi: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 5/8] crypto/snow3g: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 6/8] crypto/zuc: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 7/8] crypto/aesni_mb: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 8/8] test/crypto: do not allocate extra memory for digest Pablo de Lara
2017-09-05 12:38 ` Zhang, Roy Fan [this message]
2017-09-11 9:39 ` [dpdk-dev] [PATCH v2 0/8] Remove temporary digest allocation De Lara Guarch, Pablo
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=9F7182E3F746AB4EA17801C148F3C60433038C6F@IRSMSX101.ger.corp.intel.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@intel.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).