From: Mike Fedyk <mfedyk@matchmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: More questions about 2.6 /proc/meminfo was: (Mem: and Swap: lines in /proc/meminfo)
Date: Mon, 15 Dec 2003 10:57:01 -0800 [thread overview]
Message-ID: <20031215185701.GC1769@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0312141915550.26386-100000@chimarrao.boston.redhat.com>
On Sun, Dec 14, 2003 at 07:17:05PM -0500, Rik van Riel wrote:
> On Sat, 13 Dec 2003, Mike Fedyk wrote:
>
> > > > Are Dirty: and Writeback: counted in Inactive: or are they seperate?
> > >
> > > They're unrelated statistics to active/inactive and will
> > > overlap with active/inactive.
> >
> > Do they count anonymous memory, or are they strictly dirty/writeback
> > pagecache?
>
> Pagecache only, I think.
>
That makes sence, since dirty anonymous memory should be swapped out, not
"written back".
Though dirty seems anbiguous, since it could contain dirty anon memory too.
But, I think you are right. On my idle system (with kde running), there's
only 40KB "dirty" memory, so it's probably pagecache only.
Thanks.
> > > > Does Mapped: include all files mmap()ed, or only the executable ones?
> > >
> > > Mapped: includes all mmap()ed pages, regardless of executable
> > > status.
> >
> > Is mmap() always pagecache backed, or can it be backed with anonymous
> > memory? IE, can I subtract mapped from pagecache?
>
> Mapped includes all mapped memory, both pagecache and
> anonymous.
>
Ok, then I can't subtract it from the pagecache value. I'll have to graph
that differently (a line instead of a stack).
Thanks.
> > I'd love to find a more accurate way to get the amount of memory used for
> > apps, short of reading the output of ps and doing calculations on RSS,
> > VIRTUAL, and SHARED...
>
> That would be great, it would really help with tuning
> the VM further (if that turns out to be needed for
> special workloads).
Any suggestions?
next prev parent reply other threads:[~2003-12-15 18:57 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
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 [this message]
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=20031215185701.GC1769@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