DPDK patches and discussions
 help / color / mirror / Atom feed
From: P Smith <dpdk_learn-dev@yahoo.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Memory footprint of a PMD
Date: Fri, 3 May 2019 09:37:22 +0000 (UTC)	[thread overview]
Message-ID: <899934402.3791304.1556876242992@mail.yahoo.com> (raw)
In-Reply-To: <899934402.3791304.1556876242992.ref@mail.yahoo.com>

Hi,     Given that a dpdk driver uses rte_malloc_xx() and friends to allocate/free its memory what is the best way to find out the runtime memory footprint of a PMD ? One can use 'malloc_info' to dump the malloc output in case of general 'malloc' ...but what is the way here since it's all hugepages ? How to know the memory /footprint of my testpmd /application at different points during run-time?Is there a tool or some API i can invoke to find out the same?
Thanks P

       reply	other threads:[~2019-05-03  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <899934402.3791304.1556876242992.ref@mail.yahoo.com>
2019-05-03  9:37 ` P Smith [this message]
2019-05-03  9:37   ` P Smith
2019-05-03 10:02   ` Burakov, Anatoly
2019-05-03 10:02     ` Burakov, Anatoly
2019-05-03 19:03     ` Stephen Hemminger
2019-05-03 19:03       ` 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=899934402.3791304.1556876242992@mail.yahoo.com \
    --to=dpdk_learn-dev@yahoo.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).