Re: [dpdk-dev] [PATCH] eal: fix detection of static or shared DPDK builds

Hi Bruce,

Thanks for the fix.
I do see the issue mentioned when using DPDK shared libs with OVS and this patch fixes it.

However, I saw the issue only for system installed DPDK but not for directory installed DPDK.

 

I saw this issue with OVS, where I was getting weird failures about ports not
being bound (in case of physical ports) or not being created (in case of virtio
ports), when using a shared build. Since it's potentially serious, I'd appreciate
if someone can reproduce the issue and verify the fix so we can consider it
for 21.02 inclusion.

To demonstrate this with regular DPDK, do a usual build of DPDK and then do
"ninja install" to install system-wide. Then build an example app, e.g.
l2fwd, using "make" from the examples/l2fwd directory. Running the
example normally, e.g. ./build/l2fwd -c F00, leads to no drivers being loaded
or ports being found. Adding "-d /path/to/drivers" e.g.
"/usr/local/lib/x86_64-linux-gnu/dpdk/pmds-21.1" on my system works as
expected. This shows the driver loading is not correct.

After applying this patch and re-running "ninja install", l2fwd should run the
same with and without the "-d" flag.

/Bruce

Tested-by: Sunil Pai G <redacted>