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>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: update release notes for AESNI PMDs
Date: Fri, 15 Nov 2019 11:30:55 +0000	[thread overview]
Message-ID: <BN7PR11MB28365F6F09F558EB72BD7D7F84700@BN7PR11MB2836.namprd11.prod.outlook.com> (raw)
In-Reply-To: <VE1PR04MB6639178BA50FA337D1219E0FE6710@VE1PR04MB6639.eurprd04.prod.outlook.com>

Hi Akhil,

> -----Original Message-----
> From: Akhil Goyal <akhil.goyal@nxp.com>
> Sent: Thursday, November 14, 2019 1:51 PM
> To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>; Kovacevic, Marko <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] doc: update release notes for AESNI PMDs
> 
> Hi Pablo,
> 
> > AESNI MB and AESNI GCM PMDs were updated to support latest IPSec Multi
> > buffer library (v0.53), and the user guide of hose drivers were
> > updated but not release notes.
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> > ---
> >  doc/guides/rel_notes/release_19_11.rst | 9 +++++++++
> >  1 file changed, 9 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/release_19_11.rst
> > b/doc/guides/rel_notes/release_19_11.rst
> > index 682c1bdf3..441c53898 100644
> > --- a/doc/guides/rel_notes/release_19_11.rst
> > +++ b/doc/guides/rel_notes/release_19_11.rst
> > @@ -223,6 +223,15 @@ New Features
> >    Support is added for all sequence number sizes for control and user plane.
> >    Test application is updated for unit testing.
> >
> > +* **Updated the AESNI-MB PMD.**
> > +
> > +  * Added support for intel-ipsec-mb version 0.53.
> > +
> > +* **Updated the AESNI-GCM PMD.**
> > +
> > +  * Added support for intel-ipsec-mb version 0.53.
> > +  * Supported in-place chained mbufs on AES-GCM algorithm.
> > +
> 
> Both the bullets can be combined in a single bullet.

This is following the same format as was done in the past.
They are different statements, resulting from different patches.
They don't really have anything in common (basically, the chained mbuf support
 is not something that was done due to the new intel-ipsec-mb version).

Therefore, I'd say the should be two bullet points.

> 
> >  * **Enabled Single Pass GCM acceleration on QAT GEN3.**
> >
> >    Added support for Single Pass GCM, available on QAT GEN3 only
> > (Intel
> > --
> > 2.21.0
> 
> Ideally this patch should be part of the actual patch which was adding this
> support.

Yes, that was my bad, I forgot to add these. Apologies for this.

Thanks,
Pablo

> 
> -Akhil


  reply	other threads:[~2019-11-15 11:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-14 12:21 Pablo de Lara
2019-11-14 13:51 ` Akhil Goyal
2019-11-15 11:30   ` De Lara Guarch, Pablo [this message]
2019-11-18  9:36     ` Akhil Goyal

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=BN7PR11MB28365F6F09F558EB72BD7D7F84700@BN7PR11MB2836.namprd11.prod.outlook.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@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).