This series was triggered after investigating why the eal_flags_file_prefix_autotest unit test was failing in the case of statically built binaries [1]).
For now, I went with a simple (naive) approach and put all accesses to the shared data under a single lock: ethdev maintainers, it is your turn to shine and give me reasons why we should keep the locks the way they were ;-). And let's see what the CI reports... 1: https://inbox.dpdk.org/dev/20230816153439.551501-12-bruce.richard...@intel.com/T/#m0e4c23f7be80bbdac076a387f4a2f9094dd07e0a -- David Marchand David Marchand (2): ethdev: protect shared memory accesses under one lock ethdev: cleanup shared data with the last port lib/eal/common/eal_common_mcfg.c | 6 +++ lib/eal/common/eal_memcfg.h | 1 + lib/eal/include/rte_eal_memconfig.h | 4 ++ lib/eal/version.map | 1 + lib/ethdev/ethdev_driver.c | 36 ++++++++++------- lib/ethdev/ethdev_private.c | 23 ++++++----- lib/ethdev/ethdev_private.h | 12 ++++-- lib/ethdev/rte_ethdev.c | 60 ++++++++++++++++------------- 8 files changed, 91 insertions(+), 52 deletions(-) -- 2.41.0
