[dpdk-dev] eal: DPDK: 18.11.6 version rte_eal_init() function cleans the runtime directory in 5.4.35 kernel

[Mohakud, Amiya Ranjan]

The primary process does not clear the files ( e.g. /var/run/dpdk/rte/fbarray_*) in case of 4.19 kernel, since the flock() fails. I think, this is correct behavior, since secondary processes rely on those files for their memzone_init().
But in 5.4, the primary process clears these files, which cause secondary processes to fail.


From: Burakov, Anatoly <anatoly.burakov at intel.com>
Sent: 15 October 2020 19:23
To: Mohakud, Amiya Ranjan <amohakud at rbbn.com>; dpdk-dev <dev at dpdk.org>
Subject: Re: [dpdk-dev] eal: DPDK: 18.11.6 version rte_eal_init() function cleans the runtime directory in 5.4.35 kernel

________________________________
NOTICE: This email was received from an EXTERNAL sender
________________________________

On 15-Oct-20 2:26 PM, Mohakud, Amiya Ranjan wrote:
> Hi All,
> I'm facing one issue with DPDK-18.11.6 in EAL library. Please find the below problem statement.
>
> Problem Statement:
> I have one DPDK application using DPDK version 18.11.6 which works fine in 4.19 version kernel. The rte_eal_init() works fine and eal_clean_runtime_dir() does not remove the files present in dpdk run time directory, /var/run/dpdk/rte/.
> The same application when I am trying to run in 5.4.35 kernel, the rte_eal_init() behavior is different. eal_clean_runtime_dir() cleans up dpdk run time directory, as a result the secondary processes fail to come up. Basically the flock system call succeeds , return value is 0 which goes and deletes the files. And in 4.19 kernel the flcok system call fails.
>
> Note: This is the case with 5.3 kernel version .
>

I'm not quite sure what the issue is. The runtime dir is *supposed to*
be cleared when you're running a primary process, and is not supposed to
be cleared when you're running a secondary process. Are you expecting
for a *primary* process to not clear the runtime directory?

--
Thanks,
Anatoly