public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: 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: Tue, 19 Mar 2002 10:04:17 -0800	[thread overview]
Message-ID: <20020319180417.GP2254@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0203190753140.25412-100000@netfinity.realnet.co.sz> <E16nJin-0007iU-00@the-village.bc.nu>

On Tue, Mar 19, 2002 at 01:32:13PM +0000, Alan Cox wrote:
> > actually been *allocated* as per requests, but not necesserily in use? 
> > This one is my home box, looks a bit crazy don't you think? The box has 
> 
> Yes
> 
> > about ~120 processes right now, heavy X session (2000x2000@32 virtual, 
> > KDE2 with lots of eye candy), two kernel builds in the background and 
> > cdrecord. 
> 
> I'm chasing a leak or two somewhere. One common theme seems to be KDE so
> my guess is there is something like an mprotect/mremap/shared page path that
> isnt correctly accounted and kde triggers more than most other stuff (eg
> because of the strange way KDE execs new processes). 
> 
> Last night I added some validator code for the non shmfs cases to see if
> I can find it. 

Hmm, you must have missed my report I sent to you earlier.

After a fresh reboot, I booted into the console (no X/kde started) and ran the
while looped kernel compile for a couple days.  Then I switched to single
user mode to see if the address space was recovered, but it was not.

Is there any way (I don't thing so, but...) that KDE can affect this when
there aren't any KDE processes running?

Mike

  reply	other threads:[~2002-03-19 18:03 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 [this message]
2002-03-19 18:26                             ` Alan Cox
2002-03-19 18:29                               ` Mike Fedyk
2002-03-21  5:11                                 ` Mike Fedyk
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=20020319180417.GP2254@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