From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Mohakud, Amiya Ranjan" <amohakud@rbbn.com>, dpdk-dev <dev@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
Date: Fri, 30 Oct 2020 10:00:14 +0000 [thread overview]
Message-ID: <55c4c285-a0b0-f390-1e68-5ac4e6f5268f@intel.com> (raw)
In-Reply-To: <DM6PR03MB354735D92E93448941947046B9140@DM6PR03MB3547.namprd03.prod.outlook.com>
On 29-Oct-20 5:40 PM, Mohakud, Amiya Ranjan wrote:
> Hi Anatoly
>
> Thanks for the reply.
>
> Do you have a sample code for primary and secondary processes which I
> can try in my setup? And once reproduced, can let you know.
>
> We have DPDK applications in our product with which I always see this issue.
>
> Regards
>
> Amiya
>
Hi,
I was running a test app with a debugger, putting a break point before
and after eal_cleanup_runtime_dir(), and checking if things were deleted
that shouldn't have been deleted. Any old DPDK app will do for this
purpose, as all of them will call EAL init.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-10-30 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR03MB3547EDC8BAAD1DA17AE4470EB9020@DM6PR03MB3547.namprd03.prod.outlook.com>
2020-10-15 13:26 ` Mohakud, Amiya Ranjan
2020-10-15 13:52 ` Burakov, Anatoly
2020-10-15 14:43 ` Mohakud, Amiya Ranjan
2020-10-15 15:08 ` Burakov, Anatoly
2020-10-15 16:07 ` Mohakud, Amiya Ranjan
2020-10-15 16:14 ` Mohakud, Amiya Ranjan
2020-10-15 18:01 ` Burakov, Anatoly
2020-10-15 18:34 ` Burakov, Anatoly
2020-10-16 5:34 ` Mohakud, Amiya Ranjan
2020-10-22 7:12 ` Mohakud, Amiya Ranjan
[not found] ` <DM6PR03MB3547C263D4E20B3DD124AD43B91D0@DM6PR03MB3547.namprd03.prod.outlook.com>
2020-10-28 7:00 ` Mohakud, Amiya Ranjan
2020-10-29 15:51 ` Burakov, Anatoly
2020-10-29 17:10 ` Burakov, Anatoly
2020-10-29 17:40 ` Mohakud, Amiya Ranjan
2020-10-30 10:00 ` Burakov, Anatoly [this message]
2021-01-04 7:53 ` Mohakud, Amiya Ranjan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55c4c285-a0b0-f390-1e68-5ac4e6f5268f@intel.com \
--to=anatoly.burakov@intel.com \
--cc=amohakud@rbbn.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).