From: remaper <yp.fangdong@gmail.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re:[PATCH] fs/buffer.c: Remove the unnecessary init operation afterallocating buffer_head.
Date: Fri, 19 Apr 2013 14:06:27 +0800 [thread overview]
Message-ID: <tencent_31437B7D0889BFB832E5286F@qq.com> (raw)
i don't understand why the init_buffer() should relay on the memory allocation behavior, :)
------------------ Original ------------------
From: "majianpeng"<majianpeng@gmail.com>;
Date: Fri, Apr 19, 2013 10:29 AM
To: "Al Viro"<viro@zeniv.linux.org.uk>; "akpm"<akpm@linux-foundation.org>; "tytso"<tytso@mit.edu>;
Cc: "linux-fsdevel"<linux-fsdevel@vger.kernel.org>; "linux-kernel"<linux-kernel@vger.kernel.org>; "linux-ext4"<linux-ext4@vger.kernel.org>;
Subject: [PATCH] fs/buffer.c: Remove the unnecessary init operation afterallocating buffer_head.
Because alloc struct buffer_head using kmem_cache_zalloc,so it's not need to
call 'init_buffer(bh, NULL, NULL)'.
Signed-off-by: Jianpeng Ma <majianpeng@gmail.com>
---
fs/buffer.c | 2 --
fs/jbd/journal.c | 1 -
fs/jbd2/journal.c | 1 -
3 files changed, 4 deletions(-)
diff --git a/fs/buffer.c b/fs/buffer.c
index b4dcb34..52b7739 100644
--- a/fs/buffer.c
+++ b/fs/buffer.c
@@ -865,8 +865,6 @@ try_again:
/* Link the buffer to its page */
set_bh_page(bh, page, offset);
-
- init_buffer(bh, NULL, NULL);
}
return head;
/*
diff --git a/fs/jbd/journal.c b/fs/jbd/journal.c
index 81cc7ea..0c3fe90 100644
--- a/fs/jbd/journal.c
+++ b/fs/jbd/journal.c
@@ -311,7 +311,6 @@ int journal_write_metadata_buffer(transaction_t *transaction,
new_bh = alloc_buffer_head(GFP_NOFS|__GFP_NOFAIL);
/* keep subsequent assertions sane */
new_bh->b_state = 0;
- init_buffer(new_bh, NULL, NULL);
atomic_set(&new_bh->b_count, 1);
new_jh = journal_add_journal_head(new_bh); /* This sleeps */
diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
index ed10991..95120c6 100644
--- a/fs/jbd2/journal.c
+++ b/fs/jbd2/journal.c
@@ -368,7 +368,6 @@ retry_alloc:
/* keep subsequent assertions sane */
new_bh->b_state = 0;
- init_buffer(new_bh, NULL, NULL);
atomic_set(&new_bh->b_count, 1);
new_jh = jbd2_journal_add_journal_head(new_bh); /* This sleeps */
--
1.8.2.rc2.4.g7799588
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2013-04-19 6:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_31437B7D0889BFB832E5286F@qq.com \
--to=yp.fangdong@gmail.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).