From: "Kumar, Ruban" <ruban.kumar@hughes.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Memzone corruption Issue
Date: Wed, 26 May 2021 14:52:43 +0000 [thread overview]
Message-ID: <BL0PR11MB3170D8A6C1B455889CE4017895249@BL0PR11MB3170.namprd11.prod.outlook.com> (raw)
Hi,
I have a sample_dpdk_app program which uses memzone as shared memory between the Lcores. The program was developed and tested using DPDK 19.02 , and the code works as expected. On compiling the same sample_dpdk_app with DPDK 20.08 , we notice the following issues,
1. The memzone used as shared memory seems to be corrupted. Primary writes a structure into the memzone and when secondary reads the structure, I see that some of the structure members are corrupted.
2. During compilation we see this warning /opt/dpdk/dpdk-20.08/x86_64-native-linuxapp-icc/include/generic/rte_rwlock.h(142): warning #68: integer conversion resulted in a change of sign
if (x != 0 || __atomic_compare_exchange_n(&rwl->cnt, &x, -1, 1,
^
I am not sure if the above mentioned issues are related, Any help will be greatly appreciated !!
---
Primary lcore creates the memzone as shown below
const struct rte_memzone* zone = rte_memzone_reserve("testzone", 64*numFlows, rte_socket_id(), RTE_MEMZONE_2MB);
Secondary lcore does a lookup of the memzone as shown below
const struct rte_memzone* zone = rte_memzone_lookup("testzone");
Thanks & Regards,
Ruban
reply other threads:[~2021-05-26 14:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BL0PR11MB3170D8A6C1B455889CE4017895249@BL0PR11MB3170.namprd11.prod.outlook.com \
--to=ruban.kumar@hughes.com \
--cc=users@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).