From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: ABI version on build machine and target machine
Date: Tue, 20 Sep 2022 08:13:33 -0700 [thread overview]
Message-ID: <20220920081333.4ef0e8db@hermes.local> (raw)
In-Reply-To: <CAO8pfF=iwJz+ePp0m3oN8zGV=8Wp+6g4_TqjCqkjQM-f9TV21Q@mail.gmail.com>
On Tue, 20 Sep 2022 16:24:52 +0200
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:
> I have an application that is built with version 21.11.0 of the DPDK (ABI22).
> Now I run the application on a target machine that has 21.11.2
> installed, then the same ABI.
>
> How can I be sure that the DPDK inlined source code in 21.11.0 is the
> same or compatible with that in 21.11.2?
> I mean, if an inline function in version 21.11.0 has changed in
> 21.11.2, could I see problems?
>
> Is this important or the fact that the two DPDKs have the same ABI
> grants that everything will work?
yes. Especially for bugfix (ie stable) releases.
The only thing is that if a bug fix is done in an inline in 21.11.2
then obviously you have to build with that version to get it.
next prev parent reply other threads:[~2022-09-20 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 14:24 Antonio Di Bacco
2022-09-20 15:13 ` Stephen Hemminger [this message]
2022-09-20 20:17 ` Antonio Di Bacco
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=20220920081333.4ef0e8db@hermes.local \
--to=stephen@networkplumber.org \
--cc=a.dibacco.ks@gmail.com \
--cc=users@dpdk.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).