dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: He Peng <xnhp0320@icloud.com>
To: dev@dpdk.org
Subject: [dpdk-dev] How *rte_zmalloc_socket* ensure that the memory is zero'd ?
Date: Wed, 17 Jul 2019 02:26:57 GMT	[thread overview]
Message-ID: <fbe8b807-ccfa-43f6-838f-97ecdd1dde18@me.com> (raw)

Hi,

In file dpdk/lib/librte_eal/common/rte_malloc.c:

/*
* Allocate memory on default heap.
*/
void *
rte_malloc(const char *type, size_t size, unsigned align)
{
  return rte_malloc_socket(type, size, align, SOCKET_ID_ANY);
}

/*
* Allocate zero'd memory on specified heap.
*/
void *
rte_zmalloc_socket(const char *type, size_t size, unsigned align, int socket)
{
  return rte_malloc_socket(type, size, align, socket);
}

Looks like the *rte_malloc* and *rte_zmalloc_socket* is the same, then, how the latter function ensure the memory allocated by is zeroed?

             reply	other threads:[~2019-07-17  2:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17  2:26 He Peng [this message]
2019-07-17  4:51 ` [dpdk-dev] How *rte_zmalloc_socket* ensure that the memory is zero'd ? Stephen Hemminger
2019-07-17  5:19 He Peng
2019-07-17  5:22 He Peng

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=fbe8b807-ccfa-43f6-838f-97ecdd1dde18@me.com \
    --to=xnhp0320@icloud.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).