From: Con Kolivas <conman@kolivas.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] vm swappiness with contest
Date: Tue, 31 Dec 2002 17:57:50 +1100 [thread overview]
Message-ID: <200212311757.50916.conman@kolivas.net> (raw)
In-Reply-To: <3E113B25.534BEBE4@digeo.com>
On Tuesday 31 Dec 2002 5:37 pm, Andrew Morton wrote:
> Con Kolivas wrote:
> > On Tuesday 31 Dec 2002 5:08 pm, Andrew Morton wrote:
> > > Con Kolivas wrote:
> > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > Hash: SHA1
> > > >
> > > > On Saturday 28 Dec 2002 5:16 pm, Con Kolivas wrote:
> > > > > Is there something about the filesystem layer or elsewhere in the
> > > > > kernel that could decay or fragment over time that only a reboot
> > > > > can fix? This would seem to be a bad thing.
> > > >
> > > > Ok Linus suggested I check slabinfo before and after.
> > > >
> > > > I ran contest for a few days till I recreated the problem and it did
> > > > recur. I don't know how to interpret the information so I'll just
> > > > dump it here:
> > >
> > > Looks OK. Could we see /proc/meminfo and /proc/vmstat?
> >
> > meminfo:
> > MemTotal: 257296 kB
> > MemFree: 47468 kB
> > Buffers: 27028 kB
> > Cached: 7480 kB
> > SwapCached: 272 kB
> > Active: 154968 kB
> > Inactive: 42756 kB
> > HighTotal: 0 kB
> > HighFree: 0 kB
> > LowTotal: 257296 kB
> > LowFree: 47468 kB
> > SwapTotal: 4194272 kB
> > SwapFree: 4193816 kB
> > Dirty: 1116 kB
> > Writeback: 0 kB
> > Mapped: 3740 kB
> > Slab: 8564 kB
> > Committed_AS: 6580 kB
> > PageTables: 196 kB
> > ReverseMaps: 1381
>
> These numbers _look_ wrong, but ext3 truncate does funny things.
> Could you now run a big usemem/fillmem application to try to allocate and
> use 200 megs of memory, then resend /proc/meminfo?
post usemem:
MemTotal: 257296 kB
MemFree: 86168 kB
Buffers: 392 kB
Cached: 2244 kB
SwapCached: 632 kB
Active: 159484 kB
Inactive: 1380 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 257296 kB
LowFree: 86168 kB
SwapTotal: 4194272 kB
SwapFree: 4192668 kB
Dirty: 60 kB
Writeback: 0 kB
Mapped: 1768 kB
Slab: 6748 kB
Committed_AS: 6588 kB
PageTables: 196 kB
ReverseMaps: 619
Con
next prev parent reply other threads:[~2002-12-31 6:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 5:46 [BENCHMARK] vm swappiness with contest Con Kolivas
2002-12-27 10:00 ` Con Kolivas
2002-12-28 6:16 ` Con Kolivas
2002-12-28 6:26 ` Andrew Morton
2002-12-28 8:05 ` Linus Torvalds
2002-12-31 5:58 ` Con Kolivas
2002-12-31 6:08 ` Andrew Morton
2002-12-31 6:24 ` Con Kolivas
2002-12-31 6:37 ` Andrew Morton
2002-12-31 6:57 ` Con Kolivas [this message]
2002-12-31 7:08 ` Andrew Morton
2002-12-31 7:20 ` Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2002-12-27 13:13 Paolo Ciarrocchi
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=200212311757.50916.conman@kolivas.net \
--to=conman@kolivas.net \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.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