linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: Pekka Enberg <penberg@kernel.org>,
	Christoph Lameter <cl@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH/RFC] MM slub: add a sysfs entry to show the calculated number of fallback slabs
Date: Fri, 12 Nov 2010 10:46:51 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1011121043250.5830@chino.kir.corp.google.com> (raw)
In-Reply-To: <1289561309.1972.30.camel@castor.rsk>

On Fri, 12 Nov 2010, Richard Kennedy wrote:

> Add a slub sysfs entry to show the calculated number of fallback slabs.
> 
> Using the information already available it is straightforward to
> calculate the number of fallback & full size slabs. We can then track
> which slabs are particularly effected by memory fragmentation and how
> long they take to recover. 
> 
> There is no change to the mainline code, the calculation is only
> performed on request, and the value is available without having to
> enable CONFIG_SLUB_STATS.  
> 

I don't see why this information is generally useful unless debugging an 
issue where statistics are already needed such as ALLOC_SLOWPATH and 
ALLOC_SLAB, so it CONFIG_SLUB_STATS can be enabled to also track 
ORDER_FALLBACK.  All stats can be cleared by writing a '0' to its sysfs 
stats file so you can collect statistics for various workloads without 
rebooting (after doing a forced shrink, for example).

--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2010-11-12 18:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 11:28 Richard Kennedy
2010-11-12 15:13 ` Christoph Lameter
2010-11-12 16:22   ` Richard Kennedy
2010-11-12 16:29     ` Christoph Lameter
2010-11-12 18:46 ` David Rientjes [this message]

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=alpine.DEB.2.00.1011121043250.5830@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=richard@rsk.demon.co.uk \
    /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