From: Christoph Lameter <clameter@sgi.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, dgc@sgi.com
Subject: [patch 05/12] Slab defragmentation: Log information to the syslog to show defrag operations
Date: Sat, 07 Jul 2007 20:05:43 -0700 [thread overview]
Message-ID: <20070708030844.569230197@sgi.com> (raw)
In-Reply-To: <20070708030538.729027694@sgi.com>
[-- Attachment #1: slub_defrag_tracing --]
[-- Type: text/plain, Size: 1571 bytes --]
Dump information into the syslog during defragmentation actions to show that
something is occurring and what effect it has.
This is likely only useful in mm for testing and verification.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
---
mm/slub.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
Index: linux-2.6.22-rc6-mm1/mm/slub.c
===================================================================
--- linux-2.6.22-rc6-mm1.orig/mm/slub.c 2007-07-06 20:04:54.000000000 -0700
+++ linux-2.6.22-rc6-mm1/mm/slub.c 2007-07-06 20:06:45.000000000 -0700
@@ -2599,6 +2599,8 @@ static unsigned long sort_partial_list(s
return freed;
}
+#define NR_INUSE 40
+
/*
* Shrink the slab cache on a particular node of the cache
*/
@@ -2610,6 +2612,8 @@ static unsigned long __kmem_cache_shrink
LIST_HEAD(zaplist);
int freed;
int inuse;
+ int nr[NR_INUSE] = { 0, };
+ int i;
spin_lock_irqsave(&n->list_lock, flags);
freed = sort_partial_list(s, n, scratch);
@@ -2646,6 +2650,8 @@ static unsigned long __kmem_cache_shrink
n->nr_partial--;
SetSlabFrozen(page);
slab_unlock(page);
+ if (inuse < NR_INUSE)
+ nr[inuse]++;
}
spin_unlock_irqrestore(&n->list_lock, flags);
@@ -2659,6 +2665,13 @@ static unsigned long __kmem_cache_shrink
if (__kmem_cache_vacate(s, page, flags, scratch) == 0)
freed++;
}
+ printk(KERN_INFO "Slab %s: Defrag freed %d pages. PartSlab config=",
+ s->name, freed << s->order);
+
+ for (i = 0; i < NR_INUSE; i++)
+ if (nr[i])
+ printk(" %d=%d", i, nr[i]);
+ printk("\n");
return freed;
}
--
next prev parent reply other threads:[~2007-07-08 3:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 3:05 [patch 00/12] Slab defragmentation V4 Christoph Lameter
2007-07-08 3:05 ` [patch 01/12] Slab defragmentation: Add support for kmem_cache_ops Christoph Lameter
2007-07-08 3:05 ` [patch 02/12] Slab defragmentation: Core piece Christoph Lameter
2007-07-08 3:05 ` [patch 03/12] Slab defragmentation: Updates to slabinfo.c Christoph Lameter
2007-07-08 3:05 ` [patch 04/12] Slab defragmentation: Logic to trigger defragmentation from memory reclaim Christoph Lameter
2007-07-08 3:05 ` Christoph Lameter [this message]
2007-07-08 3:05 ` [patch 06/12] Slab defragmentation: Support dentry defragmentation Christoph Lameter
2007-07-08 3:05 ` [patch 07/12] Slab defragmentation: Support for buffer_head defrag Christoph Lameter
2007-07-08 3:05 ` [patch 08/12] Slab defragmentation: Support generic defragmentation for inode slab caches Christoph Lameter
2007-07-08 3:05 ` [patch 09/12] Slab defragmentation: Support defragmentation for extX filesystem inodes Christoph Lameter
2007-07-08 3:05 ` [patch 10/12] Slab defragmentation: Support inode defragmentation for xfs Christoph Lameter
2007-07-08 3:05 ` [patch 11/12] Slab defragmentation: Support reiserfs inode defragmentation Christoph Lameter
2007-07-08 3:05 ` [patch 12/12] Slab defragmentation: kmem_cache_vacate for antifrag / memory compaction 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=20070708030844.569230197@sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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