DPDK usage discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: wangyunjian <wangyunjian@huawei.com>,
	"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Cc: Feifei Wang <Feifei.Wang2@arm.com>,
	Ruifeng Wang <Ruifeng.Wang@arm.com>,
	Huangshaozhang <huangshaozhang@huawei.com>,
	dingxiaoxiong <dingxiaoxiong@huawei.com>,
	Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	nd <nd@arm.com>
Subject: RE: [dpdk-dev][dpdk-users] A problem about  memory may not be all-zero allocated by rte_zmalloc_socket()
Date: Mon, 31 Jan 2022 04:21:57 +0000	[thread overview]
Message-ID: <DBAPR08MB58145AE8598C5B3E38A91AF298259@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <61c1d85e0f8a42d4812830864fc59b0a@huawei.com>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

Hi Yunjian,
                That's interesting. Is it possible to elaborate the use case or possibly provide the code snippet?

It is possible that it is a synchronization problem due to relaxed memory model that Arm architecture uses. There could be a barrier missing in the code.

Thanks,
Honnappa

From: wangyunjian <wangyunjian@huawei.com>
Sent: Saturday, January 29, 2022 9:21 PM
To: dev@dpdk.org; users@dpdk.org
Cc: Feifei Wang <Feifei.Wang2@arm.com>; Ruifeng Wang <Ruifeng.Wang@arm.com>; Huangshaozhang <huangshaozhang@huawei.com>; dingxiaoxiong <dingxiaoxiong@huawei.com>
Subject: [dpdk-dev][dpdk-users] A problem about memory may not be all-zero allocated by rte_zmalloc_socket()

Hi, all

There's a problem that the memory are allocated by rte_zmalloc_socket()
may not be all-zero on the ARM platform.

However, the x86 platform does not have this problem.


Any ideas ?


Thanks,

Yunjian


[-- Attachment #2: Type: text/html, Size: 5006 bytes --]

  reply	other threads:[~2022-01-31  4:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-30  3:21 wangyunjian
2022-01-31  4:21 ` Honnappa Nagarahalli [this message]
2022-02-07  2:43   ` wangyunjian
2022-02-08  8:01   ` wangyunjian
2022-02-08 18:05     ` Honnappa Nagarahalli
2022-02-10 12:11       ` wangyunjian
2022-02-22  9:17         ` Ruifeng Wang
2022-02-23 11:22           ` wangyunjian
2022-02-23 15:38             ` Honnappa Nagarahalli
2023-04-12 17:35               ` Stephen Hemminger

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=DBAPR08MB58145AE8598C5B3E38A91AF298259@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Feifei.Wang2@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=dev@dpdk.org \
    --cc=dingxiaoxiong@huawei.com \
    --cc=huangshaozhang@huawei.com \
    --cc=nd@arm.com \
    --cc=users@dpdk.org \
    --cc=wangyunjian@huawei.com \
    /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).