mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 17:00:24 +0300	[thread overview]
Message-ID: <1244728824.17483.51.camel@penberg-laptop> (raw)
In-Reply-To: <alpine.DEB.1.10.0906110941520.29827@gentwo.org>

Hi Christoph,

On Thu, 2009-06-11 at 09:43 -0400, Christoph Lameter wrote:
> We have had that with SLAB. NO! This leads to the situation that some
> slabs have debug on and some have not. You just do not know which.

I do see your point but surely we don't want to use order 1 allocations
in the fall-back case for kmalloc-4096? Couldn't we just add a printk
saying that debug was disabled for the cache? After all, my patch is
much better than what SLAB does.

On Thu, 2009-06-11 at 09:43 -0400, Christoph Lameter wrote:
> Note that CONFIG_SLUB_DEBUG only enables the code to debug a slab. It does
> not enable debugging for each slab. CONFIG_SLUB_DEBUG_ON does that.

True. Larry, do you have CONFIG_SLUB_DEBUG_ON enabled or are you passing
SLUB debugging options to the kernel?

			Pekka


  reply	other threads:[~2009-06-11 14:00 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 [this message]
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
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=1244728824.17483.51.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®