From: Mike Fedyk <mfedyk@matchmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
MrChuoi <MrChuoi@yahoo.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.19-pre3-ac1
Date: Wed, 20 Mar 2002 21:11:01 -0800 [thread overview]
Message-ID: <20020321051101.GA2673@matchmail.com> (raw)
In-Reply-To: <20020319180417.GP2254@matchmail.com> <E16nOJF-0008Le-00@the-village.bc.nu> <20020319182933.GS2254@matchmail.com>
On Tue, Mar 19, 2002 at 10:29:33AM -0800, Mike Fedyk wrote:
> On Tue, Mar 19, 2002 at 06:26:09PM +0000, Alan Cox wrote:
> > > Is there any way (I don't thing so, but...) that KDE can affect this when
> > > there aren't any KDE processes running?
> >
> > Please try -ac2. It seems KDE just happens to be one of the triggers for
> > a bug where someone mremaps a partial vma larger and moves it.
>
> OK, will do.
>
Ok, did.
So far, after "up 1 day, 2:14" running a "while; make -j5" loop I haven't
seen my Committed_AS grow like before.
In multi user mode 116 processes running (with make -j loop):
total: used: free: shared: buffers: cached:
Mem: 129703936 117108736 12595200 0 3862528 58535936
Swap: 500056064 70832128 429223936
MemTotal: 126664 kB
MemFree: 12300 kB
MemShared: 0 kB
Buffers: 3772 kB
Cached: 24416 kB
SwapCached: 32748 kB
Active: 78996 kB
Inact_dirty: 18796 kB
Inact_clean: 1912 kB
Inact_target: 19940 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 126664 kB
LowFree: 12300 kB
SwapTotal: 488336 kB
SwapFree: 419164 kB
Committed_AS: 133840 kB
After:
total: used: free: shared: buffers: cached:
Mem: 129703936 76472320 53231616 0 8724480 54001664
Swap: 500056064 40960 500015104
MemTotal: 126664 kB
MemFree: 51984 kB
MemShared: 0 kB
Buffers: 8520 kB
Cached: 52696 kB
SwapCached: 40 kB
Active: 40848 kB
Inact_dirty: 16264 kB
Inact_clean: 5852 kB
Inact_target: 12592 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 126664 kB
LowFree: 51984 kB
SwapTotal: 488336 kB
SwapFree: 488296 kB
Committed_AS: 2228 kB
^^^^
This was down to ~500k before mutt was started.
init-+-bdflush
|-init---bash---bash-+-mutt---editor
| `-pstree
|-keventd
|-kjournald
|-ksoftirqd_CPU0
|-kswapd
|-kupdated
|-lockd
|-mdrecoveryd
`-rpciod
next prev parent reply other threads:[~2002-03-21 5:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 1:42 Linux 2.4.19-pre3-ac1 Alan Cox
2002-03-16 2:44 ` Mike Fedyk
2002-03-16 5:33 ` MrChuoi
2002-03-16 6:00 ` J Sloan
2002-03-16 7:52 ` MrChuoi
2002-03-16 17:30 ` Alan Cox
2002-03-16 17:50 ` MrChuoi
2002-03-16 18:00 ` Alan Cox
2002-03-16 19:14 ` MrChuoi
2002-03-16 20:58 ` Alan Cox
2002-03-17 5:36 ` Mike Fedyk
2002-03-17 23:52 ` Matthew D. Pitts
2002-03-18 0:01 ` Mike Fedyk
2002-03-18 3:02 ` MrChuoi
2002-03-18 3:01 ` Mike Fedyk
2002-03-18 3:03 ` Rik van Riel
2002-03-19 1:46 ` MrChuoi
2002-03-18 11:44 ` Alan Cox
2002-03-18 21:23 ` toon
2002-03-19 1:39 ` MrChuoi
2002-03-19 1:55 ` Alan Cox
2002-03-19 5:54 ` Zwane Mwaikambo
2002-03-19 6:20 ` Mike Fedyk
2002-03-19 6:46 ` Zwane Mwaikambo
2002-03-19 13:32 ` Alan Cox
2002-03-19 18:04 ` Mike Fedyk
2002-03-19 18:26 ` Alan Cox
2002-03-19 18:29 ` Mike Fedyk
2002-03-21 5:11 ` Mike Fedyk [this message]
2002-03-21 13:32 ` Alan Cox
2002-03-18 5:24 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2002-03-17 13:55 jarmo kettunen
2002-03-17 17:23 ` Alan Cox
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=20020321051101.GA2673@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=MrChuoi@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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