+deb_dpdk for visibility
This seems to be the definitive answer in terms of packaging. Because of
need for closed source, support for the MLX5 has to be outside and
independent of the RPM packaging.
On 11/30/2016 03:24 PM, Damjan Marion (damarion) wrote:
Hi Daniel,
Activating PMD also requires having closed-source MLX libraries
installed, as MLX
PMD is just wrapper around them
Fact that it depends on closed source libs prevents us from enabling
MLX devices by default.
So we will need to add configuration knob and that will require some
tweaking of vpp build system, I plan to do that but it is not top thing
on my todo list…
I was also thinking about building native driver for mlx using their
libraries and skip overhead of PMD, that might be interesting project…
Thanks,
Damjan
On 30 Nov 2016, at 20:36, Bernier, Daniel (520165)
<daniel.bern...@bell.ca <mailto:daniel.bern...@bell.ca>> wrote:
Hello,
Currently working on leveraging MLX5 drivers in VPP which requires
activating the PMD at DPDK compilation?
Is it something that can be done through the VPP build process (e.g.
tweaking with DPDK .config file)?
Making it part of the default binary package?
Thanks,
Daniel Bernier | Bell Canada
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io <mailto:vpp-dev@lists.fd.io>
https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
--
*Thomas F Herbert*
SDN Group
Office of Technology
*Red Hat*
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
