From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: dev@dpdk.org, Jan Blunck <jblunck@infradead.org>,
cjcollier@linuxfoundation.org, ricardo.salveti@linaro.org,
Luca Boccassi <luca.boccassi@gmail.com>
Subject: Re: [dpdk-dev] [PATCH v2] mk: Provide option to set Major ABI version
Date: Thu, 16 Mar 2017 18:19:50 +0100 [thread overview]
Message-ID: <4962963.ZZcnbaMyEK@xps13> (raw)
In-Reply-To: <CALe+Z03-PzvnO_TeYQDMeT6MQw4eExYKkcwLxHP0kMS14cL9jg@mail.gmail.com>
2017-03-01 15:35, Jan Blunck:
> On Wed, Mar 1, 2017 at 10:34 AM, Christian Ehrhardt
> <christian.ehrhardt@canonical.com> wrote:
> > Downstreams might want to provide different DPDK releases at the same
> > time to support multiple consumers of DPDK linked against older and newer
> > sonames.
> >
> > Also due to the interdependencies that DPDK libraries can have applications
> > might end up with an executable space in which multiple versions of a
> > library are mapped by ld.so.
> >
> > Think of LibA that got an ABI bump and LibB that did not get an ABI bump
> > but is depending on LibA.
> >
> > Application
> > \-> LibA.old
> > \-> LibB.new -> LibA.new
> >
> > That is a conflict which can be avoided by setting CONFIG_RTE_MAJOR_ABI.
> > If set CONFIG_RTE_MAJOR_ABI overwrites any LIBABIVER value.
> > An example might be ``CONFIG_RTE_MAJOR_ABI=16.11`` which will make all
> > libraries librte<?>.so.16.11 instead of librte<?>.so.<LIBABIVER>.
[...]
> >
> > Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
> Reviewed-by: Jan Blunck <jblunck@infradead.org>
> Tested-by: Jan Blunck <jblunck@infradead.org>
Not sure about how it can be used in distributions, but it does not hurt
to provide the config option.
Are you going to link applications against a fixed DPDK version for
every libraries?
Applied, thanks
next prev parent reply other threads:[~2017-03-16 17:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 10:52 [dpdk-dev] Further fun with ABI tracking Christian Ehrhardt
2017-02-14 16:19 ` Bruce Richardson
2017-02-14 20:31 ` Jan Blunck
2017-02-22 13:12 ` Christian Ehrhardt
2017-02-22 13:24 ` [dpdk-dev] [PATCH] mk: Provide option to set Major ABI version Christian Ehrhardt
2017-02-28 8:34 ` Jan Blunck
2017-03-01 9:31 ` Christian Ehrhardt
2017-03-01 9:34 ` [dpdk-dev] [PATCH v2] " Christian Ehrhardt
2017-03-01 14:35 ` Jan Blunck
2017-03-16 17:19 ` Thomas Monjalon [this message]
2017-03-17 8:27 ` Christian Ehrhardt
2017-03-17 9:16 ` Jan Blunck
2017-02-23 18:48 ` [dpdk-dev] Further fun with ABI tracking Ferruh Yigit
2017-02-24 7:32 ` Christian Ehrhardt
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=4962963.ZZcnbaMyEK@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=christian.ehrhardt@canonical.com \
--cc=cjcollier@linuxfoundation.org \
--cc=dev@dpdk.org \
--cc=jblunck@infradead.org \
--cc=luca.boccassi@gmail.com \
--cc=ricardo.salveti@linaro.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).