From: David Woodhouse Date: Sat, 13 Oct 2007 10:29:07 +0000 (+0100) Subject: [JFFS2] Relax threshold for triggering GC due to dirty blocks. X-Git-Tag: v2.6.24-rc1~1364^2~10 X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=85becc535b7f33be5aefdb8ecea9fac4998e4b6f;p=linux-2.6 [JFFS2] Relax threshold for triggering GC due to dirty blocks. Instead of matching resv_blocks_gcmerge, which is only about 3, instead match resv_blocks_gctrigger, which includes a proportion of the total device size. These ought to become tunable from userspace, at some point. Signed-off-by: David Woodhouse --- diff --git a/fs/jffs2/build.c b/fs/jffs2/build.c index 8c27c12816..722a6b6829 100644 --- a/fs/jffs2/build.c +++ b/fs/jffs2/build.c @@ -289,7 +289,7 @@ static void jffs2_calc_trigger_levels(struct jffs2_sb_info *c) trigger the GC thread even if we don't _need_ the space. When we can't mark nodes obsolete on the medium, the old dirty nodes cause performance problems because we have to inspect and discard them. */ - c->vdirty_blocks_gctrigger = c->resv_blocks_gcmerge; + c->vdirty_blocks_gctrigger = c->resv_blocks_gctrigger; if (jffs2_can_mark_obsolete(c)) c->vdirty_blocks_gctrigger *= 10;