From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: michael@ucc.gu.uwa.edu.au, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12-rc2: >100% memory usage
Date: Fri, 15 Apr 2005 15:23:42 +1000 [thread overview]
Message-ID: <1113542622.6517.25.camel@npiggin-nld.site> (raw)
In-Reply-To: <20050414222024.059f7aa9.rddunlap@osdl.org>
On Thu, 2005-04-14 at 22:20 -0700, Randy.Dunlap wrote:
> On Fri, 15 Apr 2005 14:59:05 +1000 Nick Piggin wrote:
>
> | On Fri, 2005-04-15 at 12:48 +0800, Michael Deegan wrote:
> | > Hi folks,
> | >
> | > I noticed something unusual on my home desktop machine (K6II, 448M RAM, runs
> | > KDE, samba, nfsd. 2.6.12-rc2 on Debian sarge). The machine seems to feel
> | > slightly sluggish; it seems to swap a fair bit more than it did under
> | > 2.6.11, but at the same time it's not actually using more swap that it used
> | > to. The large numbers are slowly growing larger too. The biggest spamd was
> | > only 156% of memory yesterday. Normally it's only my xserver (and
> | > occasionally konqueror) that manages to grab more than 10% of memory...
> |
> | FWIW, me too :P
> |
> | I think there is a memory leak in recent 2.6.12 kernels.
> | At least on my desktop there is (although it has some of
> | my own patches and I've been too lazy to do more work on
> | it so I haven't reported it).
> |
> | It seems to be leaking `size-4096` slabs somewhere.
>
> This one or yet another one?
> http://marc.theaimsgroup.com/?l=linux-kernel&m=111264601928365&w=2
>
>
No, another one. Much faster. A few kernel compiles and I have
to reboot (only 256MB RAM, though).
But as I said, not quite a vanilla kernel. I'll have to get
motivated and compile a plain one and try to work it out. I
was hoping someone else would do it ;)
prev parent reply other threads:[~2005-04-15 5:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 4:48 Michael Deegan
2005-04-15 4:59 ` Nick Piggin
2005-04-15 5:20 ` Randy.Dunlap
2005-04-15 5:23 ` Nick Piggin [this message]
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=1113542622.6517.25.camel@npiggin-nld.site \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ucc.gu.uwa.edu.au \
--cc=rddunlap@osdl.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
all inboxes | Powered by JetHome®