DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Gagandeep Singh <G.Singh@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Gagandeep Singh <G.Singh@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/dpaa_sec: fix performance issue
Date: Tue, 28 Jan 2020 06:16:19 +0000	[thread overview]
Message-ID: <VE1PR04MB6639A13F6731DCA0498C730BE60A0@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200127090724.1667-1-g.singh@nxp.com>

> 
> DPAA sec driver is using virtual to physical address
> translation in its data path and driver is using
> dpaax_iova_table_update() API in every address translation
> which is very costly.
> This patch moves dpaax_iova_table_update() calling to rte_dpaa_mem_ptov(),
> only if it fails to found translation from DPAAX table.
> 
> Fixes: 033968bdc28 ("drivers/crypto/dpaa_sec: update DPAA iova table in
> dpaa_mem_vtop")
> Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
> ---
Series
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>

From next time, please update the version of the updated patch in title
And specify change log after '---'

Series applied to dpdk-next-crypto

Thanks.


      parent reply	other threads:[~2020-01-28  6:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 10:45 Gagandeep Singh
2020-01-21 10:45 ` [dpdk-dev] [PATCH 2/2] crypto/dpaa_sec: reorganize structure members Gagandeep Singh
2020-01-27  9:07 ` [dpdk-dev] [PATCH 1/2] crypto/dpaa_sec: fix performance issue Gagandeep Singh
2020-01-27  9:07   ` [dpdk-dev] [PATCH 2/2] crypto/dpaa_sec: reorganize structure members Gagandeep Singh
2020-01-28  6:16   ` Akhil Goyal [this message]

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=VE1PR04MB6639A13F6731DCA0498C730BE60A0@VE1PR04MB6639.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=G.Singh@nxp.com \
    --cc=dev@dpdk.org \
    /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).