DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: DPDK used for building programs and the one used to run the programs
Date: Tue, 5 Dec 2023 08:34:15 -0800	[thread overview]
Message-ID: <20231205083415.42afe17b@hermes.local> (raw)
In-Reply-To: <CAO8pfF=BQ6nC+WZV__N+rLE8cUKOSCYhjmY_6+MrqcxmT8Xz4g@mail.gmail.com>

On Tue, 5 Dec 2023 14:47:47 +0100
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:

> On the target machine I use to have a DPDK compiled after installing
> the Mellanox 5/6 drivers.
> I see that there are files related to MLX5 pmds in the target machine
> (include files).
> 
> To compile my programs I use a container where there is installed a
> DPDK that doesn't have the MLX5 support, I mean I don't find the
> rte_mlx5_pmds.h in the container.
> 
> Now, a program compiled in the container could have problems when
> using MLX5 on the target machine?
> 
> Thanks,
> Anna.

Header files are only used when compiling.
A possible issue is any shared libraries that MLX5 PMD is depending on not being
visible in the container.

      reply	other threads:[~2023-12-05 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 13:47 Antonio Di Bacco
2023-12-05 16:34 ` Stephen Hemminger [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=20231205083415.42afe17b@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).