From: "Jarrett L. Redd" <jredd@cisco.com>
To: linux-kernel@vger.kernel.org
Subject: /proc/meminfo behaviour...
Date: Wed, 15 Jan 2003 16:32:12 -0800 [thread overview]
Message-ID: <3E25FD8C.1030103@cisco.com> (raw)
Guys, is this normal?
# head -2 /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 193830912 76816384 117014528 0 425984 72572928
^^^^^^^^^
# sleep 1
# head -2 /proc/meminfo
total: used: free: shared: buffers: cached:
Mem: 193830912 76869632 116961280 0 430080 72609792
^^^^^^^^^
#
This is on a PC with no swap and no disk, booting off an initrd stored
on a compact flash. I can understand that while sleep is running, the
amount of free memory is reduced. Why does the number stay reduced even
after it is done running? No matter how long you wait, the number never
comes back up. Is the memory really gone or is there something I don't
understand about /proc/meminfo? Or does this have something to do with
the ramdisk? Thanks.
-Jarrett Redd
reply other threads:[~2003-01-16 0:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E25FD8C.1030103@cisco.com \
--to=jredd@cisco.com \
--cc=linux-kernel@vger.kernel.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