DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Arek Kusztal <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5 3/3] drivers/qat: add handling of capabilities in multi process
Date: Tue, 7 Jul 2020 22:28:46 +0000	[thread overview]
Message-ID: <VI1PR04MB3168F7E42CE5AEB096F4A70EE6660@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200707150239.13400-4-arkadiuszx.kusztal@intel.com>


> Move qat capabilities data into a memzone where it can be
> shared by primary and secondary processes.
> 
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>
> ---

Series Applied to dpdk-next-crypto

Fixed following check patch warning while applying the patchset.

diff --git a/drivers/crypto/qat/qat_sym_pmd.c b/drivers/crypto/qat/qat_sym_pmd.c
index 2dcda4a06..f6f9f5bdd 100644
--- a/drivers/crypto/qat/qat_sym_pmd.c
+++ b/drivers/crypto/qat/qat_sym_pmd.c
@@ -435,18 +435,18 @@ qat_sym_dev_create(struct qat_pci_device *qat_pci_dev,

        internals->capa_mz = rte_memzone_lookup(capa_memz_name);
        if (internals->capa_mz == NULL) {
-       internals->capa_mz = rte_memzone_reserve(capa_memz_name,
+               internals->capa_mz = rte_memzone_reserve(capa_memz_name,
                capa_size,
                rte_socket_id(), 0);
        }
        if (internals->capa_mz == NULL) {
-       QAT_LOG(DEBUG,
-               "Error allocating memzone for capabilities, destroying PMD for %s",
-               name);
-       rte_cryptodev_pmd_destroy(cryptodev);
-       memset(&qat_dev_instance->sym_rte_dev, 0,
-               sizeof(qat_dev_instance->sym_rte_dev));
-       return -EFAULT;
+               QAT_LOG(DEBUG,
+                       "Error allocating memzone for capabilities, destroying PMD for %s",
+                       name);
+               rte_cryptodev_pmd_destroy(cryptodev);
+               memset(&qat_dev_instance->sym_rte_dev, 0,
+                       sizeof(qat_dev_instance->sym_rte_dev));
+               return -EFAULT;
        }


  reply	other threads:[~2020-07-07 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 15:02 [dpdk-dev] [PATCH v5 0/3] drivers/qat: improve handling of " Arek Kusztal
2020-07-07 15:02 ` [dpdk-dev] [PATCH v5 1/3] " Arek Kusztal
2020-07-07 15:02 ` [dpdk-dev] [PATCH v5 2/3] drivers/qat: add multi process handling of driver id Arek Kusztal
2020-07-07 15:02 ` [dpdk-dev] [PATCH v5 3/3] drivers/qat: add handling of capabilities in multi process Arek Kusztal
2020-07-07 22:28   ` Akhil Goyal [this message]
2020-07-07 15:28 ` [dpdk-dev] [PATCH v5 0/3] drivers/qat: improve handling of " Trahe, Fiona

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=VI1PR04MB3168F7E42CE5AEB096F4A70EE6660@VI1PR04MB3168.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@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).