From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Xueming Li <xuemingl@mellanox.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Anatoly Burakov <anatoly.burakov@intel.com>,
dev@dpdk.org, Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1] app/testpmd: add memory dump command
Date: Fri, 3 Apr 2020 09:08:52 -0700 [thread overview]
Message-ID: <20200403090852.29db0d1b@hermes.lan> (raw)
In-Reply-To: <9b130a91-7d0d-ba3d-a521-64829e34a28c@intel.com>
On Fri, 3 Apr 2020 14:29:06 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> > + socket_stats.heap_totalsz_bytes / 1.0e6,
> > + socket_stats.heap_allocsz_bytes / 1.0e6,
> > + (double)socket_stats.heap_allocsz_bytes * 100 /
> > + (double)socket_stats.heap_totalsz_bytes,
> > + socket_stats.heap_freesz_bytes / 1.0e6,
> > + socket_stats.alloc_count,
> > + socket_stats.free_count);
>
> This gives an output like [1], can you please divide to (1024*1024) to convert
> byte to Mb, than it can give more clear numbers.
Agree, the standard is to use 1024*1024 for memory megabytes.
And 1000*1000 for bytes in networking.
next prev parent reply other threads:[~2020-04-03 16:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 13:03 [dpdk-dev] [PATCH] " Xueming Li
2020-04-02 15:55 ` Ferruh Yigit
2020-04-03 6:53 ` [dpdk-dev] [PATCH v1] " Xueming Li
2020-04-03 6:53 ` Xueming Li
2020-04-03 13:29 ` Ferruh Yigit
2020-04-03 16:04 ` Stephen Hemminger
2020-04-03 16:08 ` Stephen Hemminger [this message]
2020-04-03 16:34 ` Morten Brørup
2020-04-05 2:49 ` [dpdk-dev] [PATCH v2] " Xueming Li
2020-04-05 2:49 ` Xueming Li
2020-04-07 9:21 ` Ferruh Yigit
2020-04-07 11:24 ` Xueming(Steven) Li
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=20200403090852.29db0d1b@hermes.lan \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=asafp@mellanox.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jingjing.wu@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=xuemingl@mellanox.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).