All of lore.kernel.org
 help / color / mirror / Atom feed
From: Park Ju Hyung <qkrwngud825@gmail.com>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [PATCH 3/3] f2fs: always assume that the device is idle under gc_urgent
Date: Tue, 14 May 2019 15:36:23 +0900	[thread overview]
Message-ID: <20190514063623.57162-3-qkrwngud825@gmail.com> (raw)
In-Reply-To: <20190514063623.57162-1-qkrwngud825@gmail.com>

This allows more aggressive discards and balancing job to be done
under gc_urgent.

Signed-off-by: Park Ju Hyung <qkrwngud825@gmail.com>
---
 fs/f2fs/f2fs.h | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 533fafca68f4..14c95116cd3d 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -2192,6 +2192,9 @@ static inline struct bio *f2fs_bio_alloc(struct f2fs_sb_info *sbi,
 
 static inline bool is_idle(struct f2fs_sb_info *sbi, int type)
 {
+	if (sbi->gc_mode == GC_URGENT)
+		return true;
+
 	if (get_pages(sbi, F2FS_RD_DATA) || get_pages(sbi, F2FS_RD_NODE) ||
 		get_pages(sbi, F2FS_RD_META) || get_pages(sbi, F2FS_WB_DATA) ||
 		get_pages(sbi, F2FS_WB_CP_DATA) ||
-- 
2.21.0

  parent reply	other threads:[~2019-05-14  6:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14  6:36 [PATCH 1/3] f2fs: remove sleep_time under gc_urgent Park Ju Hyung
2019-05-14  6:36 ` [PATCH 2/3] f2fs: don't wait with each discards " Park Ju Hyung
2019-05-14  6:36 ` Park Ju Hyung [this message]
2019-05-21  0:11   ` [PATCH 3/3] f2fs: always assume that the device is idle " Jaegeuk Kim
2019-05-22 12:10     ` Chao Yu
2019-05-14  9:20 ` [PATCH 1/3] f2fs: remove sleep_time " Chao Yu
     [not found]   ` <CAD14+f0Zia3oAi+QO+wCBrbV_=csp1SWB4BE7yN0h+=paZpg=w@mail.gmail.com>
2019-05-14 11:19     ` Chao Yu
2019-05-14 11:30       ` Ju Hyung Park
2019-05-15  2:08         ` Chao Yu
2019-05-21  0:10           ` Jaegeuk Kim
2019-05-22 12:10             ` 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=20190514063623.57162-3-qkrwngud825@gmail.com \
    --to=qkrwngud825@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.