public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	"nmeyers@vestmark.com" <nmeyers@vestmark.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Major slab mem leak with 2.6.17 / GCC 4.1.1
Date: Mon, 16 Oct 2006 05:32:32 +0000	[thread overview]
Message-ID: <1160976752.6477.3.camel@Homer.simpson.net> (raw)
In-Reply-To: <1160899154.5935.19.camel@Homer.simpson.net>

On Sun, 2006-10-15 at 07:59 +0000, Mike Galbraith wrote:

> 2.6.19-rc1 + patch-2.6.19-rc1-kmemleak-0.11 compiles fine now (unless
> CONFIG_DEBUG_KEEP_INIT is set), boots and runs too.. but axle grease
> runs a lot faster ;-)  I'll try a stripped down config sometime.

My roughly three orders of magnitude (amusing to watch:) boot slowdown
turned out to be stack unwinding.  With CONFIG_UNWIND_INFO disabled,
2.6.19-rc2 + patch-2.6.19-rc1-kmemleak-0.11 runs just fine.

	-Mike


  parent reply	other threads:[~2006-10-16  5:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13  0:49 Major slab mem leak with 2.6.17 / GCC 4.1.1 nmeyers
2006-10-13  5:56 ` Pekka Enberg
2006-10-13 11:59   ` Catalin Marinas
2006-10-15  7:59     ` Mike Galbraith
2006-10-15 14:14       ` nmeyers
2006-10-15 17:59         ` Mike Galbraith
2006-10-18 13:59           ` Nathan Meyers
2006-10-16  5:32       ` Mike Galbraith [this message]
2006-10-16  8:07         ` Catalin Marinas
2006-10-16  9:08           ` Mike Galbraith
2006-10-16  8:44             ` Catalin Marinas
2006-10-16  9:33               ` Mike Galbraith
2006-10-13  8:25 ` Mike Galbraith
2006-10-13 10:55   ` nmeyers
2006-10-13 21:28     ` Mike Galbraith

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=1160976752.6477.3.camel@Homer.simpson.net \
    --to=efault@gmx.de \
    --cc=catalin.marinas@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nmeyers@vestmark.com \
    --cc=penberg@cs.helsinki.fi \
    /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