From: Mike Fedyk <mfedyk@matchmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Mem: and Swap: lines in /proc/meminfo
Date: Thu, 11 Dec 2003 15:05:11 -0800 [thread overview]
Message-ID: <20031211230511.GI15401@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312111741150.15419-100000@chimarrao.boston.redhat.com>
On Thu, Dec 11, 2003 at 05:42:46PM -0500, Rik van Riel wrote:
> On Thu, 11 Dec 2003, Mike Fedyk wrote:
>
> > Inact_dirty: 21516 kB
> > Inact_laundry: 65612 kB
> > Inact_clean: 19812 kB
> >
> > These three are seperate lists in rmap, and are equal to "Inactive:" in
> > the -aa vm.
>
> I should add an Inactive: list to -rmap that sums up all
> 3, to make it a bit easier on programs parsing /proc.
>
ISTR, asking for this a while ago ;)
Yes, please do add that Inactive: line to rmap. :)
> Note that the inactive clean pages count (more or less)
> as free pages, too.
>
But I should count it as "Inactive" right?
So, if it's clean, then the page has already been zeroed out, and is ready
to be used but just needs some flags updated? Or they contain possibly
useful data, and just are not dirty? So a page that is inactive, but not
dirty will go directly in that list?
What can happen to Inact_clean pages besides being freed, and used on the
free memory list?
> > Inact_target: 150080 kB
> >
> > This doesn't account any memory, but is only what the VM is trying to size
> > the sum of the three lists above.
> >
> > Do I have that right?
>
> Yes, you're completely right.
Great. :)
next prev parent reply other threads:[~2003-12-11 23:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 0:00 Mem: and Swap: lines in /proc/meminfo Mike Fedyk
2003-12-11 22:02 ` Rik van Riel
2003-12-11 22:23 ` Mike Fedyk
2003-12-11 22:42 ` Rik van Riel
2003-12-11 23:05 ` Mike Fedyk [this message]
2003-12-12 0:41 ` shm Rob Roschewsk
2003-12-12 0:43 ` shm Rob Roschewsk
2003-12-12 0:44 ` shm Rob Roschewsk
2003-12-12 0:45 ` shm Rob Roschewsk
2003-12-12 12:00 ` Mem: and Swap: lines in /proc/meminfo Rik van Riel
2003-12-12 18:12 ` Mike Fedyk
2003-12-13 3:23 ` More questions about 2.6 /proc/meminfo was: (Mem: and Swap: lines in /proc/meminfo) Mike Fedyk
2003-12-13 17:54 ` Rik van Riel
2003-12-14 1:44 ` Mike Fedyk
2003-12-15 0:17 ` Rik van Riel
2003-12-15 18:57 ` Mike Fedyk
2003-12-15 19:40 ` edjard
2003-12-15 21:57 ` Mike Fedyk
2003-12-16 4:10 ` Calculating total slab memory on 2.2/2.0 (was: More questions about 2.6 /proc/meminfo was: (Mem: and Swap: lines in /proc/meminfo)) Mike Fedyk
2003-12-16 20:07 ` Re: Re: More questions about 2.6 /proc/meminfo was: (Mem: and Swap: lines in /proc/meminfo) edjard
2003-12-17 1:12 ` [PATCH 2.4 Rmap] Add Inactive to /proc/meminfo was: Mem: and Swap: lines in /proc/meminfo Mike Fedyk
2003-12-17 3:59 ` Rik van Riel
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=20031211230511.GI15401@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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