From: Ed Tomlinson <tomlins@cam.org>
To: Jonathan Morton <chromi@cyberspace.org>,
Ed Tomlinson <tomlins@cam.org>,
linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: what is using memory?
Date: Mon, 11 Jun 2001 07:37:46 -0400 [thread overview]
Message-ID: <01061107374601.06951@oscar> (raw)
In-Reply-To: <l03130300b74a2f8d4db6@[192.168.239.105]>
In-Reply-To: <l03130300b74a2f8d4db6@[192.168.239.105]>
On Monday 11 June 2001 04:20, Jonathan Morton wrote:
> >My box has
> >
> >320280K
> >
> >from proc/meminfo
> >
> > 17140 buffer
> >123696 cache
> > 32303 free
> >
> >leaving unaccounted
> >
> >123627K
>
> This is your processes' memory, the inode and dentry caches, and possibly
> some extra kernel memory which may be allocated after boot time. It is
> *very* much accounted for.
No its not. For instance the slab caches encompass the inode and dentry
caches. Point I was/am tring to make is not that this memory is lost or
not need, but that is it _not_ accounted. ie. There is not way to tell
what is using it, hense we cannot see leaks or places that could be
optimized.
I have attempted to count all memory I could. The 123M is what is left in
the kernel overhead bucket...
Ed Tomlinson
WARNING: multiple messages have this Message-ID (diff)
From: Ed Tomlinson <tomlins@cam.org>
To: Jonathan Morton <chromi@cyberspace.org>,
Ed Tomlinson <tomlins@CAM.ORG>,
linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org
Subject: Re: what is using memory?
Date: Mon, 11 Jun 2001 07:37:46 -0400 [thread overview]
Message-ID: <01061107374601.06951@oscar> (raw)
In-Reply-To: <l03130300b74a2f8d4db6@[192.168.239.105]>
On Monday 11 June 2001 04:20, Jonathan Morton wrote:
> >My box has
> >
> >320280K
> >
> >from proc/meminfo
> >
> > 17140 buffer
> >123696 cache
> > 32303 free
> >
> >leaving unaccounted
> >
> >123627K
>
> This is your processes' memory, the inode and dentry caches, and possibly
> some extra kernel memory which may be allocated after boot time. It is
> *very* much accounted for.
No its not. For instance the slab caches encompass the inode and dentry
caches. Point I was/am tring to make is not that this memory is lost or
not need, but that is it _not_ accounted. ie. There is not way to tell
what is using it, hense we cannot see leaks or places that could be
optimized.
I have attempted to count all memory I could. The 123M is what is left in
the kernel overhead bucket...
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 prev parent reply other threads:[~2001-06-11 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-11 3:36 what is using memory? Ed Tomlinson
2001-06-11 3:36 ` Ed Tomlinson
2001-06-11 8:20 ` Jonathan Morton
2001-06-11 8:20 ` Jonathan Morton
2001-06-11 11:37 ` Ed Tomlinson [this message]
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=01061107374601.06951@oscar \
--to=tomlins@cam.org \
--cc=chromi@cyberspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.