All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: yoursunny <sunnylandh@gmail.com>
Cc: Junxiao Shi <git@mail1.yoursunny.com>, dev@dpdk.org
Subject: Re: [PATCH] crypto: recognize OP_TYPE_UNDEFINED in rte_crypto_op_pool_create
Date: Tue, 9 Oct 2018 16:41:40 +0530	[thread overview]
Message-ID: <9e19271f-714f-514d-4d0f-096f553654f3@nxp.com> (raw)
In-Reply-To: <CANsAqf5BD+FohUT_-mGRM6ZzN9FtS7oWvH8UFJ6vGc7X2bACKw@mail.gmail.com>



On 10/9/2018 4:28 PM, yoursunny wrote:
> Hi Akhil
>
> The documentation of rte_crypto_op_pool_create indicates that _UNDEFINED
> creates a pool that supports both symmetric and assymetric crypto. This
> change makes the code consistent with documentation.
>
> Yours, Junxiao
Please add this information in the patch description and this should be 
marked as a fix.

Please also add
Fixes: c0f87eb5252b ("cryptodev: change burst API to be crypto op oriented")

and cc stable@dpdk.org
> On Tue, Oct 9, 2018 at 06:51 Akhil Goyal <akhil.goyal@nxp.com> wrote:
>
>> Hi  Junxiao,
>>
>> On 10/3/2018 12:35 AM, Junxiao Shi wrote:
>>> Signed-off-by: Junxiao Shi <git@mail1.yoursunny.com>
>>> ---
>>>    lib/librte_cryptodev/rte_cryptodev.c | 2 ++
>>>    1 file changed, 2 insertions(+)
>>>
>>> diff --git a/lib/librte_cryptodev/rte_cryptodev.c
>> b/lib/librte_cryptodev/rte_cryptodev.c
>>> index 63ae23f..3d6f474 100644
>>> --- a/lib/librte_cryptodev/rte_cryptodev.c
>>> +++ b/lib/librte_cryptodev/rte_cryptodev.c
>>> @@ -1477,6 +1477,8 @@ rte_crypto_op_pool_create(const char *name, enum
>> rte_crypto_op_type type,
>>>                elt_size += sizeof(struct rte_crypto_sym_op);
>>>        } else if (type == RTE_CRYPTO_OP_TYPE_ASYMMETRIC) {
>>>                elt_size += sizeof(struct rte_crypto_asym_op);
>>> +     } else if (type == RTE_CRYPTO_OP_TYPE_UNDEFINED) {
>>> +             elt_size += RTE_MAX(sizeof(struct rte_crypto_sym_op),
>> sizeof(struct rte_crypto_asym_op));
>>>        } else {
>>>                CDEV_LOG_ERR("Invalid op_type\n");
>>>                return NULL;
>> Could you please explain the need for this change. If there is some type
>> which is missing, we can add that.
>> defining the size of undefined op type does not make sense.
>>
>> -Akhil
>>

  reply	other threads:[~2018-10-09 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 19:05 [PATCH] crypto: recognize OP_TYPE_UNDEFINED in rte_crypto_op_pool_create Junxiao Shi
2018-10-09 10:50 ` Akhil Goyal
2018-10-09 10:58   ` yoursunny
2018-10-09 11:11     ` Akhil Goyal [this message]
2018-10-09 12:51       ` Akhil Goyal
2018-10-02 19:05 Junxiao Shi

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=9e19271f-714f-514d-4d0f-096f553654f3@nxp.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=git@mail1.yoursunny.com \
    --cc=sunnylandh@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.