From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/crypto-perf: fix crypto op init
Date: Mon, 6 Nov 2017 11:59:01 +0000 [thread overview]
Message-ID: <9F7182E3F746AB4EA17801C148F3C6043304F07D@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20171106093604.1463-1-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Monday, November 6, 2017 9:36 AM
> To: Doherty, Declan <declan.doherty@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH] app/crypto-perf: fix crypto op init
>
> The mempool and the physical address of the crypto operation at mempool
> initialization were not being set, leading to incorrect physical addresses.
>
> Fixes: bf9d6702eca9 ("app/crypto-perf: use single mempool")
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
> app/test-crypto-perf/cperf_test_common.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/app/test-crypto-perf/cperf_test_common.c b/app/test-crypto-
> perf/cperf_test_common.c
> index 46e4a46..7180bb9 100644
> --- a/app/test-crypto-perf/cperf_test_common.c
> +++ b/app/test-crypto-perf/cperf_test_common.c
> @@ -119,6 +119,8 @@ mempool_obj_init(struct rte_mempool *mp,
> op->type = RTE_CRYPTO_OP_TYPE_SYMMETRIC;
> op->status = RTE_CRYPTO_OP_STATUS_NOT_PROCESSED;
> op->sess_type = RTE_CRYPTO_OP_WITH_SESSION;
> + op->phys_addr = rte_mem_virt2phy(obj);
> + op->mempool = mp;
>
> /* Set source buffer */
> op->sym->m_src = m;
> --
> 2.9.4
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2017-11-06 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 9:36 Pablo de Lara
2017-11-06 11:59 ` Zhang, Roy Fan [this message]
2017-11-07 7:25 ` Ferruh Yigit
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=9F7182E3F746AB4EA17801C148F3C6043304F07D@IRSMSX101.ger.corp.intel.com \
--to=roy.fan.zhang@intel.com \
--cc=declan.doherty@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).