DPDK patches and discussions
 help / color / mirror / Atom feed
From: Arek Kusztal <arkadiuszx.kusztal@intel.com>
To: dev@dpdk.org
Cc: gakhil@marvell.com, roy.fan.zhang@intel.com,
	Arek Kusztal <arkadiuszx.kusztal@intel.com>
Subject: [PATCH v3 0/4] Clarify asymmetric random, add 'k' and crypto uint
Date: Fri, 11 Feb 2022 16:02:34 +0000	[thread overview]
Message-ID: <20220211160238.90065-1-arkadiuszx.kusztal@intel.com> (raw)

This patchset introduces following changes:

1) DSA 'k' was added that devices without random support can work.
2) Clarified usage of random numbers in asym, as per discussion from December.
3) Added typedef for crypto_uint to remove some repeating comments making code more readable. Additionally, some rearrangement was made to improve readability.

v2:
- added patches justification to each commit
v3:
- add abidiff ignore hint for rte_crypto_asym_op

Arek Kusztal (4):
  crypto: add dsa random number k
  crypto: clarify usage of random numbers in asym
  crypto: use rte macro instead of direct attribute
  crypto: reorganize endianness comments, add crypto uint

 devtools/libabigail.abignore    |   5 +
 lib/cryptodev/rte_crypto_asym.h | 363 ++++++++++++++++------------------------
 2 files changed, 146 insertions(+), 222 deletions(-)

-- 
2.13.6


             reply	other threads:[~2022-02-11 17:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11 16:02 Arek Kusztal [this message]
2022-02-11 16:02 ` [PATCH v3 1/4] crypto: add dsa random number k Arek Kusztal
2022-02-11 16:02 ` [PATCH v3 2/4] crypto: clarify usage of random numbers in asym Arek Kusztal
2022-02-11 16:02 ` [PATCH v3 3/4] crypto: use rte macro instead of direct attribute Arek Kusztal
2022-02-11 16:02 ` [PATCH v3 4/4] crypto: reorganize endianness comments, add crypto uint Arek Kusztal
2022-02-12 10:52 ` [EXT] [PATCH v3 0/4] Clarify asymmetric random, add 'k' and " 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=20220211160238.90065-1-arkadiuszx.kusztal@intel.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.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).