From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, mel@csn.ul.ie, Larry.Finger@lwfinger.net
Subject: Re: [PATCH 2/2] SLUB: Disable debugging if it increases the minimum page order
Date: Thu, 11 Jun 2009 18:28:06 +0300 [thread overview]
Message-ID: <1244734086.17483.59.camel@penberg-laptop> (raw)
In-Reply-To: <alpine.DEB.1.10.0906111118350.14020@gentwo.org>
Hi Christoph,
On Thu, 11 Jun 2009, Pekka Enberg wrote:
> > I think my patch is the simplest solution here: it turns off debugging
> > for those caches where the metadata bumps up the minimum allocation
> > order and I suspect that we disable cache only for 4096 in practice.
On Thu, 2009-06-11 at 11:20 -0400, Christoph Lameter wrote:
> There could be other slab caches that would randomly be affected by this.
> I ran a couple of times into situations where I had to hack slab to do
> debugging of exempted slabs.
Yes, I do understand that and I have hit that too in the past. But
surely a printk() telling the user we disabled debugging can cure that?
My main point is that a lot of _testers_ will probably enable all SLUB
debugging by default because we encourage them to and it's pretty bad
that we end up causing order 1 allocations and oom conditions.
So I still think we need to fix _at minimum_ the kmalloc-4096 case
(assuming Larry won't hit the same problem still). I see you're not
happy with my patch so any suggestions how to handle that?
Pekka
next prev parent reply other threads:[~2009-06-11 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 8:44 Pekka J Enberg
2009-06-11 13:43 ` Christoph Lameter
2009-06-11 14:00 ` Pekka Enberg
2009-06-11 14:24 ` Christoph Lameter
2009-06-11 15:11 ` Pekka Enberg
2009-06-11 15:20 ` Christoph Lameter
2009-06-11 15:28 ` Pekka Enberg [this message]
2009-06-11 15:49 ` Christoph Lameter
2009-06-11 16:49 ` Larry Finger
2009-06-11 18:04 ` Mel Gorman
2009-06-11 18:26 ` Christoph Lameter
2009-06-11 19:16 ` Mel Gorman
2009-06-11 14:39 ` Larry Finger
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=1244734086.17483.59.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=Larry.Finger@lwfinger.net \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
/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®