Re: [dpdk-dev] [PATCH] eal: check if hugedir write lock is already being held

30/04/2018 15:07, Andrew Rybchenko: > On 04/30/2018 01:38 PM, Anatoly Burakov wrote: > > At hugepage info initialization, EAL takes out a write lock on > > hugetlbfs directories, and drops it after the memory init is > > finished. However, in non-legacy mode, if "-m" or "--socket-mem" > > switches

Re: [dpdk-dev] [PATCH] eal: check if hugedir write lock is already being held

On 04/30/2018 01:38 PM, Anatoly Burakov wrote: At hugepage info initialization, EAL takes out a write lock on hugetlbfs directories, and drops it after the memory init is finished. However, in non-legacy mode, if "-m" or "--socket-mem" switches are passed, this leads to a deadlock because EAL tri

Re: [dpdk-dev] [PATCH] eal: check if hugedir write lock is already being held

Monday, April 30, 2018 1:38 PM, Anatoly Burakov: > Cc: arybche...@solarflare.com; anatoly.bura...@intel.com > Subject: [dpdk-dev] [PATCH] eal: check if hugedir write lock is already being > held > > At hugepage info initialization, EAL takes out a write lock on hugetlbfs > dire

[dpdk-dev] [PATCH] eal: check if hugedir write lock is already being held

At hugepage info initialization, EAL takes out a write lock on hugetlbfs directories, and drops it after the memory init is finished. However, in non-legacy mode, if "-m" or "--socket-mem" switches are passed, this leads to a deadlock because EAL tries to allocate pages (and thus take out a write l