From: Akhil Goyal <akhil.goyal@nxp.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>, pablo.de.lara.guarch@intel.com
Cc: akhil.goyal@nxp.com, dev@dpdk.org,
Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/dpaa2_sec: remove iova conversion for fle address
Date: Wed, 9 May 2018 14:44:08 +0530 [thread overview]
Message-ID: <ca1fb35f-cdae-58b0-f566-aac579509377@nxp.com> (raw)
In-Reply-To: <20180509092642.9092-1-shreyansh.jain@nxp.com>
On 5/9/2018 2:56 PM, Shreyansh Jain wrote:
> From: Hemant Agrawal <hemant.agrawal@nxp.com>
>
> fle is already in virtual addressing mode - no need to perform
> address conversion for it.
>
> Fixes: 8d1f3a5d751b ("crypto/dpaa2_sec: support crypto operation")
> Cc: akhil.goyal@nxp.com
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> index 58cbce868..56fa969d3 100644
> --- a/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> +++ b/drivers/crypto/dpaa2_sec/dpaa2_sec_dpseci.c
> @@ -1261,8 +1261,7 @@ sec_fd_to_mbuf(const struct qbman_fd *fd, uint8_t driver_id)
> DPAA2_SEC_ERR("error: non inline buffer");
> return NULL;
> }
> - op = (struct rte_crypto_op *)DPAA2_IOVA_TO_VADDR(
> - DPAA2_GET_FLE_ADDR((fle - 1)));
> + op = (struct rte_crypto_op *)DPAA2_GET_FLE_ADDR((fle - 1));
>
> /* Prefeth op */
> src = op->sym->m_src;
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2018-05-09 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 9:26 Shreyansh Jain
2018-05-09 9:14 ` Akhil Goyal [this message]
2018-05-09 10:24 ` De Lara Guarch, Pablo
2018-05-09 11:39 ` Shreyansh Jain
2018-05-09 11:30 ` De Lara Guarch, Pablo
2018-05-09 12:29 ` Shreyansh Jain
2018-05-09 12:46 ` Shreyansh Jain
2018-05-09 12:43 ` [dpdk-dev] [PATCH v2] " Shreyansh Jain
2018-05-09 14:35 ` 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=ca1fb35f-cdae-58b0-f566-aac579509377@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=shreyansh.jain@nxp.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).