From: David Marchand <david.marchand@redhat.com>
To: Kai Ji <kai.ji@intel.com>
Cc: dev <dev@dpdk.org>, Fan Zhang <roy.fan.zhang@intel.com>,
Akhil Goyal <gakhil@marvell.com>
Subject: Re: [dpdk-dev] crypto/qat: fix process type handling
Date: Tue, 1 Mar 2022 09:00:51 +0100 [thread overview]
Message-ID: <CAJFAV8yvMqaRpA5C9dEtahrcfRf-ivdHVoWRv5Bv6z-thy-BTw@mail.gmail.com> (raw)
In-Reply-To: <20220228173639.51393-1-kai.ji@intel.com>
On Mon, Feb 28, 2022 at 6:36 PM Kai Ji <kai.ji@intel.com> wrote:
>
> This patch fix the process type handling in QAT PMDs where
> only primary and secondary process are supported in qat
> build request
>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> ---
> drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c | 3 +++
> drivers/crypto/qat/dev/qat_crypto_pmd_gen4.c | 3 +++
> drivers/crypto/qat/dev/qat_sym_pmd_gen1.c | 3 +++
> drivers/crypto/qat/qat_sym.c | 8 ++++----
> 4 files changed, 13 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c b/drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c
> index 5084a5fcd1..739404b1d4 100644
> --- a/drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c
> +++ b/drivers/crypto/qat/dev/qat_crypto_pmd_gen3.c
> @@ -358,6 +358,9 @@ qat_sym_crypto_set_session_gen3(void *cdev __rte_unused, void *session)
> enum rte_proc_type_t proc_type = rte_eal_process_type();
> int ret;
>
> + if (proc_type < 0 || proc_type == RTE_PROC_INVALID)
> + return -EINVAL;
This is not supposed to happen after rte_eal_init() is called.
I have a doubt on Windows init because I can't see where
rte_config.process_type is initialised.
Are you seeing this issue on Windows?
In any case, the commitlog needs more explanation.
--
David Marchand
next prev parent reply other threads:[~2022-03-01 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 17:36 Kai Ji
2022-03-01 8:00 ` David Marchand [this message]
2022-03-01 10:51 ` Ji, Kai
2022-03-01 15:02 ` [dpdk-dev v2] " Kai Ji
2022-03-04 10:29 ` [EXT] " 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=CAJFAV8yvMqaRpA5C9dEtahrcfRf-ivdHVoWRv5Bv6z-thy-BTw@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=roy.fan.zhang@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).