From: Shahaf Shuler <shahafs@mellanox.com>
To: Timothy Redaelli <tredaelli@redhat.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx: fix rdma-core glue path with EAL plugins
Date: Mon, 12 Mar 2018 10:05:13 +0000 [thread overview]
Message-ID: <DB7PR05MB44263829B447A030E614166CC3D30@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180302170742.5552983b@redhat.com>
Friday, March 2, 2018 6:08 PM, Timothy Redaelli:
> On Fri, 2 Mar 2018 15:15:17 +0100
> Adrien Mazarguil <adrien.mazarguil@6wind.com> wrote:
>
> > Glue object files are looked up in RTE_EAL_PMD_PATH by default when
> > set and should be installed in this directory.
> >
> > During startup, EAL attempts to load them automatically like other
> > plug-ins found there. While normally harmless, dlopen() fails when
> > rdma-core is not installed, EAL interprets this as a fatal error and
> > terminates the application.
> >
> > This patch requests glue objects to be installed in a different
> > directory to prevent their automatic loading by EAL since they are PMD
> > helpers, not actual DPDK plug-ins.
> >
> > Fixes: f6242d0655cd ("net/mlx: make rdma-core glue path configurable")
> > Cc: stable@dpdk.org
> >
> > Reported-by: Timothy Redaelli <tredaelli@redhat.com>
> > Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>
> Tested-by: Timothy Redaelli <tredaelli@redhat.com>
Applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-03-12 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 12:43 [dpdk-dev] [PATCH] " Adrien Mazarguil
2018-03-02 14:15 ` [dpdk-dev] [PATCH v2] " Adrien Mazarguil
2018-03-02 16:07 ` Timothy Redaelli
2018-03-12 10:05 ` Shahaf Shuler [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=DB7PR05MB44263829B447A030E614166CC3D30@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=tredaelli@redhat.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).