From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>, Jun Yang <jun.yang@nxp.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] examples/ip_pipeline: fix crypto queue config
Date: Fri, 14 Feb 2020 10:52:03 +0000 [thread overview]
Message-ID: <SN6PR11MB262255750F486B7B92A51DFFB8150@SN6PR11MB2622.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20191211052534.14600-1-hemant.agrawal@nxp.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Hemant Agrawal
> Sent: Wednesday, December 11, 2019 5:26 AM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; stable@dpdk.org;
> Jun Yang <jun.yang@nxp.com>; Hemant Agrawal
> <hemant.agrawal@nxp.com>
> Subject: [dpdk-dev] [PATCH 1/2] examples/ip_pipeline: fix crypto queue
> config
>
> queue_conf need to have mempool details before pair setup.
>
> Fixes: 261bbff75e34 ("examples: use separate crypto session mempools")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jun Yang <jun.yang@nxp.com>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2020-02-14 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 5:25 Hemant Agrawal
2019-12-11 5:25 ` [dpdk-dev] [PATCH 2/2] examples/ip_pipeline: fix to use sock id instead of cpuid Hemant Agrawal
2020-02-14 11:27 ` Dumitrescu, Cristian
2020-02-14 15:18 ` [dpdk-dev] [EXT] " Jun Yang
2020-02-18 10:47 ` Dumitrescu, Cristian
2020-02-19 14:17 ` Jun Yang
2020-02-14 10:52 ` Zhang, Roy Fan [this message]
2020-02-14 11:22 ` [dpdk-dev] [PATCH 1/2] examples/ip_pipeline: fix crypto queue config Dumitrescu, Cristian
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=SN6PR11MB262255750F486B7B92A51DFFB8150@SN6PR11MB2622.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jun.yang@nxp.com \
--cc=stable@dpdk.org \
/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).