Re: [dpdk-dev] [PATCH 01/25] eal: add API to lock/unlock memory hotplug

2019-05-29 Thread Stephen Hemminger
On Wed, 29 May 2019 17:30:47 +0100 Anatoly Burakov wrote: > +rte_eal_mcfg_mem_read_lock(void) > +{ > + struct rte_mem_config *mcfg = rte_eal_get_configuration()->mem_config; > + rte_rwlock_read_lock(&mcfg->memory_hotplug_lock); > +} > + We should also make eal configuration private but t

[dpdk-dev] [PATCH 01/25] eal: add API to lock/unlock memory hotplug

2019-05-29 Thread Anatoly Burakov
Currently, the memory hotplug is locked automatically by all memory-related _walk() functions, but sometimes locking the memory subsystem outside of them is needed. There is no public API to do that, so it creates a dependency on shared memory config to be public. Fix this by introducing a new API