From: Wang shilong <wangshilong1991@gmail.com>
To: jack@suse.cz
Cc: linux-ext4@vger.kernel.org,
Wang shilong <wangshilong1991@gmail.com>,
Wang Shilong <wangsl-fnst@cn.fujitsu.com>
Subject: [PATCH 3/3] Ext2: remove the static function release_blocks to optimize the kernel
Date: Wed, 6 Feb 2013 14:14:28 +0800 [thread overview]
Message-ID: <1360131268-1615-3-git-send-email-wangshilong1991@gmail.com> (raw)
In-Reply-To: <1360131268-1615-1-git-send-email-wangshilong1991@gmail.com>
From: Wang Shilong <wangsl-fnst@cn.fujitsu.com>
Because the static function 'release_blocks' is only called
when releasing blocks,it will be more simple and efficient to
call the function 'percpu_counter_add' directly.
Signed-off-by: Wang Shilong <wangsl-fnst@cn.fujitsu.com>
---
fs/ext2/balloc.c | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/fs/ext2/balloc.c b/fs/ext2/balloc.c
index 9d372bf..d5a6afd 100644
--- a/fs/ext2/balloc.c
+++ b/fs/ext2/balloc.c
@@ -159,15 +159,6 @@ read_block_bitmap(struct super_block *sb, unsigned int block_group)
return bh;
}
-static void release_blocks(struct super_block *sb, int count)
-{
- if (count) {
- struct ext2_sb_info *sbi = EXT2_SB(sb);
-
- percpu_counter_add(&sbi->s_freeblocks_counter, count);
- }
-}
next prev parent reply other threads:[~2013-02-06 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 6:14 [PATCH 1/3] Ext2: remove the overhead check about sb in the function ext2_new_blocks Wang shilong
2013-02-06 6:14 ` [PATCH 2/3] Ext2: mark inode dirty after the function dquot_free_block_nodirty is called Wang shilong
2013-02-06 12:44 ` Jan Kara
2013-02-06 6:14 ` Wang shilong [this message]
2013-02-06 12:48 ` [PATCH 3/3] Ext2: remove the static function release_blocks to optimize the kernel Jan Kara
2013-02-06 12:46 ` [PATCH 1/3] Ext2: remove the overhead check about sb in the function ext2_new_blocks Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2013-02-06 20:03 [PATCH 3/3] Ext2: remove the static function release_blocks to optimize the kernel Wang Shilong
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=1360131268-1615-3-git-send-email-wangshilong1991@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=wangsl-fnst@cn.fujitsu.com \
/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).