From: Akhil Goyal <akhil.goyal@nxp.com>
To: "asomalap@amd.com" <asomalap@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>, Ravi Kumar <ravi1.kumar@amd.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1 6/6] crypto/ccp: scheduling multiple CCP within single burst
Date: Tue, 15 Oct 2019 11:15:05 +0000 [thread overview]
Message-ID: <VE1PR04MB66395C638A762A4D71AAF0D6E6930@VE1PR04MB6639.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <VE1PR04MB6639EEF54DB7223DA8332A7CE6930@VE1PR04MB6639.eurprd04.prod.outlook.com>
Also please include CCP maintainer in cc list for v2.
@Ravi Kumar: could you please review this series.
> -----Original Message-----
> From: Akhil Goyal
> Sent: Tuesday, October 15, 2019 4:43 PM
> To: asomalap@amd.com; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: RE: [PATCH v1 6/6] crypto/ccp: scheduling multiple CCP within single
> burst
>
> Title: crypto/ccp: schedule multiple devs within single burst
> Or
> Crypto/ccp: improve performance.
>
> >
> > From: Amaranath Somalapuram <asomalap@amd.com>
> >
> > ccp driver was scheduling only one CCP in a single burst.
> > Effective throughput was limited to 1 CCP performance.
> > Scheduling multiple ccp within one burst will increase the ccp performance.
> > this changes will divide the enqueue packets equally among the multiple CCP
> > Cc: stable@dpdk.org
>
> This patch also doesn't look like a fix, rather a performance improvement.
> Not sure if this need to be backported?
> If yes, then a fixes line is required and title would be "crypto/ccp: fix
> performance"
>
> >
> > Signed-off-by: Amaranath Somalapuram <asomalap@amd.com>
> > ---
prev parent reply other threads:[~2019-10-15 11:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 7:02 asomalap
2019-10-15 11:12 ` Akhil Goyal
2019-10-15 11:15 ` 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=VE1PR04MB66395C638A762A4D71AAF0D6E6930@VE1PR04MB6639.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=asomalap@amd.com \
--cc=dev@dpdk.org \
--cc=ravi1.kumar@amd.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).