From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <cl@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Manfred Spraul <manfred@colorfullife.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH -mm 3/6] slub: introduce __kfree_rcu
Date: Tue, 03 Mar 2009 21:44:30 +0800 [thread overview]
Message-ID: <49AD343E.6010903@cn.fujitsu.com> (raw)
Introduce __kfree_rcu() for kfree_rcu()
It like __kfree_rcu() in slab.c.
We can calculate the object poiter from a poiter inside this
object in slub.c, so we can use it for rcu callback and free
the object.
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
---
diff --git a/mm/slub.c b/mm/slub.c
index 0280eee..b438ec5 100644
--- a/mm/slub.c
+++ b/mm/slub.c
@@ -2756,6 +2756,30 @@ void kfree(const void *x)
}
EXPORT_SYMBOL(kfree);
+static void kfree_rcu_callback(struct rcu_head *rcu)
+{
+ void *portion = rcu;
+ struct page *page = virt_to_head_page(portion);
+
+ if (unlikely(!PageSlab(page))) {
+ BUG_ON(!PageCompound(page));
+ put_page(page);
+ } else {
+ struct kmem_cache *s = page->slab;
+ void *start = page_address(page);
+ unsigned int index = (portion - start) / s->size;
+ void *object = start + s->size * index;
+
+ slab_free(s, page, object, _RET_IP_);
+ }
+}
+
+void __kfree_rcu(const void *x, struct rcu_head *rcu)
+{
+ call_rcu(rcu, kfree_rcu_callback);
+}
+EXPORT_SYMBOL(__kfree_rcu);
+
/*
* kmem_cache_shrink removes empty slabs from the partial lists and sorts
* the remaining slabs by the number of items in use. The slabs with the
next reply other threads:[~2009-03-03 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 13:44 Lai Jiangshan [this message]
2009-03-04 15:06 ` [PATCH -mm 3/6] slub: introduce __kfree_rcu Christoph Lameter
2009-03-05 1:20 ` Lai Jiangshan
2009-03-05 14:39 ` Christoph Lameter
2009-03-07 5:34 ` Paul E. McKenney
2009-03-23 7:50 ` 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=49AD343E.6010903@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=paulmck@linux.vnet.ibm.com \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.