DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "shally.verma@caviumnetworks.com"
	<shally.verma@caviumnetworks.com>,
	"sunila.sahu@caviumnetworks.com" <sunila.sahu@caviumnetworks.com>,
	"ashish.gupta@caviumnetworks.com"
	<ashish.gupta@caviumnetworks.com>,
	"umesh.kartha@caviumnetworks.com"
	<umesh.kartha@caviumnetworks.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] cryptodev: rework mod exp and mod inv comments
Date: Tue, 5 Feb 2019 13:02:25 +0000	[thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435896DA2DA@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20190205111319.2104-1-arkadiuszx.kusztal@intel.com>

Hi Arek,

> -----Original Message-----
> From: Kusztal, ArkadiuszX
> Sent: Tuesday, February 5, 2019 11:13 AM
> To: dev@dpdk.org
> Cc: shally.verma@caviumnetworks.com; sunila.sahu@caviumnetworks.com;
> ashish.gupta@caviumnetworks.com; umesh.kartha@caviumnetworks.com; Trahe, Fiona
> <fiona.trahe@intel.com>; akhil.goyal@nxp.com; Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Subject: [PATCH] cryptodev: rework mod exp and mod inv comments
> 
> This patch changes modular exponentiation and modular multiplicative
> inverse API comments to make it more precise.
> 
> Signed-off-by: Arek Kusztal <arkadiuszx.kusztal@intel.com>

> +	 * In case this number is equal to zero driver set crypto op
> +	 * status field to RTE_CRYPTO_OP_STATUS_ERROR
[Fiona] grammar nit - ....the driver should set the crypto op.....

> - * Structure describing modulus inverse xform params
> + * Structure describing modular multiplicative inverse transform xform params
[Fiona] grammar nit - no need for transform and xform - one will do. 

> +	 * In case this number is equal to zero driver set crypto op
> +	 * status field to RTE_CRYPTO_OP_STATUS_ERROR
[Fiona] grammar nit - same comment as above 

> +	 *
> +	 * This number need to be relatively prime to base
> +	 * in corresponding Modular Multiplicative Inverse
> +	 * rte_crypto_mod_op_param
>  	 */
[Fiona] grammar nit - "The number needs..." or "This number should be" 

>  struct rte_crypto_mod_op_param {
>  	rte_crypto_param base;
>  	/**<
> -	 * Pointer to base of modular exponentiation/inversion data in
> -	 * Octet-string network byte order format.
> +	 * Pointer to base of modular exponentiation/multiplicative
> +	 * inverse data in Octet-string network byte order format.
[Fiona] grammar nit - octet-string - no need for capitalisation
> +	 *
> +	 * In case Multiplicative Inverse is used this number need
> +	 * to be relatively prime to modulus in corresponding Modular
> +	 * Multiplicative Inverse rte_crypto_modinv_xform
[Fiona] grammar nit - same comment as above

      reply	other threads:[~2019-02-05 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 11:13 Arek Kusztal
2019-02-05 13:02 ` Trahe, Fiona [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=348A99DA5F5B7549AA880327E580B435896DA2DA@IRSMSX101.ger.corp.intel.com \
    --to=fiona.trahe@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=ashish.gupta@caviumnetworks.com \
    --cc=dev@dpdk.org \
    --cc=shally.verma@caviumnetworks.com \
    --cc=sunila.sahu@caviumnetworks.com \
    --cc=umesh.kartha@caviumnetworks.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).