The decision to deliver mlx4/mlx5 rdma-core glue plug-ins separately instead of generating them at run time due to security concerns [1] led to a few issues:
- They must be present on the file system before running DPDK. - Their location must be known to the dynamic linker. - Their names overlap and ABI compatibility is not guaranteed, which may lead to crashes. This series addresses the above by adding version information to plug-ins and taking CONFIG_RTE_EAL_PMD_PATH into account to locate them on the file system. [1] http://dpdk.org/ml/archives/dev/2018-January/089617.html v2 changes: - Fixed extra "\n" in glue file name generation (although it didn't break functionality). Adrien Mazarguil (4): net/mlx: add debug checks to glue structure net/mlx: fix missing includes for rdma-core glue net/mlx: version rdma-core glue libraries net/mlx: make rdma-core glue path configurable doc/guides/nics/mlx4.rst | 17 ++++++++++++ doc/guides/nics/mlx5.rst | 14 ++++++++++ drivers/net/mlx4/Makefile | 8 ++++-- drivers/net/mlx4/mlx4.c | 57 ++++++++++++++++++++++++++++++++++++++- drivers/net/mlx4/mlx4_glue.c | 4 +++ drivers/net/mlx4/mlx4_glue.h | 9 +++++++ drivers/net/mlx5/Makefile | 8 ++++-- drivers/net/mlx5/mlx5.c | 57 ++++++++++++++++++++++++++++++++++++++- drivers/net/mlx5/mlx5_glue.c | 1 + drivers/net/mlx5/mlx5_glue.h | 7 +++++ 10 files changed, 176 insertions(+), 6 deletions(-) -- 2.11.0
