From: Vlad Zolotarov <vlad@scalemp.com>
To: "linux-kernel" <linux-kernel@vger.kernel.org>, viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org
Subject: [PATCH] fs: Move bh_cachep to the __read_mostly section
Date: Tue, 15 May 2012 12:29:52 +0300 [thread overview]
Message-ID: <201205151229.52854.vlad@scalemp.com> (raw)
From: Shai Fultheim <shai@scalemp.com>
bh_cachep is only written to once on initialization, so move it to the
__read_mostly section.
Signed-off-by: Shai Fultheim <shai@scalemp.com>
Signed-off-by: Vlad Zolotarov <vlad@scalemp.com>
---
fs/buffer.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/buffer.c b/fs/buffer.c
index 36d6665..a1d82fb 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -3151,7 +3151,7 @@ SYSCALL_DEFINE2(bdflush, int, func, long, data)
/*
* Buffer-head allocation
*/
-static struct kmem_cache *bh_cachep;
+static struct kmem_cache *bh_cachep __read_mostly;
/*
* Once the number of bh's in the machine exceeds this level, we start
--
1.7.7.6
next reply other threads:[~2012-05-15 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 9:29 Vlad Zolotarov [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-24 11:22 [PATCH] fs: Move bh_cachep to the __read_mostly section Vlad Zolotarov
2012-05-03 11:26 ` Vlad Zolotarov
2012-04-17 10:11 Vlad Zolotarov
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=201205151229.52854.vlad@scalemp.com \
--to=vlad@scalemp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).