All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Chao Yu <yuchao0@huawei.com>
Subject: [PATCH 3/3] f2fs: remove redundant judgement condition in available_free_memory
Date: Sun, 21 Aug 2016 23:21:31 +0800	[thread overview]
Message-ID: <1471792891-2388-3-git-send-email-chao@kernel.org> (raw)
In-Reply-To: <1471792891-2388-1-git-send-email-chao@kernel.org>

From: Chao Yu <yuchao0@huawei.com>

In available_free_memory, there are two same judgement conditions which
is used for checking NAT excess, remove one of them.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
---
 fs/f2fs/node.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index f75d197..8a28800 100644
--- a/fs/f2fs/node.c
+++ b/fs/f2fs/node.c
@@ -54,8 +54,6 @@ bool available_free_memory(struct f2fs_sb_info *sbi, int type)
 		res = mem_size < ((avail_ram * nm_i->ram_thresh / 100) >> 2);
 		if (excess_cached_nats(sbi))
 			res = false;
-		if (nm_i->nat_cnt > DEF_NAT_CACHE_THRESHOLD)
-			res = false;
 	} else if (type == DIRTY_DENTS) {
 		if (sbi->sb->s_bdi->wb.dirty_exceeded)
 			return false;
-- 
2.7.2

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH 3/3] f2fs: remove redundant judgement condition in available_free_memory
Date: Sun, 21 Aug 2016 23:21:31 +0800	[thread overview]
Message-ID: <1471792891-2388-3-git-send-email-chao@kernel.org> (raw)
In-Reply-To: <1471792891-2388-1-git-send-email-chao@kernel.org>

From: Chao Yu <yuchao0@huawei.com>

In available_free_memory, there are two same judgement conditions which
is used for checking NAT excess, remove one of them.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
---
 fs/f2fs/node.c | 2 --
 1 file changed, 2 deletions(-)

diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
index f75d197..8a28800 100644
--- a/fs/f2fs/node.c
+++ b/fs/f2fs/node.c
@@ -54,8 +54,6 @@ bool available_free_memory(struct f2fs_sb_info *sbi, int type)
 		res = mem_size < ((avail_ram * nm_i->ram_thresh / 100) >> 2);
 		if (excess_cached_nats(sbi))
 			res = false;
-		if (nm_i->nat_cnt > DEF_NAT_CACHE_THRESHOLD)
-			res = false;
 	} else if (type == DIRTY_DENTS) {
 		if (sbi->sb->s_bdi->wb.dirty_exceeded)
 			return false;
-- 
2.7.2


------------------------------------------------------------------------------

  parent reply	other threads:[~2016-08-21 15:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21 15:21 [PATCH 1/3] f2fs: check return value of write_checkpoint during fstrim Chao Yu
2016-08-21 15:21 ` [PATCH 2/3] f2fs: schedule in between two continous batch discards Chao Yu
2016-08-21 15:21   ` Chao Yu
2016-08-23 16:53   ` Jaegeuk Kim
2016-08-23 16:53     ` Jaegeuk Kim
2016-08-25  9:22     ` Chao Yu
2016-08-25  9:22       ` Chao Yu
2016-08-25 16:57       ` Jaegeuk Kim
2016-08-25 16:57         ` Jaegeuk Kim
2016-08-26  0:50         ` Chao Yu
2016-08-26  0:50           ` Chao Yu
2016-08-26  2:50           ` Jaegeuk Kim
2016-08-26  2:50             ` Jaegeuk Kim
2016-08-21 15:21 ` Chao Yu [this message]
2016-08-21 15:21   ` [PATCH 3/3] f2fs: remove redundant judgement condition in available_free_memory Chao Yu

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=1471792891-2388-3-git-send-email-chao@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.