From: Dave Jones <davej@redhat.com>
To: Kirill Korotaev <dev@sw.ru>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Muli Ben-Yehuda" <muli@il.ibm.com>,
"Björn Steinbrink" <B.Steinbrink@gmx.de>,
linux-kernel@vger.kernel.org, dev@openvz.org, stable@kernel.org
Subject: Re: + sys_getppid-oopses-on-debug-kernel.patch added to -mm tree
Date: Wed, 9 Aug 2006 13:38:30 -0400 [thread overview]
Message-ID: <20060809173830.GA10930@redhat.com> (raw)
In-Reply-To: <44D99901.20202@sw.ru>
On Wed, Aug 09, 2006 at 12:12:49PM +0400, Kirill Korotaev wrote:
> > > >>Even without getting into just how ugly this is, is it really worth
> > > >>it?
> > > it is impossible to run debug kernels w/o this patch :/
> > > or are you asking whether this optimization worth it?
> > >
> > > What makes me worry is that this is a sign that vendors
> > > don't even bother to run debug kernels :((((
> >
> > Fedora rawhide is nearly always shipping with DEBUG_SLAB enabled,
> > and we didn't hit this once. Are you sure this is a problem
> > with DEBUG_SLAB, and not DEBUG_PAGEALLOC ?
> Sorry, it's my fault. Surely, CONFIG_DEBUG_PAGEALLOC.
Then you're correct, vendors rarely turn this on :)
I do sometimes if I'm trying to chase down something particularly
difficult, and it usually gets me a bunch of mail from users
asking why 'everything got all slow', so it's a last-resort option
rather than a 'on all the time' option.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-09 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200608081432.k78EWprf007511@shell0.pdx.osdl.net>
2006-08-08 14:39 ` + sys_getppid-oopses-on-debug-kernel.patch added to -mm tree Muli Ben-Yehuda
2006-08-08 14:51 ` Björn Steinbrink
2006-08-08 14:57 ` Muli Ben-Yehuda
2006-08-08 15:22 ` Alan Cox
2006-08-08 15:39 ` Kirill Korotaev
2006-08-08 16:36 ` Dave Jones
2006-08-09 8:12 ` Kirill Korotaev
2006-08-09 17:38 ` Dave Jones [this message]
2006-08-10 9:35 ` Kirill Korotaev
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=20060809173830.GA10930@redhat.com \
--to=davej@redhat.com \
--cc=B.Steinbrink@gmx.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dev@openvz.org \
--cc=dev@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=muli@il.ibm.com \
--cc=stable@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