From: Dave Chinner <david@fromorbit.com>
To: viro@ZenIV.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
eric.dumazet@gmail.com, paulmck@linux.vnet.ibm.com
Subject: [PATCH 3/4] fs: Use RCU freeing of inodes via SLAB_DESTROY_BY_RCU
Date: Mon, 8 Nov 2010 18:28:24 +1100 [thread overview]
Message-ID: <1289201305-14866-4-git-send-email-david@fromorbit.com> (raw)
In-Reply-To: <1289201305-14866-1-git-send-email-david@fromorbit.com>
From: Dave Chinner <dchinner@redhat.com>
Change the inode caches to use RCU freed inodes via the SLAB_DESTROY_BY_RCU
method. This is the first step in converting the inode hash lookups to use RCU
methods.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
---
include/linux/slab.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/slab.h b/include/linux/slab.h
index dca23c5..1fea5f1 100644
--- a/include/linux/slab.h
+++ b/include/linux/slab.h
@@ -96,6 +96,7 @@
* Set the default flags necessary for inode caches manipulated by the VFS.
*/
#define SLAB_INODE_CACHE (SLAB_MEM_SPREAD | \
+ SLAB_DESTROY_BY_RCU | \
SLAB_RECLAIM_ACCOUNT)
/*
--
1.7.2.3
next prev parent reply other threads:[~2010-11-08 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 7:28 fs: inode rcu freeing and hash walking V2 Dave Chinner
2010-11-08 7:28 ` [PATCH 1/4] fs: pull inode->i_lock up out of writeback_single_inode Dave Chinner
2010-11-08 7:28 ` [PATCH 2/4] fs: Convert inode slab creation to use consistent parameters Dave Chinner
2011-04-25 17:46 ` Christoph Hellwig
2010-11-08 7:28 ` Dave Chinner [this message]
2010-11-08 7:28 ` [PATCH 4/4] fs: rcu protect inode hash lookups Dave Chinner
2010-11-08 8:53 ` Eric Dumazet
2010-11-08 11:10 ` Christoph Hellwig
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=1289201305-14866-4-git-send-email-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=viro@ZenIV.linux.org.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;
as well as URLs for NNTP newsgroup(s).