All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:23:11 -0800	[thread overview]
Message-ID: <20031211222311.GH15401@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312111701330.15419-100000@chimarrao.boston.redhat.com>

On Thu, Dec 11, 2003 at 05:02:01PM -0500, Rik van Riel wrote:
> On Mon, 8 Dec 2003, Mike Fedyk wrote:
> 
> > Now I need to change the order (it is using Mem: and Swap: first, and the
> > other more thurough method second), but I'm wondering what versions of the
> > kernel I'd be cutting out if I just removed the parsing of Mem: and Swap:...
> 
> IIRC 2.2 kernels already had the one-value-per-line
> memory statistics, so you'd only lose 2.0 and earlier.

Ahh, great.  I'll change the ordering.  Should help clean up the code a bit
and make adding the features I want easier. :)

Another question:

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.

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?

I'm going to graph active and inactive for lrrd, and I need to know how to
map the different values when it is run on a rmap kernel.

Thanks.

  reply	other threads:[~2003-12-11 22:23 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 [this message]
2003-12-11 22:42     ` Rik van Riel
2003-12-11 23:05       ` Mike Fedyk
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=20031211222311.GH15401@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 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.