From: Raslan Darawsheh <rasland@nvidia.com>
To: Gerry Wan <gerryw@stanford.edu>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Enable MLX5 driver v20.11
Date: Sun, 13 Dec 2020 08:35:24 +0000 [thread overview]
Message-ID: <DM6PR12MB2748BD4F7E1E933BA2B89137CFC80@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAAcwi38fEK-JS2OQy6MLVgBp7tP7W5SjPGqs9RbymK+OzUP5qQ@mail.gmail.com>
Hi Gerry,
Starting V20.11 the build system was switched to use meson only,
And if you have necessary packages for MLX5 (a.k. rdma-core) it will be built automatically.
As for your question if you still don't need to bind mlx5 driver that's true, its still valid.
Kindest regards,
Raslan Darawsheh
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Gerry Wan
> Sent: Sunday, December 13, 2020 1:22 AM
> To: users@dpdk.org
> Subject: [dpdk-users] Enable MLX5 driver v20.11
>
> Hello,
> I am trying to update my DPDK version from 20.08 to 20.11. I am using the
> mlx5 driver, and previously to enable it I had to set
> CONFIG_RTE_LIBRTE_MLX5_PMD=y in config/common_base. In 20.11, I see
> no
> option to do so. I was able to build my application (and the sample
> applications), but running rte_eth_dev_count_avail() returns 0 and cannot
> find any ports.
>
> The steps I did to build DPDK from source were:
>
> $ meson build
>
> $ cd build
>
> $ sudo ninja install
>
> $ sudo ldconfig
>
>
> Normally I would edit dpdk-20.xx/config/common_base before meson build,
> but
> that file is gone.
>
> What are the steps I need to take to enable mlx5 driver? I also recall that
> I don't need to bind the mlx5 driver, is that still the case?
>
> Thanks
next prev parent reply other threads:[~2020-12-13 8:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 23:22 Gerry Wan
2020-12-13 8:35 ` Raslan Darawsheh [this message]
2020-12-13 11:25 ` Gerry Wan
2020-12-13 11:31 ` Raslan Darawsheh
2020-12-13 21:04 ` Gerry Wan
2020-12-14 5:32 ` Gerry Wan
2020-12-14 8:27 ` Raslan Darawsheh
2020-12-14 8:40 ` Raslan Darawsheh
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=DM6PR12MB2748BD4F7E1E933BA2B89137CFC80@DM6PR12MB2748.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=gerryw@stanford.edu \
--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).