DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Power, Ciara" <ciara.power@intel.com>
To: Aaron Conole <aconole@redhat.com>
Cc: "Sivaramakrishnan, VenkatX" <venkatx.sivaramakrishnan@intel.com>,
	"Akhil Goyal" <gakhil@marvell.com>, "Ji, Kai" <kai.ji@intel.com>,
	"probb@iol.unh.edu" <probb@iol.unh.edu>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
Subject: RE: reg. https://patches.dpdk.org/project/dpdk/list/?series=31200 - patch result
Date: Wed, 6 Mar 2024 12:20:30 +0000	[thread overview]
Message-ID: <SN7PR11MB7639E03F54FF99371C824575E6212@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f7ty1awa5k6.fsf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]

Hi Aaron,

> -----Original Message-----
> From: Aaron Conole <aconole@redhat.com>
> Sent: Tuesday, March 5, 2024 6:37 PM
> To: Power, Ciara <ciara.power@intel.com>
> Cc: Sivaramakrishnan, VenkatX <venkatx.sivaramakrishnan@intel.com>; Akhil
> Goyal <gakhil@marvell.com>; Ji, Kai <kai.ji@intel.com>; probb@iol.unh.edu;
> dev@dpdk.org
> Subject: Re: reg. https://patches.dpdk.org/project/dpdk/list/?series=31200 -
> patch result
>
> "Power, Ciara" <ciara.power@intel.com> writes:
>
> > + Patrick
> >
> >
> >
> > From: Power, Ciara
> > Sent: Tuesday, March 5, 2024 10:05 AM
> > To: Sivaramakrishnan, VenkatX <venkatx.sivaramakrishnan@intel.com>;
> > Akhil Goyal <gakhil@marvell.com>
> > Cc: Ji, Kai <kai.ji@intel.com>; Aaron Conole <aconole@redhat.com>
> > Subject: RE: reg.
> > https://patches.dpdk.org/project/dpdk/list/?series=31200 - patch
> > result
> >
> >
> >
> > Hi folks,
> >
> >
> >
> > Had a quick look, I can also see this:
> >
> > crypto/ipsec_mb: IPSec_MB version >= 1.4.0 is required, found version
> > 1.2.0
>
> This version of ipsec_mb is less than 1 year old.  Did this pass any other CI
> testing?  I would be surprised if it did - I'm not sure any downstream
> environments that would be using it already.

We have been using 1.4 (and even 1.5 since it was released) for internal regression testing and development.
Other than that, the library would be tested by Intel-ipsec-mb team directly.
1.4 has been supported by the ipsec-mb SW PMDs since it was released, but now we would like to make it the required version,
to remove the various ifdef codepaths in PMD, and use the newer, more performant version of the library.



>
> > I guess the installed PMD .so file isn’t created because they are not
> > compiled in, due to the minimum version on environment not meeting the
> new requirements.
>
> I don't see any such new requirements anywhere on the crypto tree.  The only
> change I know about was for QAT to try and default to IPSec_MB 1.4, but it is
> supposed to fall back to OpenSSL if that is unavailable.  Did this change?

This patchset introduces the requirement, it is not yet on the crypto tree.
It is a SW PMD change only - currently they require 1.1 ipsec-mb, but we want to bump that to 1.4.
QAT dependencies are unchanged.

Thanks,
Ciara

[-- Attachment #2: Type: text/html, Size: 3305 bytes --]

  reply	other threads:[~2024-03-06 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CH3PR11MB85898465A351CD7EEFDB707682232@CH3PR11MB8589.namprd11.prod.outlook.com>
     [not found] ` <SN7PR11MB7639AB757ECB3D039E47B10AE6222@SN7PR11MB7639.namprd11.prod.outlook.com>
2024-03-05 18:37   ` Aaron Conole
2024-03-06 12:20     ` Power, Ciara [this message]
2024-03-06 14:57       ` Aaron Conole
2024-03-06 16:57         ` Power, Ciara
2024-03-08 19:39           ` Aaron Conole

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=SN7PR11MB7639E03F54FF99371C824575E6212@SN7PR11MB7639.namprd11.prod.outlook.com \
    --to=ciara.power@intel.com \
    --cc=aconole@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=probb@iol.unh.edu \
    --cc=venkatx.sivaramakrishnan@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).