From: "Mohakud, Amiya Ranjan" <amohakud@rbbn.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.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: Mon, 4 Jan 2021 07:53:45 +0000 [thread overview]
Message-ID: <DM6PR03MB3547C29AA48A66BF86C16491B9D20@DM6PR03MB3547.namprd03.prod.outlook.com> (raw)
In-Reply-To: <55c4c285-a0b0-f390-1e68-5ac4e6f5268f@intel.com>
Hi Anatoly - Happy New Year !
I have updated the bug https://bugs.dpdk.org/show_bug.cgi?id=561with my latest comments. Request you to please have a look and let me know if anything more is required. Thanks!
Regards
Amiya
From: Burakov, Anatoly <anatoly.burakov@intel.com>
Sent: 30 October 2020 15:30
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
________________________________
NOTICE: This email was received from an EXTERNAL sender
________________________________
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
prev parent reply other threads:[~2021-01-04 7:53 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 ` [dpdk-dev] eal: DPDK: 18.11.6 version rte_eal_init() function cleans the runtime directory in 5.4.35 kernel 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
2021-01-04 7:53 ` Mohakud, Amiya Ranjan [this message]
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=DM6PR03MB3547C29AA48A66BF86C16491B9D20@DM6PR03MB3547.namprd03.prod.outlook.com \
--to=amohakud@rbbn.com \
--cc=anatoly.burakov@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.