From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] doc: update dependency requirement for some PMDs
Date: Wed, 23 Jun 2021 16:52:50 +0000 [thread overview]
Message-ID: <BL0PR11MB30432235AC5514532B1FA81AB8089@BL0PR11MB3043.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210623094201.6e2f4ed1@hermes.local>
Hi Stephen,
You are right, but without this we cannot rule out the chance that the
user downloaded DPDK, reverted to any version earlier than 20.11 (where make
and meson co-existed) and use make to compile - also they happened to have
intel-ipsec-mb version 1.0 or newer installed before compiling DPDK.
With the description, at least they would know switching to meson build will fix
the problem.
Regards,
Fan
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Wednesday, June 23, 2021 5:42 PM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> Cc: dev@dpdk.org; gakhil@marvell.com
> Subject: Re: [dpdk-dev] doc: update dependency requirement for some
> PMDs
>
> On Wed, 23 Jun 2021 17:20:15 +0100
> Fan Zhang <roy.fan.zhang@intel.com> wrote:
>
> > diff --git a/doc/guides/cryptodevs/aesni_gcm.rst
> b/doc/guides/cryptodevs/aesni_gcm.rst
> > index 19f95bde8e..11b23958d5 100644
> > --- a/doc/guides/cryptodevs/aesni_gcm.rst
> > +++ b/doc/guides/cryptodevs/aesni_gcm.rst
> > @@ -83,9 +83,10 @@ and the external crypto libraries supported by them:
> > 17.02 - 17.05 ISA-L Crypto v2.18
> > 17.08 - 18.02 Multi-buffer library 0.46 - 0.48
> > 18.05 - 19.02 Multi-buffer library 0.49 - 0.52
> > - 19.05+ Multi-buffer library 0.52 - 1.0
> > + 19.05+ Multi-buffer library 0.52 - 1.0*
> > ============= ================================
> >
> > +\* Multi-buffer library 1.0 or newer only works for Meson but not Make
> build system.
>
> Make is no longer a supported build system, so why mention it in docs?
next prev parent reply other threads:[~2021-06-23 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 16:20 Fan Zhang
2021-06-23 16:42 ` Stephen Hemminger
2021-06-23 16:52 ` Zhang, Roy Fan [this message]
2021-07-06 19:54 ` 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=BL0PR11MB30432235AC5514532B1FA81AB8089@BL0PR11MB3043.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gakhil@marvell.com \
--cc=stephen@networkplumber.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).