From: Akhil Goyal <gakhil@marvell.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>,
"Troy, Rebecca" <rebecca.troy@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test/crypto: refactor scheduler test worker PMDs
Date: Mon, 6 Sep 2021 19:53:52 +0000 [thread overview]
Message-ID: <CO6PR18MB4484A1610B04625D7DBED3B1D8D29@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <BL0PR11MB304368B929BC2B586FD3017EB8CF9@BL0PR11MB3043.namprd11.prod.outlook.com>
> >
> > Previously, the scheduler unit test only created and attached 1 or 2
> > AESNI-MB cryptodev PMDs as workers if less than 2 AESNI-MB PMDs had
> > already been initialized.
> >
> > This commit changes this to always create and attach 2 new AESNI-MB
> > cryptodev PMDs, regardless of previously initialized AESNI-MB PMDs.
> >
> > Signed-off-by: Rebecca Troy <rebecca.troy@intel.com>
> > ---
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2021-09-06 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 11:54 Rebecca Troy
2021-09-03 12:55 ` Zhang, Roy Fan
2021-09-06 19:53 ` Akhil Goyal [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=CO6PR18MB4484A1610B04625D7DBED3B1D8D29@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=rebecca.troy@intel.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).