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 2/6] f2fs: give scheduling point in shrinking path
Date: Mon, 25 Jan 2016 14:05:27 -0800 [thread overview]
Message-ID: <1453759531-16076-2-git-send-email-jaegeuk@kernel.org> (raw)
In-Reply-To: <1453759531-16076-1-git-send-email-jaegeuk@kernel.org>
It needs to give a chance to be rescheduled while shrinking slab entries.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fs/f2fs/extent_cache.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/f2fs/extent_cache.c b/fs/f2fs/extent_cache.c
index 18311ff..af53503 100644
--- a/fs/f2fs/extent_cache.c
+++ b/fs/f2fs/extent_cache.c
@@ -593,6 +593,8 @@ unsigned int f2fs_shrink_extent_tree(struct f2fs_sb_info *sbi, int nr_shrink)
if (node_cnt + tree_cnt >= nr_shrink)
goto unlock_out;
+
+ cond_resched();
}
up_write(&sbi->extent_tree_lock);
@@ -622,6 +624,7 @@ free_node:
__detach_extent_node(sbi, en->et, en);
write_unlock(&en->et->lock);
kmem_cache_free(extent_node_slab, en);
+ cond_resched();
}
unlock_out:
--
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 ` Jaegeuk Kim [this message]
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 ` [f2fs-dev] " Chao Yu
2016-01-26 18:48 ` Jaegeuk Kim
2016-01-27 6:28 ` Chao Yu
2016-01-25 22:05 ` [PATCH 5/6] f2fs: don't need to sync node page at every time Jaegeuk Kim
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-2-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).