From: Hugh Dickins <hugh@veritas.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Matt Mackall <mpm@selenic.com>,
linux-mm@kvack.org
Subject: Re: [patch 05/10] slub: Remove slub_nomerge
Date: Fri, 29 Feb 2008 14:01:20 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0802291327490.11617@blonde.site> (raw)
In-Reply-To: <20080229043552.282285411@sgi.com>
On Thu, 28 Feb 2008, Christoph Lameter wrote:
> No one has used that option for a long time and AFAICT its currently utterly
> useless.
Not so at all. I certainly use it: not often, but from time to time,
in debugging. If you're narrowing down on something, it's a worthwhile
tool to separate the different uses of a particular size.
And when studying slabinfo numbers, perhaps for a leak e.g. why doesn't
slabinfo doesn't show vm_area_struct, oh, it's sharing :0000088 with
cfq_queue, so we need slub_nomerge to see their actual numbers.
Perhaps I'm missing something: how does everyone else get the
right numbers without slub_nomerge?
Admittedly it's often too blunt an instrument for debugging: I'd be
happier with a debug flag which has no other side-effect than nomerge
(all the other SLUB_NEVER_MERGE flags seemed to have side-effects that
I wanted to avoid when trying to reproduce an elusive corruption),
that can be applied to a single cache as well as to the whole lot.
I could add that if you don't (or I could hack my mm/slub.c when
I need to, that's always an option: but I do think nomerge can be
useful out in the field). If you go ahead and remove slub_nomerge,
please also remove it from Documentation/kernel-parameters.txt.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-29 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080229043401.900481416@sgi.com>
[not found] ` <20080229043552.282285411@sgi.com>
2008-02-29 7:21 ` [patch 05/10] slub: Remove slub_nomerge Pekka Enberg
2008-02-29 14:01 ` Hugh Dickins [this message]
2008-02-29 19:48 ` Christoph Lameter
[not found] ` <20080229043553.284904576@sgi.com>
2008-02-29 7:29 ` [patch 09/10] slub: Rearrange #ifdef CONFIG_SLUB_DEBUG in calculate_sizes() Pekka Enberg
2008-02-29 19:31 ` Christoph Lameter
[not found] ` <20080229043552.523817079@sgi.com>
2008-02-29 7:37 ` [patch 06/10] slub: Use the objsize from the kmem_cache_cpu structure Pekka Enberg
[not found] ` <20080229043553.076119937@sgi.com>
2008-02-29 7:45 ` [patch 08/10] slub: Remove BUG_ON() from ksize and omit checks for !SLUB_DEBUG Pekka Enberg
2008-02-29 19:34 ` Christoph Lameter
2008-03-01 9:59 ` Pekka J Enberg
[not found] ` <20080229043552.749815166@sgi.com>
2008-02-29 7:46 ` [patch 07/10] slub: Add kmalloc_large_node() to support kmalloc_node fallback Pekka Enberg
[not found] ` <20080229043552.047548372@sgi.com>
2008-02-29 7:54 ` [patch 04/10] slub: Remove useless checks in alloc_debug_processing Pekka Enberg
[not found] ` <20080229043551.868567605@sgi.com>
2008-02-29 8:00 ` [patch 03/10] slub: Remove objsize check in kmem_cache_flags() Pekka Enberg
[not found] ` <20080229043551.357047304@sgi.com>
2008-02-29 8:05 ` [patch 01/10] Revert "unique end pointer" patch Pekka Enberg
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=Pine.LNX.4.64.0802291327490.11617@blonde.site \
--to=hugh@veritas.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.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;
as well as URLs for NNTP newsgroup(s).