LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: clameter@engr.sgi.com
Cc: kamezawa.hiroyu@jp.fujitsu.com, andi@firstfloor.org,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: SLUB: The unqueued Slab allocator
Date: Fri, 23 Feb 2007 21:54:39 -0800 (PST)	[thread overview]
Message-ID: <20070223.215439.92580943.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0702232145340.1872@schroedinger.engr.sgi.com>

From: Christoph Lameter <clameter@engr.sgi.com>
Date: Fri, 23 Feb 2007 21:47:36 -0800 (PST)

> On Sat, 24 Feb 2007, KAMEZAWA Hiroyuki wrote:
> 
> > >From a viewpoint of a crash dump user, this merging will make crash dump
> > investigation very very very difficult.
> 
> The general caches already merge lots of users depending on their sizes. 
> So we already have the situation and we have tools to deal with it.

But this doesn't happen for things like biovecs, and that will
make debugging painful.

If a crash happens because of a corrupted biovec-256 I want to know
it was a biovec not some anonymous clone of kmalloc256.

Please provide at a minimum a way to turn the merging off.

I also agree with Andi in that merging could mess up how object type
local lifetimes help reduce fragmentation in object pools.


  reply	other threads:[~2007-02-24  5:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22  7:00 Christoph Lameter
2007-02-22  8:34 ` Peter Zijlstra
2007-02-22 15:25   ` Christoph Lameter
2007-02-22  8:58 ` David Miller
2007-02-22 15:26   ` Christoph Lameter
2007-02-22 10:49 ` Pekka Enberg
2007-02-22 15:15   ` Christoph Lameter
2007-02-22 17:54 ` Andi Kleen
2007-02-22 18:42   ` Christoph Lameter
2007-02-23  0:16     ` Andi Kleen
2007-02-23  4:55       ` Christoph Lameter
2007-02-24  5:28     ` KAMEZAWA Hiroyuki
2007-02-24  5:47       ` Christoph Lameter
2007-02-24  5:54         ` David Miller [this message]
2007-02-24 17:32           ` Christoph Lameter
2007-02-24 19:33             ` Jörn Engel
2007-02-25  0:14               ` Christoph Lameter
2007-02-25 12:23                 ` Jörn Engel
2007-02-25  0:53             ` David Miller

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=20070223.215439.92580943.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=clameter@engr.sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --subject='Re: SLUB: The unqueued Slab allocator' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).