DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Akhil Goyal <akhil.goyal@nxp.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Nipun Gupta <nipun.gupta@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 4/4] crypto/dpaa_sec: update maximum queue pairs to 2
Date: Fri, 20 Apr 2018 16:00:21 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8976CCD9999@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <a2483237-116d-2901-6830-a58268bacd24@nxp.com>



> -----Original Message-----
> From: Akhil Goyal [mailto:akhil.goyal@nxp.com]
> Sent: Friday, April 20, 2018 11:40 AM
> To: Hemant Agrawal <hemant.agrawal@nxp.com>; dev@dpdk.org; De Lara
> Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> Cc: Nipun Gupta <nipun.gupta@nxp.com>
> Subject: Re: [PATCH 4/4] crypto/dpaa_sec: update maximum queue pairs to 2
> 
> Hi Hemant,
> On 4/20/2018 3:53 PM, Hemant Agrawal wrote:
> >
> >
> >> Hi Hemant/Nipun
> >> On 4/19/2018 10:22 PM, Hemant Agrawal wrote:
> >>> From: Nipun Gupta <nipun.gupta@nxp.com>
> >>>
> >>> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> >>> ---
> >>>  drivers/crypto/dpaa_sec/dpaa_sec.h | 2 +-
> >>>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>> diff --git a/drivers/crypto/dpaa_sec/dpaa_sec.h
> >>> b/drivers/crypto/dpaa_sec/dpaa_sec.h
> >>> index 1433595..5b25aa1 100644
> >>> --- a/drivers/crypto/dpaa_sec/dpaa_sec.h
> >>> +++ b/drivers/crypto/dpaa_sec/dpaa_sec.h
> >>> @@ -136,7 +136,7 @@ struct dpaa_sec_qp {
> >>>  	int tx_errs;
> >>>  };
> >>>
> >>> -#define RTE_DPAA_MAX_NB_SEC_QPS 1
> >>> +#define RTE_DPAA_MAX_NB_SEC_QPS 2
> >>>  #define RTE_DPAA_MAX_RX_QUEUE
> >> RTE_DPAA_SEC_PMD_MAX_NB_SESSIONS
> >>> #define DPAA_MAX_DEQUEUE_NUM_FRAMES 63
> >>>
> >>>
> >> Why 2? I think it should be 8.
> >>
> > [Hemant] Ok. Sending v2
> 
> I guess this need some testing whether it will break the existing use cases or not.
> 
> Pablo,
> 
> I recommend, it would be good if you can apply the other 3 patches in this series
> in RC1. This patch should be hold back for RC2.

Good to me.
Thanks,
Pablo

> 
> Thanks,
> Akhil

  reply	other threads:[~2018-04-20 16:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 16:52 [dpdk-dev] [PATCH 1/4] crypto/dpaa_sec: support dynamic logging Hemant Agrawal
2018-04-19 16:52 ` [dpdk-dev] [PATCH 2/4] crypto/dpaa_sec: fix HMAC supported digest sizes Hemant Agrawal
2018-04-20 10:35   ` Akhil Goyal
2018-04-19 16:52 ` [dpdk-dev] [PATCH 3/4] crypto/dpaa2_sec: " Hemant Agrawal
2018-04-20 10:36   ` Akhil Goyal
2018-04-19 16:52 ` [dpdk-dev] [PATCH 4/4] crypto/dpaa_sec: update maximum queue pairs to 2 Hemant Agrawal
2018-04-20  9:47   ` De Lara Guarch, Pablo
2018-04-20 10:22     ` Akhil Goyal
2018-04-20 10:20   ` Akhil Goyal
2018-04-20 10:23     ` Hemant Agrawal
2018-04-20 10:40       ` Akhil Goyal
2018-04-20 16:00         ` De Lara Guarch, Pablo [this message]
2018-05-07 13:39           ` De Lara Guarch, Pablo
2018-05-08 11:24   ` [dpdk-dev] [PATCH v2] crypto/dpaa_sec: update maximum queue pairs to 8 Hemant Agrawal
2018-05-09  7:06     ` Akhil Goyal
2018-05-09  8:05       ` De Lara Guarch, Pablo
2018-04-20 10:35 ` [dpdk-dev] [PATCH 1/4] crypto/dpaa_sec: support dynamic logging Akhil Goyal
2018-04-20 16:09 ` De Lara Guarch, Pablo

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=E115CCD9D858EF4F90C690B0DCB4D8976CCD9999@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=nipun.gupta@nxp.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).