kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: linux-mm <linux-mm@kvack.org>,
	Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Estimating total memory usage in any Linux system
Date: Wed, 20 May 2020 00:01:22 -0400	[thread overview]
Message-ID: <21691.1589947282@turing-police> (raw)
In-Reply-To: <CAOuPNLip2spfFyzdjwVo467XYdBqKosxZE4q9u9MocGXR+Doew@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 582 bytes --]

On Tue, 19 May 2020 22:33:15 +0530, Pintu Agarwal said:

> > Below are some data taken from a small embedded arm32 device with 512MB RAM:
> >
>
> Sorry, I forgot to mention the kernel version. Here it is 3.18 Kernel

That's a kernel from 2014.  You don't seriously expect us to remember how
all those counters worked back then, do you?

That's a very real issue, not sarcasm:

[/usr/src/linux-next] git diff --shortstat v3.18..next-20200518
 76288 files changed, 15101441 insertions(+), 5417984 deletions(-)

You're asking about what the numbers meant 15 million lines of code ago.

[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2020-05-20  4:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18 17:57 Estimating total memory usage in any Linux system Pintu Agarwal
2020-05-19 17:03 ` Pintu Agarwal
2020-05-20  4:01   ` Valdis Klētnieks [this message]
2020-05-20  4:56     ` Pintu Agarwal
2020-05-20  5:32       ` Valdis Klētnieks
2020-05-20  6:11         ` Pintu Agarwal

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=21691.1589947282@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-mm@kvack.org \
    --cc=pintu.ping@gmail.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).