From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 89585A0471
	for <public@inbox.dpdk.org>; Wed, 17 Jul 2019 04:27:04 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id 0C1D32BBB;
	Wed, 17 Jul 2019 04:27:04 +0200 (CEST)
Received: from st43p00im-ztbu10063601.me.com (st43p00im-ztbu10063601.me.com
 [17.58.63.174]) by dpdk.org (Postfix) with ESMTP id B0894160
 for <dev@dpdk.org>; Wed, 17 Jul 2019 04:27:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com;
 s=1a1hai; t=1563330421;
 bh=hMeb2blAllrk3y60dvKXXou9TyBwTBw8vfdNb43URTI=;
 h=To:From:Subject:Date:Message-id:Content-Type;
 b=AccpmUM7wa6guP9SGrJMdLVRvHt0S/suZ2hjbhEt5Y+WgrIqIHKYX90WdukS1viS5
 I5SgSR3x9UkgUXscMbBIIII8ymKPRppBFlzUwDIoIT9Wi8vtpbl4QRG6Gaj55n1U0X
 RX7R/IDvQBorZ3gT3Zwct9NujJGB7CvwjORUdGMEytKOgejGSDKqlZxSzvQioEPShR
 XMraPyhyLPwOMlTp1Hc21Qu0PJfT3wly9y/xphCkPCoJMvTvvTYEoqcnL21tmtVNZr
 2QDNQumSt45oMHSMsf+vBebYLgzVMagYucnA8spGOxTzZ0v+mftmI9IYWTLuDwoJz6
 6WPb2jjdXADMA==
Received: from localhost (pv33p03im-webms003.me.com [17.142.224.114])
 by st43p00im-ztbu10063601.me.com (Postfix) with ESMTP id 84232700C64
 for <dev@dpdk.org>; Wed, 17 Jul 2019 02:27:01 +0000 (UTC)
To: dev@dpdk.org
From: He Peng <xnhp0320@icloud.com>
Date: Wed, 17 Jul 2019 02:26:57 GMT
X-Mailer: iCloud MailClient1912Project36
 MailServer1913B46.10000-1913B-0-be2a8866e288
Message-id: <fbe8b807-ccfa-43f6-838f-97ecdd1dde18@me.com>
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, ,
 definitions=2019-07-17_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=1
 malwarescore=0
 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 mlxscore=0
 mlxlogscore=320 adultscore=0 classifier=spam adjust=0 reason=mlx
 scancount=1 engine=8.0.1-1812120000 definitions=main-1907170028
Content-Type: text/plain;
    charset=utf-8;
    format=flowed
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] How *rte_zmalloc_socket* ensure that the memory is
	zero'd ?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi,=0A=0AIn file dpdk/lib/librte_eal/common/rte_malloc.c:=0A=0A/*=0A* Allo=
cate memory on default heap.=0A*/=0Avoid *=0Arte_malloc(const char *type, =
size_t size, unsigned align)=0A{=0A=C2=A0=C2=A0return rte_malloc_socket(ty=
pe, size, align, SOCKET_ID_ANY);=0A}=0A=0A/*=0A* Allocate zero'd memory on=
 specified heap.=0A*/=0Avoid *=0Arte_zmalloc_socket(const char *type, size=
_t size, unsigned align, int socket)=0A{=0A=C2=A0=C2=A0return rte_malloc_s=
ocket(type, size, align, socket);=0A}=0A=0ALooks like the *rte_malloc* and=
 *rte_zmalloc_socket* is the same, then, how the latter function ensure th=
e memory allocated by is zeroed?