From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: SLUB: Support for statistics to help analyze allocator behavior
Date: Wed, 6 Feb 2008 00:19:48 -0800 [thread overview]
Message-ID: <20080206001948.6f749aa8.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0802042217460.6801@schroedinger.engr.sgi.com>
On Mon, 4 Feb 2008 22:20:04 -0800 (PST) Christoph Lameter <clameter@sgi.com> wrote:
> The statistics provided here allow the monitoring of allocator behavior
> at the cost of some (minimal) loss of performance. Counters are placed in
> SLUB's per cpu data structure that is already written to by other code.
Seems sane.
> The per cpu structure may be extended by the statistics to be more than
> one cacheline which will increase the cache footprint of SLUB.
>
> That is why there is a compile option to enable/disable the inclusion of
> the statistics module.
The compile-time optionality is really sad. But no obvious solution
suggests itself.
> @@ -1357,17 +1366,22 @@ static struct page *get_partial(struct k
> static void unfreeze_slab(struct kmem_cache *s, struct page *page, int tail)
> {
> struct kmem_cache_node *n = get_node(s, page_to_nid(page));
> + struct kmem_cache_cpu *c = get_cpu_slab(s, smp_processor_id());
So we're never running preemptibly here.
> ClearSlabFrozen(page);
> if (page->inuse) {
>
> - if (page->freelist != page->end)
> + if (page->freelist != page->end) {
> add_partial(n, page, tail);
> - else if (SlabDebug(page) && (s->flags & SLAB_STORE_USER))
> + stat(c, tail ? DEACTIVATE_TO_TAIL : DEACTIVATE_TO_HEAD);
> + } else {
> + stat(c, DEACTIVATE_FULL);
> + if (SlabDebug(page) && (s->flags & SLAB_STORE_USER))
> add_full(n, page);
missing a tab
> +#ifdef CONFIG_SLUB_STATS
> +
> +#define STAT_ATTR(si, text) \
> +static ssize_t text##_show(struct kmem_cache *s, char *buf) \
> +{ \
> + unsigned long sum = 0; \
> + int cpu; \
> + \
> + for_each_online_cpu(cpu) \
> + sum += get_cpu_slab(s, cpu)->stat[si]; \
maybe cache the get_cpu_slab() result in a local?
> + return sprintf(buf, "%lu\n", sum); \
> +} \
> +SLAB_ATTR_RO(text); \
this is pretty broken after cpu hot-unplug, isn't it?
--
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-06 8:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 6:20 Christoph Lameter
2008-02-05 7:24 ` Pekka J Enberg
2008-02-05 7:49 ` Eric Dumazet
2008-02-05 7:54 ` Pekka J Enberg
2008-02-05 18:08 ` Christoph Lameter
2008-02-05 18:55 ` Eric Dumazet
2008-02-05 19:07 ` Christoph Lameter
2008-02-05 18:05 ` Christoph Lameter
2008-02-05 20:20 ` Pekka Enberg
2008-02-05 21:58 ` Christoph Lameter
2008-02-05 22:19 ` Pekka J Enberg
2008-02-06 8:19 ` Andrew Morton [this message]
2008-02-06 19:01 ` Christoph Lameter
2008-02-06 21:00 ` SLUB: statistics improvements Christoph Lameter
2008-02-06 21:40 ` Eric Dumazet
2008-02-06 22:10 ` Christoph Lameter
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=20080206001948.6f749aa8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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