From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 5/6] f2fs: don't need to sync node page at every time
Date: Mon, 25 Jan 2016 14:05:30 -0800 [thread overview]
Message-ID: <1453759531-16076-5-git-send-email-jaegeuk@kernel.org> (raw)
In-Reply-To: <1453759531-16076-1-git-send-email-jaegeuk@kernel.org>
In write_end, we don't need to sync inode page at every time.
Instead, we can expect f2fs_write_inode will update later.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/data.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 260c0eb..a6a6f08 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -1627,7 +1627,6 @@ static int f2fs_write_end(struct file *file,
if (pos + copied > i_size_read(inode)) {
i_size_write(inode, pos + copied);
mark_inode_dirty(inode);
- update_inode_page(inode);
}
f2fs_put_page(page, 1);
--
2.6.3
next prev parent reply other threads:[~2016-01-25 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 22:05 [PATCH 1/6] f2fs: speed up shrinking extent_node cache Jaegeuk Kim
2016-01-25 22:05 ` [PATCH 2/6] f2fs: give scheduling point in shrinking path Jaegeuk Kim
2016-01-25 22:05 ` [PATCH 3/6] f2fs: do f2fs_balance_fs when block is allocated Jaegeuk Kim
2016-01-25 22:05 ` [PATCH 4/6] f2fs: avoid multiple node page writes due to inline_data Jaegeuk Kim
2016-01-26 5:41 ` Chao Yu
2016-01-26 18:48 ` [f2fs-dev] " Jaegeuk Kim
2016-01-27 6:28 ` Chao Yu
2016-01-25 22:05 ` Jaegeuk Kim [this message]
2016-01-25 22:05 ` [PATCH 6/6] f2fs: avoid needless sync_inode_page when reading inline_data Jaegeuk Kim
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=1453759531-16076-5-git-send-email-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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).