From: Truring Team <truring12@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] How to Enable Mellanox Driver Compilation with DPDK20.11
Date: Fri, 29 Jan 2021 18:20:52 +0530 [thread overview]
Message-ID: <CALvshjPMjS3R6hcwh67YnQG3fCSJk-szaid9iKLLVNCQsXSo1g@mail.gmail.com> (raw)
In-Reply-To: <20210129100800.GC929@bricha3-MOBL.ger.corp.intel.com>
Hi Bruce ,
Thanks a lot for your help.
After installing below packages mlx is compiled .
yum -y groupinstall "Infiniband Support"
yum install -y gcc kernel-devel-`uname -r` numactl-devel.x86_64
librdmacm-devel libmnl-devel
*find . -name *.a | grep mlx*
*./drivers/libtmp_rte_common_mlx5.a*
*./drivers/librte_common_mlx5.a*
*./drivers/libtmp_rte_net_mlx4.a*
*./drivers/librte_net_mlx4.a*
*./drivers/libtmp_rte_regex_mlx5.a*
*./drivers/librte_regex_mlx5.a*
*./drivers/libtmp_rte_vdpa_mlx5.a*
*./drivers/librte_vdpa_mlx5.a*
*./drivers/libtmp_rte_net_mlx5.a*
*./drivers/librte_net_mlx5.a*
Best Regards
Puneet
On Fri, 29 Jan 2021 at 15:38, Bruce Richardson <bruce.richardson@intel.com>
wrote:
> On Fri, Jan 29, 2021 at 11:50:08AM +0530, Truring Team wrote:
> > Hi Team ,
> >
> > Can someone help me to figure out how to enable the Mellanox Driver flag
> > in meson.build file , so that dpdk 20.11 compiles with mlx driver
> enabled.
> >
> If the driver is not being built there should be a reason given in the
> build configuration summary when you run meson. This is almost certainly
> that you are missing a library dependency for it, since all drivers are
> enabled unless their dependencies are missing.
>
> /Bruce
>
prev parent reply other threads:[~2021-01-29 12:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 6:20 Truring Team
2021-01-29 10:08 ` Bruce Richardson
2021-01-29 12:50 ` Truring Team [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=CALvshjPMjS3R6hcwh67YnQG3fCSJk-szaid9iKLLVNCQsXSo1g@mail.gmail.com \
--to=truring12@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=dev@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).