DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
	Hernan Vargas <hernan.vargas@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"trix@redhat.com" <trix@redhat.com>
Cc: "nicolas.chautru@intel.com" <nicolas.chautru@intel.com>,
	"qi.z.zhang@intel.com" <qi.z.zhang@intel.com>
Subject: RE: [EXT] Re: [PATCH v8 1/1] baseband/acc100: add detection for deRM corner cases
Date: Mon, 7 Nov 2022 04:46:59 +0000	[thread overview]
Message-ID: <CO6PR18MB4484D5D1EA8E2DB1D5EFE6D5D83C9@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <8d994300-c7ff-0002-1059-7b2700b661ab@redhat.com>

> On 11/4/22 04:08, Hernan Vargas wrote:
> > Add function to detect if de-ratematch pre-processing is recommended for
> > SW corner cases.
> > Some specific 5GUL FEC corner cases may cause unintended back pressure
> > and in some cases a potential stability issue on the ACC100.
> > The PMD can detect such code block configuration and issue an info
> > message to the user.
> >
> > Signed-off-by: Hernan Vargas <hernan.vargas@intel.com>
> > ---
> >   drivers/baseband/acc/acc_common.h     |  8 +++++
> >   drivers/baseband/acc/rte_acc100_pmd.c | 48
> ++++++++++++++++++++++++++-
> >   2 files changed, 55 insertions(+), 1 deletion(-)
> >
> 
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Applied to dpdk-next-crypto

Subject changed to
baseband/acc100: detect deRM corner cases 

Use only one verb in patch titles.

      reply	other threads:[~2022-11-07  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04  3:08 [PATCH v8 0/1] baseband/acc100: changes for 22.11 Hernan Vargas
2022-11-04  3:08 ` [PATCH v8 1/1] baseband/acc100: add detection for deRM corner cases Hernan Vargas
2022-11-03 19:44   ` Maxime Coquelin
2022-11-07  4:46     ` 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=CO6PR18MB4484D5D1EA8E2DB1D5EFE6D5D83C9@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=dev@dpdk.org \
    --cc=hernan.vargas@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=nicolas.chautru@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=trix@redhat.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).