DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "O'loingsigh, Mairtin" <mairtin.oloingsigh@intel.com>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] crypto/qat: support DOCSIS AES-256
Date: Tue, 25 Feb 2020 10:34:19 +0000	[thread overview]
Message-ID: <BN6PR11MB179650E9A20B052EC9142058E4ED0@BN6PR11MB1796.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1582624074-7981-1-git-send-email-mairtin.oloingsigh@intel.com>

Hi Mairtin,

> -----Original Message-----
> From: O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Sent: Tuesday, February 25, 2020 9:48 AM
> To: Trahe, Fiona <fiona.trahe@intel.com>; akhil.goyal@nxp.com
> Cc: dev@dpdk.org; O'loingsigh, Mairtin <mairtin.oloingsigh@intel.com>
> Subject: [PATCH 1/2] crypto/qat: support DOCSIS AES-256
> 
> This patch adds support for DOCSIS AES-256 when using qat
> 
> Signed-off-by: Mairtin o Loingsigh <mairtin.oloingsigh@intel.com>
> ---
>  drivers/crypto/qat/qat_sym_capabilities.h |    2 +-
>  drivers/crypto/qat/qat_sym_session.c      |   12 ++++++++++--
>  2 files changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/crypto/qat/qat_sym_capabilities.h b/drivers/crypto/qat/qat_sym_capabilities.h
> index 028a56c..d5487ae 100644
> --- a/drivers/crypto/qat/qat_sym_capabilities.h
> +++ b/drivers/crypto/qat/qat_sym_capabilities.h
> @@ -333,7 +333,7 @@
>  				.block_size = 16,			\
>  				.key_size = {				\
>  					.min = 16,			\
> -					.max = 16,			\
> +					.max = 32,			\
>  					.increment = 0			\
[Fiona] increment should be 16

           reply	other threads:[~2020-02-25 10:34 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1582624074-7981-1-git-send-email-mairtin.oloingsigh@intel.com>]

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=BN6PR11MB179650E9A20B052EC9142058E4ED0@BN6PR11MB1796.namprd11.prod.outlook.com \
    --to=fiona.trahe@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=mairtin.oloingsigh@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).