DPDK patches and discussions
 help / color / mirror / Atom feed
From: Timothy Redaelli <tredaelli@redhat.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Shahaf Shuler <shahafs@mellanox.com>, dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx: fix rdma-core glue path with EAL plugins
Date: Fri, 2 Mar 2018 17:07:42 +0100	[thread overview]
Message-ID: <20180302170742.5552983b@redhat.com> (raw)
In-Reply-To: <20180302141211.30818-1-adrien.mazarguil@6wind.com>

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>

Tested with and without libibverbs installed and with an old version of
libibverbs installed and it works like it should.

  reply	other threads:[~2018-03-02 16:07 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 [this message]
2018-03-12 10:05     ` Shahaf Shuler

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=20180302170742.5552983b@redhat.com \
    --to=tredaelli@redhat.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.com \
    --cc=stable@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).