From: Akhil Goyal <akhil.goyal@nxp.com>
To: Anoob Joseph <anoobj@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "declan.doherty@intel.com" <declan.doherty@intel.com>,
"konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH v2] crypto/openssl: support SG for inplace buffers
Date: Wed, 20 Nov 2019 06:11:48 +0000 [thread overview]
Message-ID: <VE1PR04MB6639808665CACB8EE9CB07DBE64F0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <MN2PR18MB28779BA7B1485D158B8E87A6DF4F0@MN2PR18MB2877.namprd18.prod.outlook.com>
> > static inline int
> > process_openssl_decryption_update(struct rte_mbuf *mbuf_src, int offset,
> > - uint8_t **dst, int srclen, EVP_CIPHER_CTX *ctx)
> > + uint8_t **dst, int srclen, EVP_CIPHER_CTX *ctx, uint8_t inplace)
> > {
> > struct rte_mbuf *m;
> > int dstlen;
> > int l, n = srclen;
> > - uint8_t *src;
> > + uint8_t *src, temp[128];
>
> [Anoob] In case of encrypt_update, the buffer is
> 'temp[EVP_CIPHER_CTX_block_size(ctx)]'. Is the above intentional?
>
Sending a v3
next prev parent reply other threads:[~2019-11-20 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 12:42 [dpdk-dev] [PATCH] " Akhil Goyal
2019-09-13 5:58 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-09-19 15:57 ` Akhil Goyal
2019-11-18 13:36 ` [dpdk-dev] [PATCH v2] " Akhil Goyal
2019-11-19 14:19 ` Akhil Goyal
2019-11-20 4:31 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-11-20 6:11 ` Akhil Goyal [this message]
2019-11-20 5:58 ` [dpdk-dev] [PATCH v3] " Akhil Goyal
2019-11-20 6:23 ` Anoob Joseph
2019-11-20 11:50 ` Akhil Goyal
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=VE1PR04MB6639808665CACB8EE9CB07DBE64F0@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@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).