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 1/7] f2fs: remove checking dirty_exceed
Date: Sun, 14 Dec 2014 23:27:32 -0800 [thread overview]
Message-ID: <1418628458-82740-1-git-send-email-jaegeuk@kernel.org> (raw)
We don't need to force to write dirty_exceeded for f2fs_balance_fs_bg.
This flag was only meaningful to write bypassing conditions.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/node.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index f83326c..d6f073e 100644
--- a/fs/f2fs/node.c
+++ b/fs/f2fs/node.c
@@ -57,8 +57,6 @@ bool available_free_memory(struct f2fs_sb_info *sbi, int type)
} else if (type == INO_ENTRIES) {
int i;
- if (sbi->sb->s_bdi->dirty_exceeded)
- return false;
for (i = 0; i <= UPDATE_INO; i++)
mem_size += (sbi->im[i].ino_num *
sizeof(struct ino_entry)) >> PAGE_CACHE_SHIFT;
--
2.1.1
next reply other threads:[~2014-12-15 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 7:27 Jaegeuk Kim [this message]
2014-12-15 7:27 ` [PATCH 2/7] f2fs: fix wrong condition check to trigger f2fs_sync_fs Jaegeuk Kim
2014-12-15 7:27 ` [PATCH 3/7] f2fs: don't need to call lock_op and lock_page for abort Jaegeuk Kim
2014-12-15 7:27 ` [PATCH 4/7] f2fs: change atomic and volatile write policies Jaegeuk Kim
2014-12-15 7:27 ` [PATCH 5/7] f2fs: fix small discards not to issue redundantly Jaegeuk Kim
2014-12-15 7:27 ` [PATCH 6/7] f2fs: remove unnecessary call to invalidate inmemory pages Jaegeuk Kim
2014-12-15 7:27 ` [PATCH 7/7] f2fs: use missing the use of f2fs_kunmap_page 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=1418628458-82740-1-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).