From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: what is using memory?
Date: Sun, 10 Jun 2001 23:36:42 -0400 [thread overview]
Message-ID: <01061023364200.03146@oscar> (raw)
I have been trying to figure out what is using my memory
My box has
320280K
>From boot I see
924 kernel
8224 reserved (initrd ramdisk?)
1488 hash tables (dentry, inode, mount, buffer, page, tcp)
from lsmod I caculate
876 for loaded modules
from proc/slabinfo
11992 for all slabs
from proc/meminfo
17140 buffer
123696 cache
32303 free
leaving unaccounted
123627K
This is about 38% of my memory, and only about 46% is pageable
Is it possible to figure out what is using this?
This is with 2.4.6-pre2 with Rik's page_launder_improvements patch,
lvm beta7 and some reieserfs patches applied, after about 12 hours
of uptime.
TIA,
Ed Tomlinson
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next reply other threads:[~2001-06-11 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 3:36 Ed Tomlinson [this message]
2001-06-11 8:20 ` Jonathan Morton
2001-06-11 11:37 ` Ed Tomlinson
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=01061023364200.03146@oscar \
--to=tomlins@cam.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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