From: Radu Nicolau <radu.nicolau@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>, Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: Re: [PATCH] crypto/ipsec_mb: require minimum version 2.0 for IPsec MB
Date: Tue, 11 Aug 2026 17:21:32 +0100 [thread overview]
Message-ID: <475ae05d-aa41-4a2d-bb54-1912fd3aae2a@intel.com> (raw)
In-Reply-To: <20260811085300.66c89502@phoenix.local>
On 11-Aug-26 4:53 PM, Stephen Hemminger wrote:
> On Tue, 11 Aug 2026 11:26:35 +0000
> Radu Nicolau <radu.nicolau@intel.com> wrote:
>
>> Increase the minimum required IPsec MB library version to 2.0
>> As a consequence, clean up the aesni_mb PMD code.
>>
>> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
>> ---
> What happens if user has out of date library?
> Is it detected at build config time with reasonable warning?
At config time the PMDs will be disabled with a warning explaining the
reason: "IPSec_MB version >= 2.0.0 is required, found version 1.5.0".
> What was release date?
> Debian changelog says 2.0 was introduced in 18 Sep 2024
> and is Debian stable (trixie).
According to
https://github.com/intel/intel-ipsec-mb/releases#release-v2.0 it's
November 2024
prev parent reply other threads:[~2026-08-11 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 11:26 [PATCH] crypto/ipsec_mb: require minimum version 2.0 for IPsec MB Radu Nicolau
2026-08-11 15:53 ` Stephen Hemminger
2026-08-11 16:21 ` Radu Nicolau [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=475ae05d-aa41-4a2d-bb54-1912fd3aae2a@intel.com \
--to=radu.nicolau@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=pablo.de.lara.guarch@intel.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